domains / families / agent-tooling / skill-development
This skill should be used when the user asks to create a new skill, repair an existing skill, improve trigger descriptions, reorganize skill structure, or make a Claude skill more reusable and internally consistent. This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
The two skills cover the same domain (creating and maintaining Claude Code skills) but diverge significantly in scope and methodology. The first copy (scenario-labs) is a theoretical guide focused on the 'Anatomy of a Skill' and 'Progressive Disclosure' design principles, treating skills as abstract plugin components. The second copy (brycewang-stanford) is a practical, environment-aware workflow that emphasizes inspecting the local filesystem, verifying the existence of referenced files, and performing integrity checks to prevent 'dead references.' The first copy lacks the local verification steps, while the second lacks the detailed theoretical breakdown of resource types (scripts vs. references vs. assets) and the specific 'Progressive Disclosure' context management strategy. Combining them yields a complete guide that covers both the design theory and the practical implementation/verification workflow.