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 — インストール & ライブデモ

なぜ使うのか

主な機能

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

ライブデモ

実際の動作

skills-skill-8.replay ▶ 準備完了

0/0

インストール

作者のリポジトリ · Claude Skills の公式ドキュメント

ユースケース

実用的な使い方： 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

使うタイミング： You have a draft SKILL.md and want it audited before sharing.

フロー

Scaffold with init-project

Use init-project to scaffold AGENTS.md and CLAUDE.md for my new skill project.✓ コピーしました

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

Run better-prompt on my SKILL.md body.✓ コピーしました

→ Clearer, more executable wording
Stress-test

Now auto-test-skill my SKILL.md — find weaknesses.✓ コピーしました

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

write-skill-readme for this skill.✓ コピーしました

→ README following convention

結果： A skill that passes its own tests before anyone else sees it.

注意点

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

組み合わせ： skillcheck-free-skill

Compare two implementation approaches with parallel-vibe

👤 Engineers stuck between two architectures ⏱ ~90 min advanced

使うタイミング： You can't decide between approach A and approach B and want to try both.

フロー

Describe both approaches

parallel-vibe: implement approach A (server-sent events) and approach B (polling) in separate workspaces. Same test suite.✓ コピーしました

→ Two independent workspaces with separate code and test results
Compare

Now compare — which is simpler to maintain and which is faster under load?✓ コピーしました

→ Honest tradeoff analysis grounded in both codebases

結果： A data-backed decision between two architectures.

組み合わせ

他のMCPと組み合わせて10倍の力を

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.✓ コピーしました

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.✓ コピーしました

ツール

このMCPが提供する機能

ツール	入力	呼び出すタイミング	コスト
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

コストと制限

運用コスト

APIクォータ: None
呼び出しあたりのトークン: parallel-vibe can be expensive — runs multiple solution attempts
金額: Free — skills are local files
ヒント: Use parallel-vibe sparingly; it multiplies your token spend by N branches.

セキュリティ

権限、シークレット、影響範囲

認証情報の保管： No credentials — pure prompts. git-* skills use your local git config.

データ送信先： None from skills themselves; git-* may push to remotes you configure.

トラブルシューティング

よくあるエラーと対処法

Wrong trigger keywords — git-commit doesn't activate

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

代替案

skills 他との比較

代替案	代わりに使う場面	トレードオフ
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

その他

リソース

📖 GitHub の公式 README を読む

🐙 オープンな issue を見る

🔍 400以上のMCPサーバーとSkillsを見る