Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →notque/agent-creator
Scaffold vexjoy-agent operator .md files: frontmatter, routing block, operator context, reference loading table, phase/gate workflow.
Passed 16 of 22 test cases with the skill, and 8 of 22 without it.
and 5 more in the full report
8 fixed8 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I manually edited agents/INDEX.json to add my new agent. Is this the standard way to update the agent index?
| Checked | Without skill | With skill |
|---|---|---|
| Instructs running python3 scripts/generate-agent-index.py rather than modifying JSON manually | Missed | Passed |
The instructions your model reads when the skill loads.
Scaffold correctly-formed vexjoy-agent operator .md files. An agent file is a system-prompt contract: it sets identity, constraints, expertise, and routing — not application code.
Phases: DISCOVER → DESIGN → SCAFFOLD → REGISTER → VALIDATE
Check for domain overlap before creating anything.
grep -i "<domain-keyword>" agents/*.md | grep "^agents/" | cut -d: -f1 | sort -u
ls agents/ | grep "<domain-prefix>"
Gate 1: If an existing agent covers the domain, add a references/ file to that agent instead of creating a new one. Proceed only when no existing agent covers the domain, or the user confirms after seeing the overlap.
Read docs/PHILOSOPHY.md before proceeding — the philosophy governs operator context structure, progressive disclosure, positive framing, and tool restrictions. Components that violate it will fail CI.
Decide the agent's identity and routing contract before writing a single line.
| Decision | Question to answer |
|---|---|
| Role type | Reviewer/auditor, code modifier/engineer, or orchestrator? |
| Allowed tools | Matches role: reviewers→Read/Glob/Grep; engineers→+Edit/Write/Bash; orchestrators→Read/Agent/Bash |
| Complexity | Low (single-file, read-only), Medium (multi-file, routing), High (full sweeps, orchestration) |
| Triggers | 3–6 specific phrases a user would naturally say — not generic verbs |
| pairs_with | 2–3 agents commonly co-dispatched; verify each exists on disk before listing |
| Reference files | Domains needing depth — each goes in agents/{name}/references/ loaded on demand |
| Description craft | Intent verb + domain object, 2–3 adjacent terms, one false-positive boundary clause with redirect |
| Activation cases | 3 should-trigger / 2 should-not-trigger / 2 near-miss phrases drafted now, saved at scaffold time |
Load references/agent-design-patterns.md for operator context structure, hook design, routing design, authority/trust framing, and smells-to-rewrite guidance.
test cases passed, vs 8 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.