Everything Claude Code (Claude Skill) — Use Cases, Install & Live Demo

Why use it

Key features

Research-first development discipline (prove understanding before writing)
Persistent memory + handoff patterns
Security defaults (no shell unless asked, no creds in chat)
Multi-harness compatible (Claude Code, Codex, OpenCode, Cursor)
Active maintenance, large community

Live Demo

What it looks like in practice

ready

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "everything-claude-code-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/affaan-m/everything-claude-code",
        "~/.claude/skills/everything-claude-code"
      ],
      "_inferred": true
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "everything-claude-code-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/affaan-m/everything-claude-code",
        "~/.claude/skills/everything-claude-code"
      ],
      "_inferred": true
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "everything-claude-code-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/affaan-m/everything-claude-code",
        "~/.claude/skills/everything-claude-code"
      ],
      "_inferred": true
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "everything-claude-code-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/affaan-m/everything-claude-code",
        "~/.claude/skills/everything-claude-code"
      ],
      "_inferred": true
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "everything-claude-code-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/affaan-m/everything-claude-code",
        "~/.claude/skills/everything-claude-code"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json

{
  "context_servers": {
    "everything-claude-code-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/affaan-m/everything-claude-code",
          "~/.claude/skills/everything-claude-code"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add everything-claude-code-skill -- git clone https://github.com/affaan-m/everything-claude-code ~/.claude/skills/everything-claude-code

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Everything Claude Code

Bootstrap a new project with strong defaults for any coding agent

👤 Tech leads setting team standards ⏱ ~30 min intermediate

When to use: You're starting a project and you want every agent (yours and your team's) to behave the same way.

Prerequisites

Skills directory exists — mkdir -p ~/.claude/skills if not already

Flow

Install

Clone everything-claude-code. List the skill modules and their purposes.✓ Copied

→ Module inventory with descriptions
Trim

Disable modules I don't need (e.g., crypto). Keep research-first, memory, security.✓ Copied

→ Pruned skill set
Validate

Run a sample prompt that should trigger research-first behavior. Confirm it does.✓ Copied

→ Agent gathers context before writing

Outcome: Every agent on the project starts with the same opinionated defaults.

Pitfalls

Skill conflicts with team's existing CLAUDE.md — Order matters — project CLAUDE.md takes precedence; reconcile explicitly

Combine with: filesystem

Add security and memory patterns to an existing setup

👤 Devs who've been improvising agent config ⏱ ~45 min intermediate

When to use: Your agent has been useful but inconsistent — sometimes shell-happy, sometimes forgetful.

Flow

Audit

Compare my current CLAUDE.md vs everything-claude-code's recommended skeleton. Highlight gaps.✓ Copied

→ Gap list with rationale
Adopt

Pull in the security and memory modules only. Diff what would change.✓ Copied

→ Diff to review

Outcome: Same agent, more reliable behavior.

Pitfalls

Adopting the whole kit changes too much at once — Per-module adoption; verify each before next

Combinations

Pair with other MCPs for X10 leverage

everything-claude-code-skill + git-mcp-idosal

Research-first + always-fresh repo source

Research-first via everything-claude-code; pull library source via GitMCP.✓ Copied

everything-claude-code-skill + claude-best-practice-skill

Layer two opinionated skill kits with conflict resolution

Adopt shanraisshan/claude-code-best-practice on top; resolve conflicts in CLAUDE.md.✓ Copied

Tools

What this MCP exposes

Tool	Inputs	When to call	Cost
research_first	task description	Default — before changes	tokens for the research step
memory_handoff	session summary	End of session	tokens
security_lint	diff	Before commit	tokens

Cost & Limits

What this costs to run

API quota: N/A
Tokens per call: Higher per-task (research adds context) but fewer total iterations
Monetary: Free
Tip: Adopt incrementally — measure before/after token spend per task type

Security

Permissions, secrets, blast radius

Minimum scopes: Read access to project workspace

Credential storage: Per-host (the skill itself stores no creds)

Data egress: None (skill is local config)

Big bundles can pull behavior surprises — review modules you enable

Troubleshooting

Common errors and fixes

Skills directory not picked up

Confirm path is ~/.claude/skills/<name> and the manifest is loaded by your harness

Verify: Restart agent; check skill list

Conflicting CLAUDE.md guidance

Resolve precedence — project > user > skill

Token spend went up

Disable modules you don't need; research-first is heaviest

Alternatives

Everything Claude Code vs others

Alternative	When to use it instead	Tradeoff
claude-best-practice-skill	You want a different opinionated bundle	Different philosophy; same general goal
Hand-written CLAUDE.md	You want minimal surface	More effort to maintain

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills