init

Initialize Shipkit and configure MCP servers for a repository.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/nille/shipkit --skill init-nille
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: init
Source: https://github.com/nille/shipkit/tree/main/shipkit/core/skills/init
Command: npx skills add https://github.com/nille/shipkit --skill init-nille

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shipkit requires manual, multi-step setup for new projects. This skill automates initial project configuration by identifying tech stacks, proposing and applying MCP servers, and syncing the agent for immediate use.

Core Features & Use Cases

  • Detects project tech stack automatically and recommends MCP servers based on detected dependencies.
  • Configures and persists project-level MCP settings, and generates agent manifests for Claude Code integration.
  • Guides the user through a safe, repeatable init workflow with idempotent operations and clear progress.

Quick Start

Run the initialization workflow to auto-detect your project, configure MCPs, and generate the agent.

Frequently Asked Questions about init

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure MCP servers for a new project automatically?

To configure MCP servers automatically, run the initialization workflow to parse project state, detect the tech stack from config files, and write settings directly into .claude/mcp.json for immediate agent integration.

How do I auto-detect a project tech stack and set up Claude Code agents?

Auto-detect the tech stack by parsing common config files during initialization, which then generates a corresponding agent manifest in .claude/agents/shipkit.md to set up Claude Code agents.

What is the best way to re-sync an agent after changes in my tech stack?

The best way to re-sync an agent after tech stack changes is to re-run the idempotent initialization workflow, which safely reconfigures MCP servers and updates project-level settings.

Do I need to manually edit mcp.json when starting a new project?

No, manual editing is unnecessary. The initialization process identifies dependencies and automatically writes and persists the project-level MCP settings into the .claude/mcp.json file.

Can I use an automated init workflow to reconfigure MCP servers?

Yes, you can use the automated init workflow to reconfigure MCP servers. It applies safely when starting new projects or reconfiguring existing setups with clear progress and idempotent operations.