creating-skills
Creating Skills
Role and Ownership
Use this skill as the primary entry point for both new skill and existing skill work, especially whenever a request matches both creating-skills and an available skill-creator.
When a compatible skill-creator is available, invoke it before local artifact-producing work and delegate only the stages it supports within the current evaluation budget: intent discovery, use cases and triggers, skill structure, scripts and other resources, drafting, evaluation cases, grading, benchmark analysis, human review, separately authorized iteration, description optimization, and packaging.
Retain ownership here for:
- target surfaces, repository policy, and durable artifact layout;
- user authority, safety invariants, and mutation or publication boundaries;
- required evidence and acceptance thresholds;
- gaps between the creator's output and the project contract; and
- the final accept, reject, or retire decision.
Treat delegated artifacts and results as candidates. Inspect them before filling gaps, and do not duplicate a delegated stage merely to keep control local. Judge an available creator by the capabilities it exposes in the active environment, not by the product name or packaging of one installation.