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".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable content packed with concrete code, commands, and config, organized into clear categories. Its main weakness is structure: all 18 pitfalls live inline in a 261-line wall of text despite matching reference files existing unused, and solutions lack explicit validation feedback loops.

Suggestions

Replace the inline per-category pitfall lists with concise summaries in SKILL.md and link to the corresponding references/ files (e.g. 'See [security-pitfalls.md](references/security-pitfalls.md)'), which already align with your categories — this turns the monolithic body into a one-level-deep overview.

For solutions involving destructive or batch operations (git rollback, AI-generated auth code, monorepo reindexing), add explicit validate→fix→retry checkpoints so workflow clarity can reach the top anchor.

Trim background restatement in 'Problem' fields and the 'Enterprise Considerations' bullet list to assume Claude's competence and reduce token cost.

Dimension	Reasoning	Score
Conciseness	The 261-line body is mostly lean Problem/Solution pairs, but all 18 pitfalls are dumped inline and some 'Problem' statements and the 'Enterprise Considerations' section restate background Claude already knows, so it could be tightened.	2 / 3
Actionability	Solutions give fully executable guidance: concrete commands ('npm run build', 'npm test', 'git checkout .'), copy-paste config blocks (.cursorignore, settings.json watcherExclude, .cursor/rules YAML), and specific keyboard shortcuts.	3 / 3
Workflow Clarity	Individual solutions are numbered and sequenced, and a few include implicit verification ('Run build', 'Run tests'), but as a catalog there is no overarching workflow with explicit validation checkpoints or feedback loops for the riskier operations (git rollback, security review).	2 / 3
Progressive Disclosure	Bundle files exist in references/ that map directly to the body's categories (ai-feature-pitfalls.md, security-pitfalls.md, configuration-pitfalls.md, performance-pitfalls.md, team-pitfalls.md), but the body never references or signals them — content that should be split across those files is monolithically inline.	2 / 3
	Total	9 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with explicit trigger guidance, third-person voice, and a clear, distinct Cursor-specific niche. The only weakness is that the capability is summarized by the single verb 'Avoid' plus category names rather than enumerating concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('common Cursor IDE pitfalls') and lists concrete categories ('AI feature mistakes, security gotchas, configuration errors, and team workflow issues'), but the only action verb is the vague 'Avoid' rather than multiple specific actions the skill performs.	2 / 3
Completeness	It states what the skill does ('Avoid common Cursor IDE pitfalls...') and provides explicit trigger guidance via 'Triggers on...', answering both 'what' and 'when'.	3 / 3
Trigger Term Quality	The 'Triggers on "cursor pitfalls", "cursor mistakes", "cursor gotchas", "cursor issues", "cursor problems", "cursor tips"' clause gives broad coverage of natural terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The Cursor-specific niche and dedicated 'cursor ...' trigger terms make it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.