Skip to content

monte-carlo-data/mc-agent-toolkit / .claude/skills/toolkit-skill-author

toolkit-skill-author

Verified

Authors or extends a skill in mc-agent-toolkit. Gates for forbidden buckets and name collisions, applies CONTRIBUTING's extend-or-split rules, then edits a peer skill or hands off to Anthropic's skill-creator and walks the registration checklist.

references/handoff-preamble.md

View on GitHub
# Handoff preamble for Anthropic's `skill-creator`

This is the template `toolkit-skill-author` uses when invoking Anthropic's `skill-creator` via the `Skill` tool. Claude fills in the bracketed placeholders from survey answers.

## Template

You are being invoked by mc-agent-toolkit's `/toolkit-skill-author` with pre-collected context.
**Use the pre-filled answers below to skip your initial interview. Then run your full workflow — test cases, iterate loop, and description optimizer — using the answers as the starting draft. If the contributor tells you mid-flow to skip iteration ("just vibe with me"), honor that.**

**Mode:** {{NEW_SKILL | IMPROVE_EXISTING}}

**Target path:** `skills/{{NAME}}/` in the mc-agent-toolkit repo (not your default workspace).

**Pre-filled answers:**
- What should this skill enable Claude to do? {{PURPOSE}}
- When should this skill trigger? {{PHRASINGS as bullet list}}
- Expected output format: {{OUTPUT}}

**Body context (inform the SKILL.md body, do NOT copy verbatim into frontmatter):**
- Persona / workflow: {{PERSONA_WORKFLOW}}
- Disambiguation from nearest peer `{{PEER_NAME}}`: {{DISAMBIGUATION}}
- Bucket: {{BUCKET}} (also emitted as the `bucket` frontmatter field — see below)

**MC-specific voice and length rules (override your defaults):**
- `description` ≤ 1,024 characters.
- Combined `description` + `when_to_use` ≤ 1,400 characters (headroom under the 1,536 truncation ceiling).
- Third-person voice. Describe what the skill does, not what "this skill" does.
- Do **not** open with "This skill…" or "Use this skill when…".
- Do **not** use the "pushy" voice pattern ("Make sure to use this skill whenever…"); use concrete triggers instead.

**Required frontmatter fields (and fields NOT to emit):**
- `name`: `monte-carlo-{{NAME}}` — canonical prefixed form; `{{NAME}}` is the directory name.
- `description`: per the length rule above.
- `when_to_use`: required (not optional).
- `bucket`: `{{BUCKET}}` — one of Trust / Incident Response / Monitoring / Prevent / Optimize / Setup. Tracks which capability bucket the skill belongs to in the public docs.
- Do **not** emit a `version` field. Versions live in the plugin manifests (`plugins/*/.*-plugin/plugin.json`), not in SKILL.md. `toolkit-skill-author` will bump them separately via `scripts/bump-version.sh` after you return.

**Portability markers (required when applicable):**
- Wrap every plugin-only passage — slash-command mentions, hook behaviour, "use the Read tool on `references/…`" instructions — in `<!-- plugin-only:start -->` / `<!-- plugin-only:end -->` on their own lines, so the MCP prompt renderer can drop it. Everything else must read correctly without the plugin. See `CONTRIBUTING.md § Portability markers for plugin-only sections`.

**Eval artifacts are scratch, not shipped:**
- Your `skills/{{NAME}}/evals/evals.json` and sibling `skills/{{NAME}}-workspace/` drive the iteration loop but are not the repo's eval format. `toolkit-skill-author` will delete them after you return.
- mc-agent-toolkit's real evals live at `plugins/claude-code/evals/{{NAME}}/trigger-evals.json` (trigger accuracy) and `plugins/claude-code/evals/{{NAME}}/live-evals-dev.yaml` (flow evals). Authoring both files is handled by `toolkit-skill-author` in the registration checklist — don't attempt to write either yourself.

**When done:** return control to `toolkit-skill-author`. It will lint the generated SKILL.md, clean up scratch artifacts, and walk the registration checklist.

## Improve-existing mode differences

When `{{MODE}} == IMPROVE_EXISTING`:
- **Target path:** the existing `skills/{{PEER_NAME}}/` (edit in place, not new scaffold).
- **Pre-filled answers** describe the *extension*, not a new skill.
- Otherwise identical: same voice rules, same full workflow, same scratch-artifact cleanup.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall