claude-code-skill-factory MCP — Use Cases, Install & Live Demo

Why use it

Key features

5 interactive builders covering every Claude Code extension shape
/build slash command — end-to-end wizard for skills, agents, prompts, hooks
/validate-output — checks SKILL.md frontmatter, file layout, packages as ZIP
9 production-ready skills included out of the box
/sync-agents-md generates AGENTS.md for cross-tool compatibility (Cursor, Codex)
Templates based on 69+ preset prompt frameworks

Live Demo

What it looks like in practice

claude-code-skill-factory-skill.replay ▶ ready

0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "claude-code-skill-factory-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alirezarezvani/claude-code-skill-factory",
        "~/.claude/skills/claude-code-skill-factory"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "claude-code-skill-factory-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alirezarezvani/claude-code-skill-factory",
        "~/.claude/skills/claude-code-skill-factory"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "claude-code-skill-factory-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alirezarezvani/claude-code-skill-factory",
        "~/.claude/skills/claude-code-skill-factory"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "claude-code-skill-factory-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alirezarezvani/claude-code-skill-factory",
        "~/.claude/skills/claude-code-skill-factory"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "claude-code-skill-factory-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alirezarezvani/claude-code-skill-factory",
        "~/.claude/skills/claude-code-skill-factory"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "claude-code-skill-factory-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/alirezarezvani/claude-code-skill-factory",
          "~/.claude/skills/claude-code-skill-factory"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add claude-code-skill-factory-skill -- git clone https://github.com/alirezarezvani/claude-code-skill-factory ~/.claude/skills/claude-code-skill-factory

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use claude-code-skill-factory

How to build and package a new Claude Skill in 10 minutes

👤 Developers who want to ship a skill without hand-writing SKILL.md boilerplate ⏱ ~15 min beginner

When to use: You have a repeatable workflow in your head and want Claude to package it as an installable skill.

Prerequisites

Skill Factory installed — git clone https://github.com/alirezarezvani/claude-code-skill-factory ~/.claude/skills/claude-code-skill-factory

Flow

Invoke /build

/build — I want a skill that audits a Next.js app for Core Web Vitals issues and outputs a Lighthouse-style report.✓ Copied

→ Factory asks clarifying questions: triggers, tool categories, output format
Answer the scaffolding questions

Trigger on 'audit CWV' or Next.js project detected. Output markdown report with screenshots.✓ Copied

→ Draft SKILL.md with frontmatter, example usages, reference files
Validate and package

/validate-output✓ Copied

→ Green checks on frontmatter, directory structure, example completeness; ZIP produced
Install locally

/install-skill ./out/cwv-audit.zip✓ Copied

→ Skill appears in ~/.claude/skills and is discovered by Claude Code

Outcome: A working, installed skill ready to trigger on the next matching prompt.

Pitfalls

Skill triggers too aggressively on unrelated prompts — Tighten the 'description' in frontmatter — Claude uses it to decide when to load the skill
Example in SKILL.md drifts from actual behavior — /validate-output re-runs the example and flags mismatches

Combine with: skills-skill-2

Wire a pre-commit hook via the Hooks Guide

👤 Teams that want to automate Claude Code behavior on specific events ⏱ ~10 min intermediate

When to use: You want something to run automatically on prompt submit, tool use, or session stop — not a skill Claude has to choose to load.

Flow

Start Hooks Guide

/build hook — run gitleaks on every Write tool call before Claude saves secrets✓ Copied

→ Guide asks which event: PreToolUse/PostToolUse/Stop
Define matcher and command

Match Write tool calls, pipe file content through gitleaks detect, block on finding.✓ Copied

→ Draft settings.json hook block with matcher + command
Install into user settings

/install-hook — user scope✓ Copied

→ ~/.claude/settings.json updated; next tool call is gated

Outcome: A hook that blocks secret-leaking writes before they happen.

Pitfalls

Hook runs too slow and stalls every tool call — Move to PostToolUse if the check doesn't need to block

Combine with: claude-code-owasp-skill

Author a reusable prompt pack using research-backed frameworks

👤 Prompt engineers building consistent house prompts for a team ⏱ ~15 min beginner

When to use: You want every teammate to get CO-STAR / RISEN-structured prompts without memorizing the frameworks.

Flow

Invoke Prompts Guide

/build prompts — 5 presets for customer-support replies, CO-STAR structured✓ Copied

→ Guide lists available frameworks and asks which tone/role bias
Review and export

Export as a prompt-pack skill so the whole team can install via git clone.✓ Copied

→ Skill bundle with SKILL.md, prompts/ directory, README

Outcome: Team-shared prompt pack installable via one git clone.

Combine with: prompt-architect-skill

Combinations

Pair with other MCPs for X10 leverage

claude-code-skill-factory-skill + prompt-architect-skill

Prompt Architect tunes individual prompts; Skill Factory packages sets of them into a shareable skill

Have prompt-architect tighten these 5 prompts, then /build prompts and export as a skill pack.✓ Copied

claude-code-skill-factory-skill + skills-skill-2

Use Posit's skill collection as reference templates when building your own

Show me the structure of the Posit R-analysis skill, then /build a parallel Python-analysis skill modeled on it.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
/build	target: 'skill'\|'agent'\|'prompt'\|'hook', description: str	Top-level entry to create any new extension	interactive Claude session
/validate-output	path: str	Before distributing a skill	0
/install-skill	zip_or_path: str, scope?: 'user'\|'project'	After validate passes	0
/install-hook	hook_definition	After Hooks Guide produces a draft	0
/sync-agents-md	skill_path: str	Distributing across Cursor/Codex	0
/factory-status	-	Troubleshooting missing builders	0

Cost & Limits

What this costs to run

API quota: None — runs entirely inside Claude Code
Tokens per call: 5k-20k tokens for a full build session
Monetary: Free. Consumes your Claude subscription.
Tip: Keep builder sessions focused — answer decisively to avoid expanding the conversation into rework.

Security

Permissions, secrets, blast radius

Credential storage: No credentials. Skill Factory writes to ~/.claude/skills and ~/.claude/settings.json only.

Data egress: No outbound calls beyond Claude Code itself.

/install-hook modifies settings.json — review the generated hook before installing to user scope.

Troubleshooting

Common errors and fixes

/build not recognized

Skill Factory isn't loaded. Confirm clone path and that SKILL.md is at the repo root, not in a subfolder.

Verify: ls ~/.claude/skills/claude-code-skill-factory/SKILL.md

Generated ZIP fails /install-skill

Usually a frontmatter typo in SKILL.md. Run /validate-output first; it surfaces the exact missing field.

Hook produces no output after install

Matcher is too narrow. /factory-status shows which events are firing; widen the matcher in settings.json.

Verify: cat ~/.claude/settings.json | jq .hooks

Alternatives

claude-code-skill-factory vs others

Alternative	When to use it instead	Tradeoff
skills-skill-2 (Posit skills)	You just want ready-made skills, not a factory to build your own	No scaffolding, no hook builder
Hand-writing SKILL.md	You've already built several skills and know the shape	More control, slower, no validation

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills