claude-code-skill-factory MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

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

Démo en direct

Aperçu en pratique

claude-code-skill-factory-skill.replay ▶ prêt

0/0

Installer

Choisissez votre 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
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.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 utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

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
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "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
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.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 utilise un tableau d'objets serveur plutôt qu'une 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"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

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

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : 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

Quand l'utiliser : You have a repeatable workflow in your head and want Claude to package it as an installable skill.

Prérequis

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

Déroulement

Invoke /build

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

→ 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.✓ Copié

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

/validate-output✓ Copié

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

/install-skill ./out/cwv-audit.zip✓ Copié

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

Résultat : A working, installed skill ready to trigger on the next matching prompt.

Pièges

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

Combiner avec : 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

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

Déroulement

Start Hooks Guide

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

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

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

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

/install-hook — user scope✓ Copié

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

Résultat : A hook that blocks secret-leaking writes before they happen.

Pièges

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

Combiner avec : 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

Quand l'utiliser : You want every teammate to get CO-STAR / RISEN-structured prompts without memorizing the frameworks.

Déroulement

Invoke Prompts Guide

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

→ 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.✓ Copié

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

Résultat : Team-shared prompt pack installable via one git clone.

Combiner avec : prompt-architect-skill

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

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.✓ Copié

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.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler	Coût
/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

Coût et limites

Coût d'exécution

Quota d'API: None — runs entirely inside Claude Code
Tokens par appel: 5k-20k tokens for a full build session
Monétaire: Free. Consumes your Claude subscription.
Astuce: Keep builder sessions focused — answer decisively to avoid expanding the conversation into rework.

Sécurité

Permissions, secrets, portée

Stockage des identifiants : No credentials. Skill Factory writes to ~/.claude/skills and ~/.claude/settings.json only.

Sortie de données : No outbound calls beyond Claude Code itself.

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

Dépannage

Erreurs courantes et correctifs

/build not recognized

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

Vérifier : 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.

Vérifier : cat ~/.claude/settings.json | jq .hooks

Alternatives

claude-code-skill-factory vs autres

Alternative	Quand l'utiliser	Compromis
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

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills