mcpField
A
agent-creator

agent-creator

github.com/fusengineAgent workflows3457 installsUpdated 1d ago
Repository

About agent-creator

A skill for scaffolding Claude Code expert agents, aimed at teams defining domain- or framework-specific agents. It supports new-agent creation, adaptation, and updates, and includes validation and marketplace registration guidance.

Key features

  1. 01Create and adapt agent definitions
  2. 02Configure frontmatter and workflows
  3. 03Add hook scripts
  4. 04Register agents in marketplace.json
  5. 05Validate generated agents

Use cases

  1. 01Creating an expert for a new framework
  2. 02Adapting an agent to another stack
  3. 03Updating an agent's skills or hooks
  4. 04Checking agent structure before registration

MCP support

The workflow calls mcp__context7__query-docs directly to look up agent examples and conventions. It also describes agents invoking tools such as Agent and SendMessage.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fusengine/claude-plugins --skill agent-creator

After installing, type/agent-creatorin Claude Code to confirm it loaded.

Details

From the project README
Agent Creator scaffolds a complete Claude Code expert agent: frontmatter (name, description, model, tools, skills, hooks), the mandatory Agent Workflow section, hook scripts, and marketplace registration. It covers three flows -- creating a brand-new domain/framework expert, adapting an existing agent to a new stack, and updating an agent's skills or hooks -- each ending with a `fuse-ai-pilot:sniper` validation pass.

It does not create the skills an agent references -- for that, use skill-creator; agent-creator only wires the agent frontmatter and workflow around skills that already exist or are created alongside it.

Agent Creator

Agent Workflow (MANDATORY)

Before ANY agent creation, delegate via Agent — spawn 2 agents in parallel (single message, 2 Agent calls). Generated agents carry Agent and SendMessage in their tools, so this same pattern is what they must use internally too:

  1. fuse-ai-pilot:explore-codebase - Check existing agents, analyze patterns
  2. fuse-ai-pilot:research-expert - Fetch latest agent conventions

mcp__context7__query-docs is a direct MCP call, not a spawned agent — invoke it directly (alongside the 2 Task calls) to get examples from existing agents.

After creation, run fuse-ai-pilot:sniper for validation.


Overview

ActionWhen to Use
New AgentNew domain/framework expert needed
AdaptCopy from similar agent (Next.js → React)
UpdateAdd skills, modify hooks

Critical Rules

  1. ALL content in English - Never French or other languages
  2. Frontmatter complete - name, description, model, tools, skills, hooks
  3. Agent Workflow section - Always first content section
  4. SOLID rules reference - Link to solid-[stack] skill
  5. Register in marketplace.json - Or agent won't load
  6. Hook scripts executable - chmod +x
  7. Output Format section mandatory - Every generated agent must define a standard ## Output Format section (status, files_changed, errors, sources) — an agent invoked by a lead must return structured data, not prose

Architecture

plugins/<plugin-name>/
├── agents/
│   └── <agent-name>.md      # Agent definition
├── skills/
│   ├── skill-a/
│   └── solid-[stack]/
├── scripts/
│   └── validate-*.sh        # Hook scripts
└── .claude-plugin/
    └── plugin.json

→ See architecture.md for details


Reference Guide

Concepts
TopicReferenceWhen to Consult
Architecturearchitecture.mdUnderstanding agent structure
Frontmatterfrontmatter.mdYAML configuration
Required Sectionsrequired-sections.mdMandatory content
Hookshooks.mdPre/Post tool validation
Registrationregistration.mdmarketplace.json
Templates
TemplateWhen to Use
agent-template.mdCreating new agent
hook-scripts.mdValidation scripts

Quick Reference

Create New Agent
# 1. Research existing agents
→ explore-codebase + research-expert

# 2. Create files
touch plugins/<plugin>/agents/<agent-name>.md
touch plugins/<plugin>/scripts/validate-<stack>-solid.sh
chmod +x plugins/<plugin>/scripts/*.sh

# 3. Register in marketplace.json

# 4. Validate
→ sniper
Adapt Existing Agent
# 1. Copy similar agent
cp plugins/nextjs-expert/agents/nextjs-expert.md plugins/new-plugin/agents/new-expert.md

# 2. Adapt with sed
sed -i '' "s/nextjs/newstack/g; s/Next\.js/NewStack/g" agents/new-expert.md

# 3. Update skills, tools, register

Validation Checklist

  • ALL content in English
  • Frontmatter complete (name, description, model, tools, skills)
  • Agent Workflow section present
  • Mandatory Skills Usage table
  • SOLID Rules reference to solid-[stack]
  • Local Documentation paths valid
  • Output Format section present (status, files_changed, errors, sources)
  • Hook scripts executable
  • Registered in marketplace.json

Related: Skill Creator

When creating an agent, you often need to create skills too.

Use /fuse-ai-pilot:skill-creator to create skills for the agent:

ScenarioAction
New agent needs skillsCreate skills with skill-creator first
Agent references skillsEnsure skills exist in skills/
Adapting agentAdapt related skills too

Best Practices

DO
  • Use skill-creator for associated skills
  • Reference solid-[stack] skill for SOLID rules
  • Include Gemini Design section for UI agents
  • Make hook scripts executable
DON'T
  • Write in French (English only)
  • Skip Agent Workflow section
  • Forget marketplace registration
  • Create agent without its skills
  • Hard-code paths in hooks (use $CLAUDE_PLUGIN_ROOT)

Comments

Markdown supported