cursor-known-pitfalls

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-known-pitfalls

Manage avoid common Cursor IDE pitfalls and mistakes. Triggers on "cursor pitfalls", "cursor mistakes", "cursor gotchas", "cursor issues", "cursor problems". Use when working with cursor known pitfalls functionality. Trigger with phrases like "cursor known pitfalls", "cursor pitfalls", "cursor".

42%

Overall

Validation — 81%

Implementation — 22%

Activation — 40%

SKILL.md

Review

Evals

Activation

40%

This description suffers from vague capability statements and grammatical issues ('Manage avoid common'). While it includes trigger terms and a 'Use when' clause, the actual functionality remains unclear - users won't know what specific pitfalls are covered or what actions the skill performs. The overly broad 'cursor' trigger creates conflict risk with other Cursor-related skills.

Suggestions

Fix the grammatical error and specify concrete actions: 'Identifies and helps avoid common Cursor IDE pitfalls including [specific examples like tab completion conflicts, context window limitations, etc.]'

Narrow the trigger terms to avoid conflicts: Remove the generic 'cursor' trigger and keep only the specific pitfall-related phrases

Add specific use cases to the 'Use when' clause: 'Use when encountering unexpected Cursor behavior, debugging IDE issues, or setting up Cursor for the first time'

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'Manage avoid common Cursor IDE pitfalls and mistakes' without listing any concrete actions or specific pitfalls. It doesn't explain what the skill actually does beyond generic 'pitfalls' management.	1 / 3
Completeness	Has a weak 'what' (manage pitfalls) and includes a 'Use when' clause, but the 'what' is so vague that the completeness is undermined. The 'when' guidance is present but circular ('Use when working with cursor known pitfalls functionality').	2 / 3
Trigger Term Quality	Includes several relevant trigger terms ('cursor pitfalls', 'cursor mistakes', 'cursor gotchas', 'cursor issues', 'cursor problems'), but they are repetitive variations of the same concept. The generic 'cursor' trigger is too broad and could conflict with other cursor-related skills.	2 / 3
Distinctiveness Conflict Risk	The 'cursor' trigger alone is very generic and could conflict with any Cursor IDE-related skill. However, the specific 'pitfalls', 'mistakes', 'gotchas' terms provide some distinctiveness for this particular use case.	2 / 3
	Total	7 / 12 Passed

Implementation

22%

This skill is a structural skeleton without substantive content. It promises to cover 'AI feature pitfalls, configuration issues, security concerns' but provides none of them in the main file. The instructions are entirely abstract with no concrete pitfalls, specific settings, or executable guidance that would help Claude avoid actual Cursor issues.

Suggestions

Add 3-5 specific, concrete pitfalls directly in the main skill file with their solutions (e.g., 'Pitfall: .cursorrules not being read - Solution: ensure file is in project root, not subdirectory')

Replace abstract instructions with actionable commands or configuration snippets (e.g., specific .cursorrules settings, keyboard shortcuts to disable problematic features)

Include at least one concrete example of a common mistake and its fix inline, rather than deferring all examples to external files

Add validation steps to verify configuration changes took effect (e.g., 'Test by typing X and confirming Y behavior')

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes unnecessary filler like 'This skill helps you identify' and generic prerequisites that Claude would already understand. The actual pitfalls content is entirely absent from the main file.	2 / 3
Actionability	The instructions are vague and abstract ('Review the pitfalls list', 'Audit your current Cursor configuration') with no concrete examples, specific pitfalls, commands, or actionable guidance. It describes what to do conceptually without showing how.	1 / 3
Workflow Clarity	The 6-step workflow is generic and lacks any validation checkpoints or specific actions. Steps like 'Implement recommended settings' provide no actual settings to implement, and there's no feedback loop for verifying changes work.	1 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main skill file contains almost no substantive content - it's essentially an empty shell pointing elsewhere without providing any quick-start value.	2 / 3
	Total	6 / 12 Passed

Validation

81%

Warnings & errors only

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata' field is not a dictionary	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Reviewed

18 days ago

Table of Contents

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