CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

context-mode

MANDATORY routing rules for context-mode. Invoke whenever you analyze, count, filter, compare, search, parse, or transform data; fetch a URL; or run a data-heavy command — so raw bytes stay out of the context window.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./configs/copilot-cli/skills/context-mode/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is exceptionally concise and provides concrete tool-call routing with clear sections, fitting a simple single-purpose skill well. Its main weakness is workflow clarity: the batch/data-heavy operations have no explicit validation or verification steps, which the rubric caps at 3.

Suggestions

Add an explicit verification checkpoint after batch_execute/fetch_and_index (e.g., confirm ctx_search returned results before proceeding) to lift workflow_clarity above 3.

Specify exact argument shapes for ctx_search (query list format) so the executable guidance is fully complete.

Clarify what to do when a routed ctx_execute fails or returns empty, adding a brief retry/fallback feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and efficient with no padding or explanation of concepts Claude already knows; every line gives routing rules or tool selections, and all tokens earn their place.

5 / 5

Actionability

It gives concrete, copy-paste-ready tool calls with arguments (e.g., 'ctx_batch_execute(commands, queries)', 'ctx_fetch_and_index(url, source)') and specific blocked-alternative mappings, though exact argument shapes for ctx_search queries are only partially spelled out.

4 / 5

Workflow Clarity

The Tool selection list provides a rough GATHER/PROCESS/WEB/SEARCH sequence, but there are no validation checkpoints or feedback loops for batch operations, which the rubric caps at 3 for batch/data-heavy skills.

3 / 5

Progressive Disclosure

This is a short, single-purpose skill under 50 lines with no bundle files needed; it is organized into well-labeled sections (Think in Code, BLOCKED, Tool selection) that make navigation trivial, satisfying the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

68%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly answers 'what' and 'when' with concrete action verbs and a use-when clause, but the routing verbs are broad enough to risk overlapping with many data/coding skills, and it describes triggers more than the skill's own capabilities. It is strong but not maximally distinctive or comprehensive.

Suggestions

Narrow the trigger list or tie it explicitly to the context-window-preservation goal so it does not fire on routine data analysis handled by general coding.

State the skill's own capability concretely (e.g., 'Routes data-heavy operations through context-managed MCP tools') rather than only listing user actions.

Add a few natural synonyms or file/format cues users would say to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Lists several concrete routing actions ('analyze, count, filter, compare, search, parse, or transform data', 'fetch a URL', 'run a data-heavy command') with minor coverage gaps; it describes triggers rather than the skill's own capabilities, which slightly limits specificity.

4 / 5

Completeness

Both 'what' (routing rules that keep raw bytes out of context) and 'when' ('Invoke whenever you analyze...') are present, but the 'what' leans on routing intent rather than stating the skill's concrete function, so it is not maximally explicit.

4 / 5

Trigger Term Quality

Natural user-action verbs are well covered ('analyze, count, filter, compare, search, parse, transform', 'fetch a URL'), but it lacks common synonyms/variations and shorthand phrases users might actually say.

4 / 5

Distinctiveness Conflict Risk

The trigger verbs are extremely broad data-analysis actions that overlap heavily with general-purpose coding/data skills; the MCP-tool niche is the only differentiator, leaving moderate conflict risk.

3 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mksglu/context-mode

Path

configs/copilot-cli/skills/context-mode/SKILL.md

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.