How do I install the Claude To Cursor skill?

Run npx skillmds@latest add scoobydont-666/claude-to-cursor in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Claude To Cursor safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Claude To Cursor?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Claude To Cursor free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Claude To Cursor?

scoobydont-666 (@scoobydont-666) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Claude To Cursor by scoobydont-666 — Agent Skill

Name: Claude To Cursor
Author: scoobydont-666

Claude To Cursor

Convert Claude Code skills to Cursor-compatible rules (.mdc/.md files) for sharing or use in Cursor workspaces. Does NOT modify local Claude Code setup — outputs go to a separate repo. Trigger on: "convert to cursor", "cursor rules", "port to cursor", ".mdc", "cursor format", or any request to export skills for Cursor users.

File contents

Claude to Cursor Converter

Export Claude Code skills as Cursor-compatible rule files for sharing. All output goes to a dedicated repo — never modifies local Claude Code configuration.

Cursor Rule Format (.mdc)

Cursor uses .mdc files (Markdown with frontmatter) in .cursor/rules/:

---
description: One-line description (used for rule matching)
globs:
  - "**/*.py"          # optional: file patterns this rule applies to
alwaysApply: false      # true = always loaded, false = matched by description
---

# Rule Title

Rule content here. Markdown format.

Key differences from Claude SKILL.md:

Extension: .mdc (not .md — Cursor's convention for rules)
No name: field — filename is the identifier
globs: for file-pattern matching (Claude uses description triggers)
alwaysApply: replaces Claude's always-loaded behavior
No references/ subdirectory convention — inline or split into companion rules

Conversion Process

1. Classify the skill

Type	Converts?	Notes
Persona (infosec-architect, cpa-tax-specialist)	Yes	Direct conversion, strong match
Workflow (tdd, write-a-prd, prd-to-plan)	Yes	Direct conversion
Code quality (code-consistency, code-quality)	Yes	Use globs for language-specific rules
Tool-specific (token-miser, budi-analytics)	No	Claude Code-only features
Infrastructure (fleet-manager, openclaw-ops)	Partial	Remove Claude-specific tool refs

2. Transform content

Strip YAML frontmatter, rewrite as Cursor frontmatter (description, globs, alwaysApply)
Remove Claude-specific tool references (Agent tool, Bash tool, Read/Write/Edit, MCP)
Inline small reference files (<200 lines) directly
Large references → separate .mdc companion files
Replace "Claude Code" with generic "AI assistant" where contextual
Add attribution:

3. Output structure

claude-to-cursor/
├── rules/                    # Converted .mdc files
│   ├── tdd.mdc
│   ├── tdd-tests-ref.mdc    # Large reference companion
│   ├── code-quality.mdc
│   └── ...
├── agents/                   # Converted agent files
│   └── ...
└── scripts/
    └── convert.sh            # Batch conversion script

4. What to skip

token-miser (Claude Code subagent routing — no Cursor equivalent)
budi-analytics (Claude Code hook analytics — Cursor-specific)
skill-updater (meta-skill for Claude Code skill management)
inbound-sync (claude.ai ↔ Claude Code sync workflow)
openclaw-ops (primary-host-specific deployment)
fleet-manager (SSH/Ansible fleet ops — not IDE-relevant)
ansible-hardening (infrastructure, not IDE-relevant)

Rules

NEVER modify local Claude Code skills or configuration
All output goes to the claude-to-cursor repo only
Keep attribution on all converted files
Test in Cursor before marking as ready
.mdc extension for rules, .md for agents

---name: claude-to-cursordescription: Convert Claude Code skills to Cursor-compatible rules (.mdc/.md files) for sharing or use in Cursor workspaces. Does NOT modify local Claude Code setup — outputs go to a separate repo. Trigger on: "convert to cursor", "cursor rules", "port to cursor", ".mdc", "cursor format", or any request to export skills for Cursor users.---# Claude to Cursor ConverterExport Claude Code skills as Cursor-compatible rule files for sharing. All outputgoes to a dedicated repo — never modifies local Claude Code configuration.## Cursor Rule Format (.mdc)Cursor uses `.mdc` files (Markdown with frontmatter) in `.cursor/rules/`:```markdown---description: One-line description (used for rule matching)globs: - "**/*.py" # optional: file patterns this rule applies toalwaysApply: false # true = always loaded, false = matched by description---# Rule TitleRule content here. Markdown format.```Key differences from Claude SKILL.md:- Extension: `.mdc` (not `.md` — Cursor's convention for rules)- No `name:` field — filename is the identifier- `globs:` for file-pattern matching (Claude uses description triggers)- `alwaysApply:` replaces Claude's always-loaded behavior- No `references/` subdirectory convention — inline or split into companion rules## Conversion Process### 1. Classify the skill| Type | Converts? | Notes ||---|---|---|| Persona (infosec-architect, cpa-tax-specialist) | Yes | Direct conversion, strong match || Workflow (tdd, write-a-prd, prd-to-plan) | Yes | Direct conversion || Code quality (code-consistency, code-quality) | Yes | Use globs for language-specific rules || Tool-specific (token-miser, budi-analytics) | No | Claude Code-only features || Infrastructure (fleet-manager, openclaw-ops) | Partial | Remove Claude-specific tool refs |### 2. Transform content1. Strip YAML frontmatter, rewrite as Cursor frontmatter (description, globs, alwaysApply)2. Remove Claude-specific tool references (Agent tool, Bash tool, Read/Write/Edit, MCP)3. Inline small reference files (<200 lines) directly4. Large references → separate `.mdc` companion files5. Replace "Claude Code" with generic "AI assistant" where contextual6. Add attribution: ``### 3. Output structure```claude-to-cursor/├── rules/ # Converted .mdc files│ ├── tdd.mdc│ ├── tdd-tests-ref.mdc # Large reference companion│ ├── code-quality.mdc│ └── ...├── agents/ # Converted agent files│ └── ...└── scripts/ └── convert.sh # Batch conversion script```### 4. What to skip- token-miser (Claude Code subagent routing — no Cursor equivalent)- budi-analytics (Claude Code hook analytics — Cursor-specific)- skill-updater (meta-skill for Claude Code skill management)- inbound-sync (claude.ai ↔ Claude Code sync workflow)- openclaw-ops (primary-host-specific deployment)- fleet-manager (SSH/Ansible fleet ops — not IDE-relevant)- ansible-hardening (infrastructure, not IDE-relevant)## Rules- NEVER modify local Claude Code skills or configuration- All output goes to the claude-to-cursor repo only- Keep attribution on all converted files- Test in Cursor before marking as ready- .mdc extension for rules, .md for agents

Frequently asked questions