agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/karma-skill/.cursor/rules/find-karma.mdc

karma-skill / rules

Cursor rule1 starsChanged 45 days agoMITView on GitHub

Discover curated AI coding agent skills and plugins matching the active workspace

  • Where files are headingNew Cursor rule files have more rules about planning and tracking tasks, and fewer about code style.

    Of the Cursor rule files we read, the 4,144 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

The file

We split this find-karma.mdc into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When the user asks for:

    line 9
  2. Distinctive:

    Run the local KARMA discovery engine in read-only JSON mode:

    line 18
  3. Distinctive:

    Never automatically install third-party code.

    line 28

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule 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
find-karma.mdc
---
description: Discover curated AI coding agent skills and plugins matching the active workspace
globs: *
alwaysApply: false
---

# FIND KARMA ☯ | Cursor Agent Adapter

When the user asks for:
- `FIND KARMA` or `FIND KARMA ☯`
- "find karma"
- "what skills should I use for this project?"
- "recommend agent skills"
- "find plugins for this repo"

## Instructions

1. Run the local KARMA discovery engine in read-only JSON mode:
   ```bash
   ./bin/karma find --project . --goal "<USER_GOAL>" --agent cursor --json
   ```
   Or using Bun/Node:
   ```bash
   bun run karma find --project . --goal "<USER_GOAL>" --agent cursor --json
   ```

2. Present only the 2-5 highest-scoring recommendations with clear "why now" reasoning and source links.
3. Never automatically install third-party code. Always display the preview and request explicit user confirmation before running any installation commands.

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