cursor-indexing-issues

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill cursor-indexing-issues

Manage troubleshoot Cursor codebase indexing problems. Triggers on "cursor indexing", "cursor index", "cursor codebase", "@codebase not working", "cursor search broken". Use when working with cursor indexing issues functionality. Trigger with phrases like "cursor indexing issues", "cursor issues", "cursor".

51%

Overall

Validation — 81%

Implementation — 35%

Activation — 50%

SKILL.md

Review

Evals

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

Implementation

35%

This skill provides a high-level outline for troubleshooting Cursor indexing but lacks the concrete, executable guidance needed to be useful. The instructions are abstract descriptions rather than specific commands or steps, and critical details are either missing or deferred to external files without providing sufficient standalone value.

Suggestions

Add specific commands for clearing the index cache (e.g., exact file paths to delete or terminal commands)

Include the actual Command Palette command for manual refresh (e.g., 'Cursor: Rebuild Index')

Provide a concrete .cursorignore example with common patterns to exclude

Add specific indicators for diagnosing each issue type (what does 'stuck' look like vs 'empty results')

Dimension	Reasoning	Score
Conciseness	The content is relatively brief but includes some unnecessary sections like 'Prerequisites' that explain things Claude would know (e.g., 'Understanding of project file structure'). The Overview section restates the purpose redundantly.	2 / 3
Actionability	Instructions are vague and abstract with no concrete commands, code, or specific steps. 'Check indexing status in status bar' and 'Clear index cache if issues persist' lack executable details - no actual paths, commands, or specific UI navigation.	1 / 3
Workflow Clarity	Steps are listed in sequence but lack validation checkpoints and specific details. There's no feedback loop for verifying fixes worked, and critical details like how to actually clear the cache or what the Command Palette command is are missing.	2 / 3
Progressive Disclosure	References to external files (errors.md, examples.md) are present and one-level deep, but the main content is too thin - it defers too much to external files without providing enough actionable content in the skill itself.	2 / 3
	Total	7 / 12 Passed

Activation

50%

The description identifies a clear niche (Cursor indexing problems) and includes some useful trigger phrases, but suffers from vague action descriptions and overly broad catch-all triggers. The 'Use when' clause is circular and doesn't provide meaningful guidance, and the specific troubleshooting capabilities are not enumerated.

Suggestions

Replace vague 'manage troubleshoot' with specific actions like 'diagnose indexing failures, rebuild codebase index, clear index cache, fix @codebase search issues'

Remove overly broad triggers ('cursor', 'cursor issues') that would conflict with other Cursor-related skills, keeping only indexing-specific terms

Rewrite the 'Use when' clause to be non-circular, e.g., 'Use when @codebase returns no results, indexing seems stuck, or search doesn't find known files'

Dimension	Reasoning	Score
Specificity	Names the domain (Cursor codebase indexing) and mentions 'manage troubleshoot' as actions, but lacks specific concrete actions like 'rebuild index', 'clear cache', or 'diagnose indexing errors'.	2 / 3
Completeness	Has a 'Use when' clause but it's circular and vague ('Use when working with cursor indexing issues functionality'). The 'what' is weak (just 'manage troubleshoot') and the 'when' doesn't add meaningful guidance beyond the title.	2 / 3
Trigger Term Quality	Includes some relevant keywords like 'cursor indexing', '@codebase not working', 'cursor search broken', but the final triggers are too broad ('cursor issues', 'cursor') which would match non-indexing Cursor problems.	2 / 3
Distinctiveness Conflict Risk	The specific triggers like '@codebase not working' and 'cursor search broken' help distinguish it, but overly broad triggers like 'cursor' and 'cursor issues' would cause conflicts with any other Cursor-related skills.	2 / 3
	Total	8 / 12 Passed

Reviewed

17 days ago

Table of Contents

Validation Implementation Activation

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.