Docs Claude Code skills
Use Edge and install skills in Claude Code
Connect Edge once, then ask Claude Code to find and load a skill for the task. For a skill you want to keep locally, put the reviewed folder under .claude/skills in the project or ~/.claude/skills for all your projects. Keep its supporting files beside SKILL.md.
No skill to install: Edge loads the right one per task.
How do I connect Edge?
Follow Edge setup for Claude Code: paste one prompt into Claude Code and it sets Edge up. To connect without installing anything, use the hosted connector below.
Pro: add your key to the connector first, then run setup.
claude mcp add edge -s user -e EDGE_KEY=edge_YOUR_KEY -- npx -y @getedge/mcp@0.6.58 npx -y @getedge/mcp@0.6.58 setup claude
Undo it with npx -y @getedge/mcp@0.6.58 setup claude --remove (the connector, the hook and the line). Free setup uses no Edge key. Read Edge setup for plans and data handling.
Can I add the connector by hand?
Yes, but a connector added by hand has no prompt hook and no instruction line, and Claude Code then calls Edge much less often. If you add it this way, run the setup command above afterwards: it keeps your entry and adds the rest.
claude mcp add edge -s user -- npx -y @getedge/mcp@0.6.58
Run claude mcp get edge to inspect the entry, then start a new session.
Can I connect without installing anything?
Yes, as a manual route. Edge also runs as a hosted HTTP MCP server at https://getedge.cc/mcp. Claude Code connects to it directly: no npm package, no Node.js, nothing downloaded. Like any connector added by hand, it adds no prompt hook or instruction line, and it cannot rank the skills installed on your machine. Free:
claude mcp add --transport http -s user edge https://getedge.cc/mcp
Pro: send your key as a header.
claude mcp add --transport http -s user edge https://getedge.cc/mcp --header "Authorization: Bearer edge_YOUR_KEY"
claude mcp get edge then shows Type: http and Status: Connected. Start a new session. To confirm the key, ask Claude to call Edge's health tool: it reports auth: pro, or auth: invalid when the key was not accepted (searches then run as Free). Remove the entry with claude mcp remove edge -s user.
The key is stored in your Claude Code user configuration (~/.claude.json), like any other MCP header.
Where do I keep a skill?
.claude/skills/my-skill/SKILL.md or ~/.claude/skills/my-skill/SKILL.md
A local skill can be selected with /my-skill. Project scope shares the folder through your repository; personal scope keeps it on this machine. Do not put user-authored skills inside the ~/.claude/skills/synced folder, which Claude Code manages.
Review a skill before adding it. Preserve its whole folder, including scripts, references and assets. Follow the skill selection guide to check its exact source and requirements.
How do I check that setup works?
Ask: Use Edge to find a skill for my task, show its source, and load it if it fits. Confirm an actual find_skill and use_skill result. Then try one small task and inspect the output. A visible configuration entry confirms setup syntax; it does not prove that a skill improves the result.
Sources, method and limits
Edge is our product. Checked 2026-10-02; hosted connector checked 2026-10-15. MCP add and resulting config readback validated in an isolated client config directory; the hosted command was also checked against the live endpoint (Connected, and a Pro key reported as auth: pro by the health tool); no model run. This guide uses client documentation and Edge setup instructions, without performance scores.