Skip to content
Claudekit.ai

Pillar guide

Claude Kit: What It Is and How to Build Yours

Everything that belongs in a Claude kit — the apps, the agentic coding setup, Skills, MCP servers and prompts — with links to the best free resources and the leading ready-made kit.

Last updated · By Claudekit Team

What is a Claude kit?

A Claude kit is the toolbox you assemble around Claude so it can do real work for you: the surface you use it from, the context it starts with, the reusable instructions it can call on and the systems it can reach. Two developers using the same Claude model can get very different results — the difference is almost always the kit.

Some people buy a ready-made kit; most combine free building blocks. This page covers both, and every section links into the Claudekit library so you can go deeper.

Claudekit.cc is now Agentkit.best

If you searched for “Claudekit.cc”, you were probably looking for the commercial starter kit that used to live at claudekit.cc. It is now Agentkit.best (formerly Claudekit.cc), at agentkit.best. It bundles pre-built Claude Code agents, Skills, commands and workflows so you can skip most of the setup below. Our Agentkit.best guide covers what you get, the price and who should skip it.

Check out Agentkit.best (affiliate link — see our disclosure). Claudekit.ai is a separate, independent library and is not the same product.

The building blocks

1. Where you use Claude

Claude.ai (web, desktop and mobile) is best for chat, research and Projects with shared files. Claude Code is the agentic coding tool that works directly in your terminal and repository. The Claude API is for building Claude into your own products. See the guides for setup walkthroughs.

2. Context: project memory

Claude Code reads a CLAUDE.md file for project instructions — your stack, conventions and the commands to build and test. A short, accurate memory file is the cheapest upgrade any kit can get.

3. Skills

Skills are folders of instructions, scripts and resources that Claude loads only when a task needs them. They turn a long prompt you keep re-pasting into a reusable capability. Browse the Skills directory.

4. MCP servers

The Model Context Protocol (MCP) is an open standard for connecting Claude to tools and data — GitHub, databases, browsers, docs and internal APIs. Add only the servers you need. Browse MCP servers.

5. Prompts

Even with Skills, a good prompt library pays off for one-off tasks. Keep the ones that work, note the model they were tested on, and retire them when models change. Browse the prompt library.

6. Agents and automation

Claude Code supports subagents, hooks and custom slash commands for multi-step workflows. Starter kits mostly package these pieces. Compare options on the comparison pages.

Build your own kit in 6 steps

  1. Pick your surface: Claude.ai for chat and Projects, Claude Code for agentic coding in the terminal, or the Claude API for your own apps.
  2. Write a project memory file (CLAUDE.md for Claude Code) with your stack, conventions and commands so every session starts with context.
  3. Add a few Skills for repeat workflows — code review, release notes, docs — instead of re-pasting long prompts.
  4. Connect the MCP servers you actually need (GitHub, your database, docs search) and nothing more; each one widens what Claude can touch.
  5. Save the prompts that work into a shared library with the model they were tested on.
  6. Review monthly: remove stale skills and servers, update prompts for new models, and check the news for breaking changes.

Starter picks from the library

Start with these guides

See all →

Popular Skills

See all →

MCP servers worth installing

See all →
Tool MCP Server

Apify MCP Server: Run Web Scrapers from Claude

Apify's official MCP server lets Claude find and run Actors from Apify Store to scrape sites, maps and social media. Claude Code plugin, OAuth, caveats.

★ 12,930

Ready-made kits

See all →

Comparisons

See all →

Frequently asked questions

What is a Claude kit?

A Claude kit is the set of tools, configuration and reusable assets you use to work with Claude effectively: usually Claude Code, a project memory file, Skills, MCP servers, prompt templates and sometimes a ready-made starter kit of agents and workflows.

What happened to Claudekit.cc?

Claudekit.cc, the commercial starter kit, changed its name to Agentkit.best and now lives at agentkit.best. Claudekit.ai is a separate, independent community resource library and is not the same product.

Is Claudekit.ai made by Anthropic?

No. Claudekit.ai is an independent community project. It is not affiliated with, endorsed by, or sponsored by Anthropic. Claude is a trademark of Anthropic, PBC.

Do I need a paid kit to use Claude Code well?

No. Everything a kit contains can be assembled from free and open-source pieces: Skills, MCP servers and prompts listed in this library. A paid kit mainly saves setup time by bundling a curated, pre-configured set.

What is the difference between a Skill and an MCP server?

A Skill packages instructions, scripts and resources that Claude loads when a task calls for them. An MCP server is a separate process that exposes tools and data to Claude over the Model Context Protocol. Skills teach Claude how to do something; MCP servers give it access to systems.

Get the weekly Claude digest

New skills, MCP servers, prompts and Claude updates — one short email a week. No spam, unsubscribe anytime.

The newsletter is launching soon. Follow the RSS feed in the meantime.