The meta-skill makes unavailable, unaudited skills mandatory workflows
Source references: 3The file claims authority over discovery and invocation of all skills and tells the agent to check for an applicable skill before work, execute steps in order, and skip none. Its complete-feature example extends through migration, version control, and launch. Because the invoked skills are not supplied, a user cannot determine from this source whether they run commands, modify repositories, access networks, or deploy.
If the agent automatically selects and follows other installed skills, the task could expand into additional code changes, commits, migrations, or release procedures. This file does not itself perform those actions and does not show that any action occurred.
The meta-skill requires the agent to find other skills before work and treats their ordered steps and verification as mandatory. Its full-feature chain can extend through version control, migration, and deployment. It also says not every task needs every skill, so deployment is not unconditional; however, the referenced skills are absent, preventing users from checking their commands, network use, or changes. Users can request all dependency texts and a permission manifest, and prohibit network, commit, migration, or deployment actions without per-action approval.
name: using-agent-skillsdescription: Discovers and invokes agent skills. Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.---Show 2 other places
1. **Check for an applicable skill before starting work.** Skills encode processes that prevent common mistakes.2. **Skills are workflows, not suggestions.** Follow the steps in order. Don't skip verification steps.3. **Multiple skills can apply.** A feature implementation might involve `idea-refine` → `spec-driven-development` → `planning-and-task-breakdown` → `incremental-implementation` → `test-driven-development` → `code-review-and-quality` → `code-simplification` → `shipping-and-launch` in sequence.4. **When in doubt, start with a spec.** If the task is non-trivial and there's no spec, begin with `spec-driven-development`.10. test-driven-development → Prove each slice works11. code-review-and-quality → Review before merge12. code-simplification → Reduce unnecessary complexity while preserving behavior13. git-workflow-and-versioning → Clean commit history14. documentation-and-adrs → Document decisions15. deprecation-and-migration → Retire old systems and move users safely when needed16. shipping-and-launch → Deploy safely```Not every task needs every skill. A bug fix might only need: `debugging-and-error-recovery` → `test-driven-development` → `code-review-and-quality`.