Documentation

Getting started with Claude Hub

Everything you need to know about skills, MCP integrations, and project context.

What are skills?

Skills are structured operational procedures for Claude — not prompt templates. Each skill:

•Reads your project context from memory.md and knowledge-base.md
•Follows a named framework with specific steps
•Produces a defined output format with quality validation
•Updates project memory with learnings after completion

Unlike a simple prompt, a skill encodes *how* to perform a task, not just *what* to ask for.

How to invoke a skill

Skills are invoked in two ways:

Automatic detection — Claude detects when a task matches a skill and applies it automatically. For example, asking "review this PR" will trigger the code review skill.

Manual invocation — Use the skill name as a slash command in Claude Code:

/code-review
/brand-audit
/financial-model

Or ask Claude directly: *"Use the accessibility-audit skill to..."*

Skill file structure

Each skill lives in its own directory with a SKILL.md file:

skills/
  development/
    accessibility-audit/
      SKILL.md
    api-design/
      SKILL.md

The SKILL.md contains: - Frontmatter — machine-readable description - Purpose — what the skill accomplishes - Inputs — required and optional parameters - Process — step-by-step instructions for Claude - Output format — expected deliverable structure - Quality checklist — validation before delivery

Project context integration

Skills automatically read two files when invoked:

memory.md — Persistent project state: current sprint, active decisions, known issues, team structure. Update this as the project evolves.

knowledge-base.md — Domain knowledge: architecture decisions, API contracts, business rules, glossary. Stable reference information.

Place these files in your project root. Skills will find them automatically and use the context to produce more relevant, project-specific output.

Setting up MCP integrations

MCP (Model Context Protocol) servers extend Claude with real-time access to external tools.

Claude Code — Add to ~/.claude/settings.json:

{
  "mcpServers": {
    "slack": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-slack"],
      "env": {
        "SLACK_BOT_TOKEN": "xoxb-..."
      }
    }
  }
}

Claude.ai — Go to Settings → Integrations and add the MCP server URL.

Each integration page on the MCP tab lists the exact configuration needed.

Quality standard

Every skill in the library meets a consistent quality bar:

Standard	Requirement
Actionable	Every step tells Claude exactly what to do
Specific	Concrete numbers, frameworks, and thresholds
Complete	Covers the full workflow from input to deliverable
System-aware	Integrates with memory, knowledge base, and audit trail
Validated	Includes quality checklist before delivery

Publishing a skill

Claude Hub is a marketplace. You can publish your own skills and MCP integrations for others to install.

How publishing works

Skills you publish are listed in the marketplace and can be installed by any Claude Hub user. You set the pricing — free, one-time, or subscription.

Submission requirements

•Skill must follow the standard SKILL.md template
•Description must be accurate and specific
•Skill must pass the quality checklist (actionable, specific, complete, validated)
•Category must match the skill's domain

To submit a skill for review, create an account and use the publisher dashboard. Skills are reviewed within 2 business days.