mcpField
C
claudekit

claudekit

github.com/akillnessAgent workflows53252 installsUpdated 4d ago
Repository

About claudekit

claudekit is an opinionated Claude Code plugin that provides reusable skills and agents plus an interactive setup wizard. It helps teams establish project-level rules, modes, hooks, and MCP scaffolding, with generated defaults intended for review.

Key features

  1. 01Reusable skills and agents
  2. 02Interactive setup wizard
  3. 03Project-level rules and modes
  4. 04Hook and settings scaffolding
  5. 05MCP configuration scaffolding

Use cases

  1. 01Bootstrapping a new repository
  2. 02Applying selected hooks and rules to an existing project
  3. 03Standardizing Claude Code workflows across teammates

MCP support

claudekit can scaffold project MCP configuration by generating `.mcp.json`. The README does not specify server connection or management capabilities.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/akillness/jeo-skills --skill claudekit

After installing, type/claudekitin Claude Code to confirm it loaded.

Bundled filesSKILL.toon

Details

From the project README

claudekit — Claude Code workflow toolkit

claudekit is an opinionated Claude Code plugin that bundles reusable skills/agents and an interactive setup wizard.

When to use this skill

  • You want project-level rules/modes/hooks/MCP scaffolding quickly.
  • You need repeatable Claude Code workflows across teammates.
  • You want a curated starter set of planning/review/build skills.

Instructions

  1. Add marketplace and install plugin: 
    /plugin marketplace add duthaho/claudekit-marketplace
/plugin install claudekit
  2. Run setup wizard: 
    /claudekit:init
# or full setup
/claudekit:init --all
  3. Verify generated files exist:
    • .claude/rules/
    • .claude/modes/
    • .claude/hooks/ + settings.local.json
    • .mcp.json
  4. Review generated defaults before commit; keep project-specific policies explicit.

Examples

  • New repo bootstrap: /claudekit:init --all 후 초기 workflow 패키지 생성.
  • Existing repo hardening: hooks/rules 일부만 선택 설치해 점진 도입.

Best practices

  • Generated hook/rule를 그대로 신뢰하지 말고 팀 정책과 충돌 여부를 먼저 검토.
  • 스킬/플러그인 업데이트는 릴리즈 노트 확인 후 반영.
  • claudekit은 가속기이며, 저장소별 검증 게이트(test/lint/review)를 대체하지 않는다.

References

Comments

Markdown supported