cli-contexts

Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings and inspect active context pipelines.

Quality

47%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/cli-contexts/SKILL.md

Quality

Content

43%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 an auto-generated command catalog: executable in form but padded with redundant echo-only examples and duplicate sections, with no workflow sequencing or validation guidance for destructive operations and no progressive disclosure into reference files.

Suggestions

De-duplicate the repeated context-eng config/show/set/list sections and reconcile the conflicting flag lists for 'context-eng set'.

Replace bare echo examples with realistic invocations showing flags in use, and add a one-line description for every subcommand.

Split the bulky catalog into per-topic reference files (e.g., contexts.md, sessions.md, context-eng.md) and keep SKILL.md as a concise overview with clearly signaled links.

Dimension	Reasoning	Score
Conciseness	It avoids explaining concepts Claude already knows, but every 'Example:' block merely echoes the bare command header and several subcommands (context-eng config/show/set/list) are duplicated verbatim, leaving noticeable boilerplate that could be tightened.	3 / 5
Actionability	Commands are technically executable, yet most subcommands carry no description, examples never demonstrate flag usage with real values, and duplicate 'context-eng set' blocks list contradictory flags — concrete but with key details missing.	3 / 5
Workflow Clarity	The body is a flat command catalog with no sequencing, and destructive/batch operations (remove, expire-all, import) lack any validation or verification steps; the rough grouping under parent commands is the only structure present.	2 / 5
Progressive Disclosure	Section headers provide some navigability, but a ~386-line command catalog that clearly belongs in split reference files (contexts.md, sessions.md, context-eng.md) is fully inlined with no external references.	3 / 5
	Total	11 / 20 Passed

Description

51%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 communicates what the skill does through several concrete actions over a distinct niche, but it omits any explicit 'when to use' trigger guidance and leans on jargon instead of natural user-facing keywords.

Suggestions

Append an explicit 'Use when ...' clause naming natural triggers (e.g., 'Use when managing context-relay sessions or RTK filters from the CLI').

Soften jargon with a few natural synonyms a user might actually say ('context filters', 'session management') to improve trigger-term quality.

Add common variations or file/command extensions to broaden the natural keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions across named objects — 'Manage context engineering configurations, RTK filter sets, and conversation sessions', 'Apply context-relay settings', 'inspect active context pipelines' — with only minor coverage gaps, matching the anchor for several specific actions.	4 / 5
Completeness	There is a clear 'what' but no 'Use when...' clause or equivalent explicit trigger guidance for when to invoke the skill, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	The terms ('RTK filter sets', 'context-relay settings', 'context pipelines') are technical jargon rather than natural phrases a user would say, and no synonyms or common variations are offered; it sits between the all-jargon anchor and a 'some relevant keywords' anchor.	2 / 5
Distinctiveness Conflict Risk	The niche vocabulary ('RTK filter sets', 'context-relay settings', 'context pipelines') gives it a distinct identity with only minor overlap risk against closely related CLI skills.	4 / 5
	Total	13 / 20 Passed

Validation

100%

Warnings & errors only

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: diegosouzapw/OmniRoute
Path: skills/cli-contexts/SKILL.md
Commit: ea0cdc5

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.