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: "co
SKILL.mdskills/claude-to-cursor/SKILL.md
GitHubClaude to Cursor
Inspect the selected skill, bundled resources and destination's existing rules. Use the requested output repository or directory; preserve source configuration and unrelated destination content. Review private paths, contacts and tool assumptions before sharing a rule.
Conversion
- Retain portable instructions and replace tool-specific calls with capabilities actually available in the target client. Do not discard general workflows just because their source used Claude tools. Token budgeting and evidence-based review, for example, remain portable.
- Write focused
.mdcproject rules in.cursor/rules/. Use a description for agent-selected relevance, globs for file-specific rules, oralwaysApply: trueonly when the user intends the rule to apply to every conversation. - Keep essential instructions in the rule body. Preserve supporting documents or scripts at explicit destination paths, update references, and verify they can be read after installation. A file reference does not automatically inline it.
- Preserve licensing and attribution. Treat hooks and executable integrations separately: copying their prose does not install or activate them in Cursor.
- Inspect the rule in the installed Cursor client and exercise a representative request. Report any unsupported capability and whether client activation was actually checked.
Example rule:
---
description: Python conventions for this repository
globs: "**/*.py"
alwaysApply: false
---
Follow this repository's configured formatter and test conventions.
Current format reference: https://cursor.com/docs/rules (checked 2026-10-13). This skill is a conversion procedure; it does not bundle an automatic converter.