Skip to main content
All docs

Claude Code

Install Edaskills skills into Claude Code — native SKILL.md directory and .mcp.json MCP config.

Claude Code

Claude Code reads skills natively from a skills directory: each skill is a folder containing SKILL.md. No pointer file is needed.

Install with the CLI

User level (available in every project):

edaskills install <slug> --agent claude_code

This lands the skill at ~/.claude/skills/<slug>/. For a project-level install:

edaskills install <slug> --agent claude_code --dir ./.claude/skills

The CLI flattens the versioned outer directory, so the result is <dest>/<slug>/SKILL.md plus its references and scripts. If the target directory already exists it stops and suggests edaskills update, which backs up the old directory before writing.

Verify the landing:

ls ~/.claude/skills/<slug>/SKILL.md

Then open Claude Code and confirm the skill is recognized.

MCP config

Claude Code reads .mcp.json and supports a direct HTTP MCP server. Create an API key under Settings → API keys, export it as EDASKILLS_API_KEY, and add:

{
  "mcpServers": {
    "edaskills": {
      "type": "http",
      "url": "https://edaskills.com/api/v1/mcp",
      "headers": {
        "Authorization": "Bearer ${EDASKILLS_API_KEY}"
      }
    }
  }
}

${EDASKILLS_API_KEY} is expanded from the environment — never commit a plaintext key. Through MCP the agent can discover skills, read content and request an install plan; MCP does not write to disk.

Verification status

The directory convention above is what the Edaskills CLI does today. A "verified on Claude Code" badge would require an actual demo run executed on this host; none is recorded yet, so no host badge is shown.

See also: Install a skill.