agent-factory_skill

This skill automates creation of production-ready Claude Code agents with enhanced frontmatter, tool patterns, and MCP integration.
  • Python

388

GitHub Stars

5

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill alirezarezvani/claude-code-skill-factory --skill agent-factory

  • agent_generator.py8.0 KB
  • expected_output.json1.9 KB
  • HOW_TO_USE.md9.1 KB
  • sample_input.json1.3 KB
  • SKILL.md8.0 KB

Overview

This skill generates production-ready Claude Code agents and sub-agents with enhanced YAML frontmatter, tool access guidance, and MCP integration support. It provides consistent templates and validation to accelerate building, deploying, and discovering Claude agents across projects. The output is a single markdown agent file ready to install into .claude/agents or a personal agents directory.

How this skill works

Fill a simple prompt template with agent name, description, domain, tools, and MCP integrations, then run the template through Claude Code to produce a fully formed .md agent file. The generator injects rich YAML metadata (color, field, expertise, model, mcp_tools), enforces tool-access patterns, assigns safe execution patterns (parallel vs sequential), and validates the configuration against best practices. Generated agents reference recommended MCP servers when available and include checklists, invocation hints, and an output format to make them immediately usable.

When to use it

  • Creating domain-specific agents (frontend, backend, data, security) for team workflows
  • Standardizing agent metadata and discovery across multiple projects
  • Prototyping multiple related agents quickly with consistent patterns
  • Integrating agents with MCP servers like mcp__github or mcp__playwright
  • Defining safe execution patterns to avoid parallelization issues

Best practices

  • Keep each agent focused on a single responsibility to enable safe parallelization
  • Use descriptive names and detailed descriptions so Claude can auto-invoke correctly
  • Match tool sets to agent type: strategic (Read/Write/Grep), implementation (full tools), quality (sequential, heavy Bash)
  • Specify execution patterns explicitly to prevent resource contention
  • Test agents incrementally and version control agent files in git

Example use cases

  • Generate a product-planner (strategic) agent that runs in parallel with research agents
  • Create frontend-developer and backend-developer implementation agents with coordinated execution
  • Produce a test-runner quality agent configured to run sequentially and access Bash for CI tasks
  • Build a fullstack-coordinator to orchestrate other agents and validate integration
  • Scaffold api-integration-specialist with mcp__github and mcp__playwright integrations

FAQ

No. Generation creates markdown agent files. Install them into .claude/agents or ~/.claude/agents and ensure your Claude Code runtime discovers them before invocation.

What if my environment lacks MCP servers?

MCP integrations are optional. Generated agents include mcp_tools metadata as recommendations; they will work without MCP servers but gain capabilities only after server configuration.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
agent-factory skill by alirezarezvani/claude-code-skill-factory | VeilStrat