Agent skill · Code Review & Quality

agent-creator

Creates specialized AI agents with optimized system prompts using the official 4-phase SOP methodology from Desktop .claude-flow, combined with evidence-based prompting techniques and Claude Agent SDK implementation. Use this skill when creating production-ready agents for specific domains, workflows, or tasks requiring consistent high-quality performance with deeply embedded domain knowledge.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill agent-creator-dnyoussef-ai-chrome-extension --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 19 KB
Bundled scripts: none
Path: skills/agent/agent-creator-dnyoussef-ai-chrome-extension/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Creator - Enhanced with 4-Phase SOP Methodology This skill provides the **official comprehensive framework** for creating specialized AI agents, integrating the proven 4-phase methodology from Desktop .claude-flow with Claude Agent SDK implementation and evidence-based prompting techniques. ## When to Use This Skill Use agent-creator for: - Creating project-specialized agents with deeply embedded domain knowledge - Building agents for recurring tasks requiring consistent behavior - Rewriting existing agents to optimize performance - Creating multi-agent workflows with sequential or parallel coordination - Agents that will integrate with MCP servers and Claude Flow ## The 4-Phase Agent Creation Methodology **Source**: Desktop `.claude-flow/` official SOP documentation **Total Time**: 2.5-4 hours per agent (first-time), 1.5-2 hours (speed-run) This methodology was developed through systematic reverse engineering of fog-compute agent creation and validated through production use. ### Phase 1: Initial Analysis & Intent Decoding (30-60 minutes) **Objective**: Deep domain understanding through systematic research, not assumptions. **Activities**: 1. **Domain Breakdown** - What pr

What's inside
Steps it walks through
  1. When to Use This Skill
  2. The 4-Phase Agent Creation Methodology
  3. Phase 1: Initial Analysis & Intent Decoding (30-60 minutes)
  4. Phase 2: Meta-Cognitive Extraction (30-45 minutes)
  5. Phase 3: Agent Architecture Design (45-60 minutes)
  6. Phase 4: Deep Technical Enhancement (60-90 minutes)
  7. Integrated Agent Creation Process
  8. Complete Workflow
  9. Claude Agent SDK Implementation
  10. TypeScript Implementation
  11. Python Implementation
  12. Agent Specialization Patterns
  13. Analytical Agents
  14. Generative Agents
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the agent-creator skill do?

Creates specialized AI agents with optimized system prompts using the official 4-phase SOP methodology from Desktop .claude-flow, combined with evidence-based prompting techniques and Claude Agent SDK implementation. Use this skill when creating production-ready agents for specific domains, workflows, or tasks requiring consistent high-quality performance with deeply embedded domain knowledge.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill agent-creator-dnyoussef-ai-chrome-extension --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going