suggesting-skills
Skill2 starsChanged 7 months agoMITView on GitHub
When the user struggles with a task that a known skill could handle, suggest installing it. Use when the user says "/suggesting-skills", "suggesting skills", or asks about suggesting skills.
3 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- ZeroTokenClaw/agents-skillsedited, first seen Sep 21, 2026
- matarpeles/skills-registry-demoedited, first seen May 5, 2026
- spencerpauly/skills-repotheir own version, first seen May 2, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- ZeroTokenClaw/agents-skills★ 199% same
- matarpeles/skills-registry-demo★ 099% same
Wrote their own version · 1
- spencerpauly/skills-repo★ 25same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository85 other files it gives its agents.
- accessibility-auditingSkill
- adding-analyticsSkill
- adding-api-docsSkill
- adding-authSkill
- adding-dockerSkill
- adding-e2e-testsSkill
- adding-error-trackingSkill
- adding-feature-flagsSkill
- adding-stripeSkill
- api-smoke-testingSkill
- architecture-decision-recordsSkill
- auditing-performanceSkill
- auditing-securitySkill
- auto-type-checkingSkill
- babysitting-prSkill
- best-of-n-solvingSkill
- building-skills-from-patternsSkill
- cavemanSkill
- codebase-onboardingSkill
- comparing-branches-visuallySkill
- converting-css-modules-to-tailwindSkill
- converting-css-to-tailwindSkill
- creating-prSkill
- dark-mode-testingSkill
- database-designSkill
- design-an-interfaceSkill
- detecting-port-conflictsSkill
- domain-modelSkill
- edit-articleSkill
- exporting-to-pngSkill
- finding-dev-server-urlSkill
- fixing-broken-linksSkill
- form-testingSkill
- generating-imagesSkill
- git-guardrails-claude-codeSkill
- github-triageSkill
- grill-meSkill
- grinding-until-passSkill
- improve-codebase-architectureSkill
- incident-responseSkill
- kubernetes-deployingSkill
- migrate-to-shoehornSkill
- monitoring-terminal-errorsSkill
- network-request-auditingSkill
- obsidian-vaultSkill
- parallel-ci-triageSkill
- parallel-code-reviewSkill
- parallel-exploringSkill
- parallel-test-fixingSkill
- profiling-performanceSkill
- prompt-engineeringSkill
- python-tdd-with-uvSkill
- qaSkill
- react-native-patternsSkill
- recording-browser-flow-as-testSkill
- request-refactor-planSkill
- responsive-testingSkill
- reviewing-codeSkill
- saving-workspace-contextSkill
- scaffold-exercisesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. 4 are common, 0 are distinctive, and 0 are very specific to this project.
4
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
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
- Common: line 21
Keep it brief and contextual:
- Common: line 56
Don't spam skill suggestions — one per conversation unless asked
- Common: line 57
Only suggest when the timing is natural (user is about to do the thing, not mid-task)
- Common: line 58
If the user declines, don't suggest the same skill again
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Suggesting Skills
Watch for moments where the user is working on something that an existing skill would make easier. Suggest it when the timing is natural.
Triggers
Suggest a skill when:
- The user asks how to do something a skill covers (e.g. "how do I add Sentry?" →
adding-error-tracking) - The user is struggling with a task and a skill has a proven workflow for it
- You notice the project is missing something a skill could set up (e.g. no tests, no CI)
- The user is manually doing something a Cursor-native skill automates
How to Suggest
Keep it brief and contextual:
There's a skill for that — `adding-error-tracking` handles Sentry
setup with source maps and performance monitoring. Want me to use it?Or when you notice a gap:
This project doesn't have CI set up. The `setting-up-ci` skill can
scaffold a GitHub Actions pipeline with lint, test, and build steps.
Want me to set that up?Skill Reference
| User is doing... | Suggest... |
| Adding analytics | adding-analytics |
| Setting up auth | adding-auth |
| Adding payments | adding-stripe |
| Writing tests from scratch | writing-tests, adding-e2e-tests |
| Debugging a hard bug | systematic-debugging |
| Creating a PR | creating-pr |
| Dockerizing | adding-docker |
| Setting up CI | setting-up-ci |
| Reviewing code quality | reviewing-code |
| Checking security | auditing-security |
| Building a mobile app | react-native-patterns |
| Working with LLM prompts | prompt-engineering |
| Designing a database | database-design |
Rules
- Don't spam skill suggestions — one per conversation unless asked
- Only suggest when the timing is natural (user is about to do the thing, not mid-task)
- If the user declines, don't suggest the same skill again
- Mention how to install: copy the
SKILL.mdto.cursor/skills/<name>/SKILL.md
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
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.

