agentleFS
Sign inStart free
scoobydont-666scoobydont-666/shared-claude-skills/skills/claude-to-cursor/SKILL.md

claude-to-cursor

Skill1 starsChanged 32 days agoMITView on GitHub

Convert selected Claude Code skills into scoped Cursor project rules, preserving bundled references and verifying target-client behavior.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the requested output repository or directory.

    line 8
  2. Very specific:

    Write focused .mdc project rules in .cursor/rules/.

    line 18
  3. Distinctive:

    Keep essential instructions in the rule body.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Claude 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

  1. 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.
  2. Write focused .mdc project rules in .cursor/rules/. Use a description for agent-selected relevance, globs for file-specific rules, or alwaysApply: true only when the user intends the rule to apply to every conversation.
  3. 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.
  4. Preserve licensing and attribution. Treat hooks and executable integrations separately: copying their prose does not install or activate them in Cursor.
  5. 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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free