Cursor
Install Edaskills skills into Cursor — skill directory plus a .cursor/rules pointer and mcp.json config.
Cursor
Cursor does not read a SKILL.md directory natively; it reads rules from
.cursor/rules/*.mdc. The Edaskills CLI therefore lands the skill files and writes
a small pointer rule that tells Cursor when to read them.
Install with the CLI
edaskills install <slug> --agent cursor
This does two things:
- Lands the skill at
~/.edaskills/skills/<slug>/(flattened, with references and scripts). - Creates a pointer rule at
<repo>/.cursor/rules/edaskills-<slug>.mdcwithdescriptionandalwaysApply: falsefrontmatter. The rule says: when a task matches<slug>, read<path>/SKILL.mdand follow its instructions.
The pointer write shows a diff and asks for confirmation first; pass --yes to
skip the prompt in CI. Existing rule content is never overwritten. If the skill
directory already exists the CLI stops and suggests edaskills update, which backs
up the old directory before writing.
MCP config
Cursor reads mcp.json and accepts a URL-based MCP server. Create an API key under
Settings → API keys, export it as EDASKILLS_API_KEY, and add:
{
"mcpServers": {
"edaskills": {
"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. MCP lets the agent discover skills, read content and request an install plan;
it does not write to disk.
Verification status
The pointer-rule convention above is what the Edaskills CLI does today. A "verified on Cursor" 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.