Skip to main content
All docs

Install a skill

Three ways to install an Edaskills skill — ZIP download, the edaskills CLI, or MCP from your agent.

Install a skill

Every Edaskills skill ships as a versioned ZIP containing SKILL.md, reference documents, scripts and (when a demo run was executed) its report. You can install it three ways. Pick the one that matches how you work.

1. Download the ZIP (web)

On any skill detail page, open the ZIP tab and download the package. The ZIP keeps the versioned outer directory (<slug>-<version>/) so you can archive it manually. Download requires a signed-in account; guests are redirected to login and returned to the same page.

The ZIP tab also shows the package checksum (sha256) and size so you can verify what you downloaded.

2. Install with the CLI

The CLI downloads, verifies the checksum, safely extracts, flattens the version directory and lands the skill where your agent reads it. It works without a web login.

npx edaskills install <slug>

Pin a version and target a specific agent:

npx edaskills install <slug>@1.0.0 --agent claude_code

Useful flags:

  • --agent <claude_code|cursor|codex|gemini_cli> — choose the host adapter.
  • --dir <path> — install into a project directory instead of the user level.
  • --no-demo — skip the demo-run/ artifacts.
  • --yes — skip the pointer-file diff confirmation (for CI).

The CLI never silently overwrites your files. If the target directory exists it stops and suggests edaskills update; both update and --force back up the old directory (.bak-…) before writing. Uninstall removes only the directories recorded in ~/.edaskills/installed.json.

See the per-agent guides for exactly where each host reads the skill:

3. Install from your agent (MCP)

Edaskills exposes a remote MCP endpoint at https://edaskills.com/api/v1/mcp. Your agent can discover skills, read their content and request an install plan. MCP does not write to your disk — it returns a plan and a one-time download link; the CLI (or you) performs the actual landing.

Create an API key under Settings → API keys and pass it as a Bearer token via the EDASKILLS_API_KEY environment variable. Never put a plaintext key in a config file or commit it to a repository.

Claude Code (.mcp.json) and Cursor (mcp.json) accept a direct HTTP config:

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

Stdio-only hosts (for example Claude Desktop) bridge through mcp-remote:

npx -y mcp-remote https://edaskills.com/api/v1/mcp \
  --header "Authorization: Bearer ${EDASKILLS_API_KEY}"

The --header value contains a space, so quote it as a whole. ${EDASKILLS_API_KEY} is expanded by the host environment.

A note on verification badges

A host compatibility badge means the skill's demo run actually executed on that host. No host has a recorded demo run yet, so skills currently carry no host badge. The install conventions above describe what the Edaskills CLI does today; they are not a claim that a given host has been tested end to end.