cursor-context-management
Optimize context window usage in Cursor with @-mentions, context pills, and conversation strategy. Triggers on "cursor context", "context window", "context limit", "cursor memory", "context management", "@-mentions", "context pills".
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-context-management/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 strong trigger term coverage and clear distinctiveness for Cursor context management. The main weakness is that the 'what' portion could be more specific about the concrete actions or outputs the skill provides beyond the general verb 'optimize'. The explicit trigger terms compensate well for completeness.
Suggestions
Replace the vague 'Optimize context window usage' with more specific actions, e.g., 'Recommends strategies for reducing token usage, structuring @-mentions, managing context pills, and splitting conversations in Cursor IDE.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Cursor context window usage) and some actions/concepts (@-mentions, context pills, conversation strategy), but doesn't list multiple concrete actions like 'reduce token usage', 'structure prompts', or 'manage file references'. 'Optimize' is somewhat vague as a primary verb. | 2 / 3 |
Completeness | Clearly answers both 'what' (optimize context window usage in Cursor with @-mentions, context pills, and conversation strategy) and 'when' (explicit trigger terms listed with 'Triggers on' clause, which serves as an equivalent to 'Use when'). | 3 / 3 |
Trigger Term Quality | Includes a good range of natural keywords users would actually say: 'cursor context', 'context window', 'context limit', 'cursor memory', 'context management', '@-mentions', 'context pills'. These cover common variations of how users would phrase their needs. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Cursor IDE's context management features. The combination of 'Cursor' + 'context window' + '@-mentions' + 'context pills' creates a clear niche that is 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 solid, actionable reference for Cursor context management with excellent concrete examples for each @-mention type and good .cursorignore/.mdc configurations. Its main weaknesses are moderate verbosity (some sections explain things Claude already knows or include potentially outdated specifics like model token limits) and a lack of explicit workflow sequencing with validation checkpoints for context management decisions. The content would benefit from splitting supplementary material into bundle files.
Suggestions
Remove or significantly trim the model context window table (token counts are time-sensitive and Claude knows these models) and the explanation of what context is in the opening paragraph.
Add a decision-tree or flowchart workflow: detect context overflow signs → specific remediation step → verify improvement, rather than just listing signs and mitigations separately.
Split the .cursorignore examples, enterprise considerations, and model reference table into separate bundle files to keep the main SKILL.md focused on the core @-mention strategy and context pill management.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally well-organized but includes some unnecessary content Claude already knows (e.g., explaining what context is, the enterprise considerations section, and the model context window table with specific token counts that may become outdated). The ASCII box diagrams are visually helpful but consume significant tokens for information that could be presented more compactly. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready examples for every @-mention strategy, real .cursorignore configurations, and specific .mdc rule examples with proper YAML frontmatter. Each section gives exact commands and patterns rather than abstract descriptions. | 3 / 3 |
Workflow Clarity | The mitigation strategies are listed clearly and the task-based @-mention examples provide good guidance, but there's no explicit workflow sequence for managing context over the lifecycle of a task. The 'Signs of Context Overflow' section identifies problems but the recovery steps are just a flat list without a clear decision tree or feedback loop (e.g., detect overflow → take specific action → verify improvement). | 2 / 3 |
Progressive Disclosure | The content is well-sectioned with clear headers and progresses from basics to advanced topics, and external resource links are provided at the end. However, with no bundle files, all content is inline in a single long document (~150 lines). The .cursorignore examples, model context tables, and enterprise considerations could be split into referenced files to keep the main skill leaner. | 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.