suggesting-skills
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?
More from spencerpauly/awesome-cursor-skills
saving-workspace-context
Automatically persist useful context — research, decisions, learnings, templates — to workspace files so knowledge survives across conversations.
38database-design
Design database schemas — tables, relationships, indexes, constraints, and ORM setup. Covers relational design, normalization, and common patterns.
37reviewing-code
Perform a thorough code review focused on correctness, maintainability, performance, and best practices.
37suggesting-cursor-rules
When the user repeats the same correction or convention multiple times, suggest a Cursor rule to encode it permanently.
35systematic-debugging
Structured debugging methodology — reproduce, isolate, hypothesize, verify. Covers git bisect, binary search, logging, and minimal reproduction.
33auditing-security
Perform a systematic security audit of a codebase, checking for OWASP Top 10 vulnerabilities, secrets exposure, and insecure patterns.
33