Skill not invoked — Claude uses its own defaults instead of init-project

Name the specific skill ('use init-project to scaffold...').

SKILL.md frontmatter wrong in a sub-skill

Each sub-skill has its own SKILL.md — inspect the specific folder.

skills — Installieren & Live-Demo

Warum nutzen

Hauptfunktionen

init-project scaffolds the directive files every serious AI project needs
auto-test-skill and auto-test-project run critical robustness tests on skill design
parallel-vibe runs alternative solutions in independent workspaces to compare
git-* skills automate conventional commits, PR review, and release notes
Targets Claude Code, Codex, and Cursor via the open Agent Skills standard

Live-Demo

In der Praxis

skills-skill-8.replay ▶ bereit

0/0

Installation

Repository des Autors · Offizielle Dokumentation zu Claude Skills

Anwendungsfälle

Praxisnahe Nutzung: skills

Author a new Claude skill and test it before publishing

👤 Developers who've built one-shot skills and want them actually reliable ⏱ ~60 min intermediate

Wann einsetzen: You have a draft SKILL.md and want it audited before sharing.

Ablauf

Scaffold with init-project

Use init-project to scaffold AGENTS.md and CLAUDE.md for my new skill project.✓ Kopiert

→ Directive files appear with sensible defaults
Polish the prompt with better-prompt

Run better-prompt on my SKILL.md body.✓ Kopiert

→ Clearer, more executable wording
Stress-test

Now auto-test-skill my SKILL.md — find weaknesses.✓ Kopiert

→ Failure modes named (vague triggers, missing examples, ambiguous steps)
Write the README

write-skill-readme for this skill.✓ Kopiert

→ README following convention

Ergebnis: A skill that passes its own tests before anyone else sees it.

Fallstricke

auto-test-skill flags everything and you fix nothing — Prioritize Critical + Warning; Suggestion-level is aspirational

Kombinieren mit: skillcheck-free-skill

Compare two implementation approaches with parallel-vibe

👤 Engineers stuck between two architectures ⏱ ~90 min advanced

Wann einsetzen: You can't decide between approach A and approach B and want to try both.

Ablauf

Describe both approaches

parallel-vibe: implement approach A (server-sent events) and approach B (polling) in separate workspaces. Same test suite.✓ Kopiert

→ Two independent workspaces with separate code and test results
Compare

Now compare — which is simpler to maintain and which is faster under load?✓ Kopiert

→ Honest tradeoff analysis grounded in both codebases

Ergebnis: A data-backed decision between two architectures.

Kombinationen

Mit anderen MCPs für 10-fache Wirkung

skills-skill-8 + skillcheck-free-skill

Cross-validate: auto-test-skill finds design weaknesses, SkillCheck validates spec compliance

Run auto-test-skill, then SkillCheck, then fix whatever either flags.✓ Kopiert

skills-skill-8 + github

git-pr-review + git-publish-release against real PRs and releases

Use git-pr-review on PR #47 then draft the release notes via git-publish-release.✓ Kopiert

Werkzeuge

Was dieses MCP bereitstellt

Werkzeug	Eingaben	Wann aufrufen	Kosten
init-project	project intent	First commit in a new project	0
better-prompt	draft prompt/instructions	Before shipping any prompt-heavy artifact	0
auto-test-skill	SKILL.md path	Before publishing a skill	0
parallel-vibe	N approaches + test criteria	When you genuinely can't pick an approach on paper	0 + LLM tokens for each branch
git-commit	diff intent	End of a unit of work	0
git-pr-review	PR number or diff	Reviewing a PR you're assigned	0

Kosten & Limits

Was der Betrieb kostet

API-Kontingent: None
Tokens pro Aufruf: parallel-vibe can be expensive — runs multiple solution attempts
Kosten in €: Free — skills are local files
Tipp: Use parallel-vibe sparingly; it multiplies your token spend by N branches.

Sicherheit

Rechte, Secrets, Reichweite

Credential-Speicherung: No credentials — pure prompts. git-* skills use your local git config.

Datenabfluss: None from skills themselves; git-* may push to remotes you configure.

Fehlerbehebung

Häufige Fehler und Lösungen

Wrong trigger keywords — git-commit doesn't activate

Say 'use git-commit' explicitly; 'commit' alone is too generic.

Alternativen

skills vs. andere

Alternative	Wann stattdessen	Kompromiss
skillcheck-free-skill	You want spec validation rather than robustness testing	Narrower scope, higher specificity to the agentskills spec
skills-skill-9 (tenequm)	You want broader product-building skills, not just skill authoring	Less meta — more domain skills

Mehr

Ressourcen

📖 Offizielle README auf GitHub lesen

🐙 Offene Issues ansehen

🔍 Alle 400+ MCP-Server und Skills durchsuchen