CtrlK
BlogDocsLog inGet started
Tessl Logo

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

64

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

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 and well-organized body with concrete Cursor-specific examples, but it is somewhat verbose and does not exploit the available reference bundle, leaving progressive disclosure underused and workflows without explicit checkpoints.

Suggestions

Link the existing references/ files (e.g., advanced-techniques.md, best-practices.md, context-optimization-strategies.md) from the body and move the full .cursorignore template and .cursor/rules YAML example into references so the overview stays lean.

Tighten the intro and shrink the ASCII context-source boxes to the essentials to reduce token overhead.

Add a short ordered workflow with an explicit validation checkpoint (e.g., after applying context changes, verify the model still references earlier instructions) to lift workflow clarity.

DimensionReasoningScore

Conciseness

Mostly efficient and Cursor-specific, but the opening maxim ('managing it well is the single biggest lever for output quality') and large ASCII context-source boxes add explanatory padding that could be tightened.

2 / 3

Actionability

Provides copy-paste-ready @-mention prompts per task type, a full .cursorignore template, a .cursor/rules YAML example, and concrete tables of model limits and automatic-context behavior.

3 / 3

Workflow Clarity

Strategies are organized and numbered, but the body presents parallel strategies rather than a sequenced multi-step workflow with validation checkpoints; no explicit feedback loops are given.

2 / 3

Progressive Disclosure

The body is well-sectioned but monolithic: seven bundle files exist in references/ yet none are linked from the body, and content such as the full .cursorignore template and rule YAML that could live in references is 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 well-formed description with explicit trigger guidance and a clear Cursor-specific niche. The only weakness is that it frames the capability as one action ('Optimize') supported by mechanisms rather than listing multiple distinct actions.

DimensionReasoningScore

Specificity

States the domain and concrete mechanisms ('@-mentions, context pills, and conversation strategy') but the single verb 'Optimize' is the only action; it does not enumerate multiple distinct actions like the level-3 anchor.

2 / 3

Completeness

Answers 'what' ('Optimize context window usage in Cursor with...') and provides explicit trigger guidance via the 'Triggers on...' clause, satisfying both what and when.

3 / 3

Trigger Term Quality

An explicit 'Triggers on' list covers natural terms a user would say ('cursor context', 'context window', 'context limit', 'cursor memory', 'context management', '@-mentions', 'context pills').

3 / 3

Distinctiveness Conflict Risk

Scoped to Cursor context management with distinct Cursor-specific triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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