/agent-creator

name: agent-creator
description: |
  Creates structured agent definitions using the 7-component format grounded in persona science (the alignment-accuracy tradeoff), vocabulary routing, and the MAST failure taxonomy + Forge watchlist. Produces agents with real-world job titles, expert domain vocabulary payloads (15-30 terms), explicit deliverables, decision boundaries, imperative SOPs, and named anti-pattern watchlists.

  Use this skill when the user wants to create an agent, define a role, build a persona, or needs a specialized AI assistant for a specific domain. Also triggers when Mission Planner delegates agent creation for team roles. Works for any domain — software, marketing, security, operations, design, writing, research, and more.

  Do NOT use for creating skills (use Skill Creator) or team composition (use Mission Planner).

Agent Creator

Creates structured agent definitions following the 7-component format. Every agent produced by this skill is grounded in persona science research, vocabulary routing mechanics, and the MAST failure taxonomy + Forge watchlist.

---

Expert Vocabulary Payload

**Agent Design:** role identity, domain vocabulary payload, deliverables, decision authority, standard operating procedure, anti-pattern watchlist, interaction model, handoff artifact, quality gate **Organizational Structure:** RACI matrix, task-relevant maturity (Andy Grove), blast radius, reporting lines, escalation path, out-of-scope boundary **Security & Risk:** STRIDE threat model, OWASP Top 10, attack surface, threat modeling (Shostack) **Persona Science:** persona alignment, alignment-accuracy tradeoff, role-task fit, persona-length effect, identity token budget **Vocabulary Mechanics:** vocabulary routing, distributional convergence, register steering, distribution center, 15-year practitioner test, sub-domain clustering, framework attribution

---

Anti-Pattern Watchlist

Flattery Persona

• **Detection:** Superlatives and absolutes in role identity — "world-class," "best," "always," "never," "unparalleled," "leading expert."
• **Why it fails:** No study isolates flattery inside personas against plain role statements. Forge bans superlatives as a style convention: they add tokens, add no scope information, and claim quality instead of defining behavior. Controlled studies show no accuracy benefit from expert personas generally (Zheng et al. 2024, arXiv:2311.10054; Wharton Prompting Science Report 4, 2025), and excessive flattery toward the model buys nothing (Yin et al. 2024, arXiv:2402.14531).
• **Resolution:** Define the role through knowledge and behavior, not quality claims. Remove every superlative. Describe what the agent knows and does, not how good it is.

Bare Role Label

• **Detection:** Identity is fewer than 10 tokens with no organizational context. Example: "You are a product manager."
• **Why it fails:** No boundary information means the agent will attempt anything remotely related to the title — nothing scopes what it owns, escalates, or leaves alone.
• **Resolution:** Add reporting lines, scope boundaries, and collaboration context. Specify the organizational unit and adjacent roles.

Verbose Identity

• **Detection:** Identity section exceeds 50 tokens or is a full paragraph of description.
• **Why it fails:** On knowledge-heavy tasks, damage grows with persona length (Hu, Rostami & Thomason 2026, arXiv:2603.18507: MMLU 71.6% no-persona → 68.0% at ~5 tokens → 66.3% at ~150 tokens). Forge keeps identities to ~20-50 tokens as a design convention, not a measured optimum. Attention budget consumed by persona processing instead of task execution.
• **Resolution:** Trim to title + primary responsibility + organizational context. Move detailed knowledge into the vocabulary payload, where it steers register and framing without consuming persona attention budget.

Missing Deliverables

• **Detection:** Role definition describes only behaviors and attitudes, no concrete artifacts. Nothing that could be verified as "produced" or "not produced."
• **Why it fails:** Without defined outputs, the agent has no completion criteria. It cannot self-assess whether its work is done or done correctly.
• **Resolution:** Every role produces specific named artifacts with format descriptions. Ask: "What does this person hand to the next person in the chain?"

Overlapping Authority

• **Detection:** Two agents in a team can both autonomously decide the same thing. Decision authority sections have intersection.
• **Why it fails:** Creates Role Overlap (Forge watchlist W-2; nearest MAST analog FM-1.2 Disobey Role Specification). Agents produce contradictory outputs or duplicate work. Neither knows the other has already decided.
• **Resolution:** Explicitly delineate — one agent decides, others advise. Use the RACI principle: exactly one Responsible, one Accountable per decision.

Generic Vocabulary

• **Detection:** Vocabulary payload contains consultant-speak — "best practices," "leverage," "synergy," "holistic approach," "robust solution," "paradigm shift."
• **Why it fails:** Generic terms are the distribution center — safe, universally-seen phrasing that dominates training data and reads as marketing copy, not domain expertise. The model produces fluent but non-specific output indistinguishable from a junior consultant's work.
• **Resolution:** Apply the 15-year practitioner test to every term. Replace each generic term with the precise term a senior practitioner would use with a peer. "Best practices for testing" becomes "mutation testing, property-based testing (QuickCheck), contract testing (Pact)."

Reasoning-Echo Instruction

• **Detection:** SOP or role identity instructs the agent to "show your reasoning," "think step by step and output your thoughts," "transcribe your internal reasoning," or similar.
• **Why it fails:** On current models, instructing an agent to echo or transcribe internal reasoning can trigger the reasoning-extraction refu