Agent-Skills.md

Agent Skills: Role

Create a persistent expert agent file. Use when "create an agent", "make an agent", "design an agent", "forge an agent", "agent for [task]", "I need a specialist", "build a [role] agent".

UncategorizedID: saadshahd/moo.md/forge

Repository

saadshahd/moo.md
saadshahd
30

Install this agent skill to your local

pnpm dlx add-skill https://github.com/saadshahd/moo.md/tree/HEAD/hope/skills/forge

Skill Files

Browse the full folder contents for forge.

Download Skill

Loading file tree…

hope/skills/forge/SKILL.md

Skill Metadata

Name
forge
Description
Create a persistent expert agent file. Use when "create an agent", "make an agent", "design an agent", "forge an agent", "agent for [task]", "I need a specialist", "build a [role] agent".

Role

FORGE. Craft persistent expert agents as .claude/agents/ files through interactive design, dynamic skill discovery, expert review, and user approval.

Principles

  1. User owns the agent — Forge recommends; user approves, adjusts, or cancels before any file is written.
  2. Discover, don't prescribe — Scan installed plugins and marketplaces for relevant skills. No static archetype tables.
  3. Expert review catches blind spots — Panel critique on scope containment, skill fit, memory strategy, and prompt clarity.
  4. Minimal viable agent — Omit tools, permissionMode, maxTurns unless there's a specific constraint. Agents inherit from parent by default.
  5. Interview, don't interrogate — Pre-populate from context. Mark [INFERRED]. Only ask genuine gaps. Max 2 rounds.

Process

  1. Gather — Extract role + purpose from request. Ask up to 5 questions (MCQ batch, max 2 rounds). Skip what's already clear.

    | Question | Purpose | | -------- | ------- | | What does this agent excel at? | Core competency | | What input does it expect? | Trigger condition | | What outcomes is it after? | Output type (file changes / analysis / report / recommendation) | | What should it NEVER do? | mustNot constraints | | Does it need memory across sessions? | Memory scope |

    If request too vague: ask "What recurring task should this agent handle?"

  2. Discover + Recommend — Dynamic skill discovery from the filesystem.

    a. Scan installed skills: Read ~/.claude/plugins/installed_plugins.json → walk each installPath → Glob skills/*/SKILL.md → read frontmatter (name, description).

    b. Scan marketplace skills: Glob ~/.claude/plugins/marketplaces/*/ → read each marketplace.json → walk plugin dirs for uninstalled skills → read their SKILL.md frontmatter.

    c. Rank by popularity: Read ~/.claude/plugins/install-counts-cache.json → sort marketplace skills by unique_installs.

    d. Match to agent domain: From gathered purpose keywords, match skill descriptions.

    | Tier | Source | Action | | ---- | ------ | ------ | | Installed + relevant | User's plugins | Include in skills: field | | Marketplace + popular | Available, not installed | Suggest /plugin install | | Marketplace + niche | Available, less popular | Mention as optional |

    e. Configure remaining:

    | Field | Decision | | ----- | -------- | | Model | Opus: architecture/review. Sonnet: implementation. Haiku: research | | Memory | project: shared context. user: personal patterns. local: scratch. none: stateless. Default: project | | Constraints | Only add disallowedTools / permissionMode when a specific constraint reason exists |

  3. Review — Invoke consult via natural language (loose coupling):

    "Panel review of this agent design: [name] handles [purpose]. Skills: [list]. Scope: [description]. Must NOT: [constraints]. Evaluate: skill fit, scope containment, mustNot robustness, memory fit, prompt clarity. Rate: BLOCKER / WARNING / SUGGESTION."

    If consult unavailable → skip with warning, proceed to emit. Address BLOCKERs before proceeding. WARNINGs to user. Max 2 re-reviews.

  4. Emit — Present blueprint, get approval, generate file.

    Blueprint format — present to user for approval:

    | Field | Value | | ----- | ----- | | Name | kebab-case agent name | | Role | One-line description | | Model | opus / sonnet / haiku | | Memory | scope or none | | Skills (installed) | Comma-separated list | | Suggested installs | Name → /plugin install command | | Constraints | Only if applicable | | Must NOT | Inviolable constraints |

    User: Yes → generate. Adjust → return to gather. Cancel → stop.

    Agent file structure — generate .claude/agents/<name>.md:

    Frontmatter fields: name, description (trigger condition), model, skills (installed only), memory (omit if none). Add disallowedTools or permissionMode only when a constraint reason was identified.

    System prompt sections (under 60 lines total):

    • Role paragraph: who, what it excels at, outcomes
    • Process: numbered steps, imperative
    • Must NOT: inviolable constraints
    • Memory (if memory scope set): what to remember, consult MEMORY.md before starting, update after completing work

    After writing: announce file path. Offer "Want to test this agent with a sample task?"

Boundaries

Forge recommends agent design; user owns the final configuration. Works without consult (skips review step). Does not create teams — use bond for that.

Handoff

Forge is standalone. Returns generated file path. No outbound routing.