sp-writing-skills

To validate skill frontmatter and metadata before deployment, run a test-driven development cycle that checks for standardized description structure, trigger mappings, and consistent metadata generation to close testing gaps before release.

Test-driven development for skill authoring workflows is a RED-GREEN-REFACTOR cycle that automates validation of new and updated skills. It ensures proper tests and documentation are established across the knowledge base before deployment.

Yes, you can use a TDD workflow to check skill triggers and dependency listings. The validation cycle automatically verifies frontmatter presence, trigger mappings, and dependency listing requirements during skill creation and review.

To run a baseline skill authoring and validation session, write the SKILL.md content first, then re-run the validation cycle to verify compliance. This repeatable process enforces baseline tests and consistent metadata generation.

Yes, skill validation includes toxicity checks and component detection. The validation cycle satisfies frontmatter presence, dependency listing, component detection, toxicity checks, and consistent metadata generation during the authoring workflow.