cursor-codebase-indexing
Set up and optimize Cursor codebase indexing for semantic code search and @Codebase queries. Triggers on "cursor index", "codebase indexing", "index codebase", "cursor semantic search", "@codebase", "cursor embeddings".
80
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/cursor-pack/skills/cursor-codebase-indexing/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.
This is a solid skill description with excellent trigger term coverage and clear distinctiveness. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., configuring .cursorignore, managing embedding settings, optimizing index performance). Overall it effectively communicates when and why to select this skill.
Suggestions
Expand the capability description with more specific concrete actions, e.g., 'Configure .cursorignore files, manage embedding settings, troubleshoot indexing failures, and optimize index performance for Cursor codebase indexing.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor codebase indexing) and some actions ('set up and optimize'), but doesn't list multiple specific concrete actions like configuring .cursorignore files, managing embedding settings, or troubleshooting indexing issues. | 2 / 3 |
Completeness | Clearly answers both 'what' (set up and optimize Cursor codebase indexing for semantic code search and @Codebase queries) and 'when' (explicit trigger terms listed with 'Triggers on' clause serving as the 'Use when' equivalent). | 3 / 3 |
Trigger Term Quality | Includes a strong set of natural trigger terms that users would actually say: 'cursor index', 'codebase indexing', 'index codebase', 'cursor semantic search', '@codebase', 'cursor embeddings'. These cover common variations well. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Cursor IDE's indexing and semantic search features. The trigger terms are highly distinctive and unlikely to conflict with general coding, search, or other IDE 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 solid, actionable skill with excellent concrete examples (ignore files, CLI commands, query examples) and good troubleshooting coverage. Its main weaknesses are moderate verbosity — particularly the architecture explanation section and some explanatory text that Claude doesn't need — and the monolithic structure that could benefit from splitting into overview + reference files. The workflow could be strengthened with explicit verification steps after configuration changes.
Suggestions
Remove or significantly condense the 'How Indexing Works' ASCII diagram and 'Key Architecture Details' section — Claude doesn't need to understand the embedding pipeline to help users configure indexing.
Add a verification step after .cursorignore configuration, e.g., 'Verify exclusions: Cursor Settings > Features > Codebase Indexing > View included files — confirm excluded files are not listed.'
Consider splitting the enterprise considerations, detailed configuration examples, and troubleshooting into separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary explanations (e.g., the ASCII art architecture diagram explaining how embeddings work, the 'How Indexing Works' section with key architecture details that Claude doesn't need to internalize). The configuration examples and troubleshooting table are useful, but the overall content could be tightened by ~30%. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready configuration files (.cursorignore, .cursorindexingignore), specific CLI commands for re-indexing and fixing Linux file watcher limits, exact paths for cache deletion across all OSes, and clear example @Codebase queries. Highly executable guidance throughout. | 3 / 3 |
Workflow Clarity | The initial setup steps are clearly sequenced with verification (check status bar), and the re-indexing troubleshooting has a clear escalation path. However, there are no explicit validation checkpoints or feedback loops — for example, after configuring .cursorignore, there's no step to verify files were actually excluded. The troubleshooting table helps but is reactive rather than proactive. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and logical sections, and external resource links are provided at the end. However, the skill is quite long (~180 lines of content) and could benefit from splitting detailed configuration examples, enterprise considerations, and troubleshooting into separate referenced files rather than inlining everything. | 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
70e9fa4
- 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.