smith

Smith: Plugin Scaffolder

You are the Smith orchestrator. When the user runs /smith <plugin-name>, scaffold a new Quickstop plugin with correct structure, frontmatter, and marketplace registration. Follow each phase in order.

Human-driven by design. Smith carries disable-model-invocation: true in its frontmatter, which means agents and sub-Claudes cannot dispatch it through the Skill tool — Skill(smith, ...) returns Skill smith cannot be used with Skill tool due to disable-model-invocation. This is intentional, not an oversight. Smith is an interactive scaffolding skill: it asks questions via AskUserQuestion and produces a plugin from human answers. Letting an agent answer those questions on the user's behalf would defeat the purpose. The supported way for an agent to "dogfood" smith is the recipe-by-hand path — read this SKILL.md and execute each phase manually against the user's stated inputs, calling Read/Write/Edit/Bash directly rather than dispatching the skill.

Hook note. Smith does not scaffold a hooks/ directory. If you see the user mention "hooks" anywhere during the questionnaire — in the Description, in Components, or in any free-text answer — prepend the following note to the very next prompt you display (once, not repeatedly): "Note: smith doesn't scaffold hooks. Author a hook by hand: a small script under bin/ wired from a hooks/hooks.json entry in the consumer's surface, observing only (no payload or flow mutation)." Then continue normally.

Phase 0: Validation

Step 1: Parse Plugin Name

Extract the plugin name from $ARGUMENTS. If empty or missing, use AskUserQuestion to ask:

• "What should the plugin be named? (kebab-case, e.g. my-plugin)"

Step 2: Validate Name

1. Kebab-case: Name must match ^[a-z][a-z0-9]*(-[a-z0-9]+)*$. If not, reject and ask for a valid name.
2. No conflicts: Glob for plugins/$ARGUMENTS/ — if it exists, tell the user and abort.
3. PROJECT_ROOT: Run git rev-parse --show-toplevel via Bash to get the repo root.