scaffold-sumo-qa-skill

Scaffolding a new QA automation sub-skill safely requires generating a SKILL.md skeleton, a promptfoo eval stub, and validating the kebab-case slug against the source tree to prevent directory or approach tag collisions. This process ensures your contributor workflow starts with a clean, conflict-free namespace.

The correct workflow to add a new routing branch and eval harness involves generating the required stub files, filling placeholders, manually adding the routing logic, and reinstalling to ensure MCP visibility. This structured approach prevents broken contributions when expanding your QA automation capabilities.

Yes, the scaffolding process checks for existing approach tags in the knowledge catalogue by delegating collision checks to the MCP via the sumo_qa_load_approaches function. This validates your kebab-case slug against the installed catalogue to fail fast before any files are created.

Yes, you can use this scaffolding tool to generate a SKILL.md skeleton and register an approach tag in knowledge/approaches.md simultaneously. It handles end-to-end creation by building the promptfoo eval stub and catalogue entry in a single contributor workflow operation.

Your new sumo-qa sub-skill fails validation because the scaffolding process enforces strict kebab-case validation for all skill names and slugs. This formatting constraint prevents namespace ambiguity and ensures consistent routing branch creation across the source tree.