scaffold-agentlisted

Use when adding a new dedicated subagent to an existing plugin in this `nuthouse` marketplace. Asks for parent plugin, agent name (descriptive role, no vague names like "agent" / "helper"), description, model (`haiku` for parsing/fetch+summary vs default for reasoning), explicit tools allowlist, input format spec, output format spec (SDD vs structured report vs custom). Generates `<plugin>/agents/<name>.md` with the right frontmatter (name, description, model, tools list) and the standard Mission / Input / Output / Hard rules sections. Encodes the subagent and SDD conventions from the legacy CLAUDE.md.
g-bastianelli/nuthouse · ★ 0 · AI & Automation · score 65

Install: claude install-skill g-bastianelli/nuthouse

# scaffold-agent ## Voice Read `../persona.md` at the start of this skill. The voice defined there (mad-scientist) is canonical and applies to all output of this skill. **Scope:** local to this skill's execution. Once the final report is printed, revert to the session's default voice. This skill is **rigid** — execute the steps in order. ## When you're invoked The user wants to add a dedicated subagent to an existing plugin. Either via `/scaffold-agent`, or routed from `scaffold-skill` when a skill declared `Q5 = "dedicated agent"`. ## Step 0 — Preconditions 1. **Inside the `nuthouse` repo.** Verify cwd contains `.claude-plugin/marketplace.json`. If not, abort. 2. **Discover existing plugins.** Glob `<repo>/*/persona.md`. List the parent-plugin candidates. 3. **Verify the target has a plugin manifest.** A plugin can expose root `agents/` to Claude Code through `.claude-plugin/plugin.json`. If the target is truly Codex-only and has no `.claude-plugin/`, abort: > "ce plugin est codex-only. ajoute d'abord une branche Claude Code si > tu veux exposer des agents." ## Step 1 — Interview ### Q1 — Parent plugin AskUserQuestion, single-select. Voice: _"dans quel laboratoire on relâche l'organisme ?"_ ### Q2 — Agent name (no prefix) Free-text. Voice: _"comment l'organisme s'appelle-t-il ?"_ **Validation rules**: - **Descriptive role or task name**: `explorer`, `issue-context`, `spec-auditor`, `code-reviewer`, `plan-writer`, `project-drafter`. ✅ - **No v