cursor-known-pitfalls
Avoid common Cursor IDE pitfalls: AI feature mistakes, security gotchas, configuration errors, and team workflow issues. Triggers on "cursor pitfalls", "cursor mistakes", "cursor gotchas", "cursor issues", "cursor problems", "cursor tips".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-known-pitfalls/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is well-structured with explicit trigger terms and a clear niche around Cursor IDE pitfalls. Its main weakness is that the 'what' portion is somewhat categorical rather than listing specific concrete actions (e.g., 'detect insecure .cursorrules configurations' or 'flag accidental AI-generated code leaks'). Overall it's a solid description that would perform well in skill selection.
Suggestions
Add more specific concrete actions beyond categories, e.g., 'Identifies insecure .cursorrules configurations, flags AI-generated code quality issues, prevents accidental secret exposure in AI context.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor IDE) and lists categories of issues (AI feature mistakes, security gotchas, configuration errors, team workflow issues), but doesn't describe concrete actions like 'diagnose', 'fix', or 'prevent' specific problems. | 2 / 3 |
Completeness | Clearly answers both 'what' (avoid common Cursor IDE pitfalls across AI features, security, configuration, and team workflows) and 'when' (explicit trigger phrases listed with 'Triggers on' clause). | 3 / 3 |
Trigger Term Quality | Explicitly lists natural trigger terms users would say: 'cursor pitfalls', 'cursor mistakes', 'cursor gotchas', 'cursor issues', 'cursor problems', 'cursor tips'. These are natural phrases a user would use when seeking this kind of help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — specifically targets Cursor IDE pitfalls and common mistakes, which is a clear niche. The trigger terms are all Cursor-specific and unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured reference skill with strong actionability—concrete solutions, specific commands, and real configuration examples make it immediately useful. Its main weaknesses are moderate verbosity (problem descriptions explain things Claude already understands) and the monolithic structure that could benefit from splitting into category-specific files. The enterprise section at the end is notably less actionable than the rest of the content.
Suggestions
Trim problem descriptions to one-line summaries—Claude doesn't need explanations of what context overflow or timing attacks are; focus tokens on the solutions.
Split into category files (security-pitfalls.md, config-pitfalls.md, etc.) with SKILL.md as a concise index, improving progressive disclosure.
Make the Enterprise Considerations section actionable with concrete steps or remove it—currently it's vague advice ('have a plan', 'review annually') that doesn't match the quality of the rest.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary framing and explanations that Claude would already know (e.g., explaining what context window overflow causes, explaining what timing attacks are). Some pitfalls could be more terse, but overall it's not excessively verbose. | 2 / 3 |
Actionability | Nearly every pitfall includes concrete, actionable solutions: specific commands (Cmd+N, Cmd+K Cmd+S), exact file contents (.cursorignore, settings.json, .mdc rules), specific steps to follow, and named tools (Semgrep, Snyk). The guidance is copy-paste ready and specific. | 3 / 3 |
Workflow Clarity | Individual pitfalls have clear problem/solution structure, and Pitfall 1 includes a sequential workflow with validation steps. However, most solutions are standalone tips rather than sequenced workflows, and there's no overarching workflow for how to audit/address these pitfalls systematically. The Enterprise section lacks actionable steps. | 2 / 3 |
Progressive Disclosure | The content is well-organized by category with clear headers, making navigation easy. However, at ~200 lines it's a long monolithic file that could benefit from splitting detailed sections (security, configuration) into separate referenced files. No bundle files exist to offload detail into. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.