Design philosophy

From README § Design philosophy:

• Skills are content. Core code stays in small Bash/Python-stdlib validators, runtimes, hooks, connectors, and guards — no pip on shipped surfaces.
• Keyless first. Every ~~category has a free/own-data recipe; MCP and paid tools are pure convenience.
• Surgical & MECE. Each skill owns one job; overlapping work ships as a mode, not a thin new skill. Registries curate, gates judge.
• No invented numbers. Skills label every figure Measured / User-provided / Estimated.
• Compliance is guidance, not law. FTC-disclosure and claim-integrity checks flag risk; they are not legal advice.