claude-code-skill-factory — Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

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

In der Praxis

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

0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: 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

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

Ablauf

Invoke /build

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

→ 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.✓ Kopiert

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

/validate-output✓ Kopiert

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

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

Fallstricke

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

Kombinieren mit: 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

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

Ablauf

Start Hooks Guide

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

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

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

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

/install-hook — user scope✓ Kopiert

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

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

Fallstricke

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

Kombinieren mit: 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

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

Ablauf

Invoke Prompts Guide

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

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

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

Kombinieren mit: prompt-architect-skill

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

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.✓ Kopiert

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.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
/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

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None — runs entirely inside Claude Code
Tokens pro Aufruf: 5k-20k tokens for a full build session
Kosten in €: Free. Consumes your Claude subscription.
Tipp: Keep builder sessions focused — answer decisively to avoid expanding the conversation into rework.

Sicherheit

Rechte, Secrets, Reichweite

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

Datenabfluss: No outbound calls beyond Claude Code itself.

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

Fehlerbehebung

Häufige Fehler und Lösungen

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.

Prüfen: cat ~/.claude/settings.json | jq .hooks

Alternativen

claude-code-skill-factory vs. andere

Alternative	Wann stattdessen	Kompromiss
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

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen