CtrlK
BlogDocsLog inGet started
Tessl Logo

omni-context-rtk

Configure RTK filters, context engineering rules, and context relay settings. Test compression with real prompt samples and manage context transformation pipelines.

51

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/omni-context-rtk/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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 body is well-structured and token-efficient, but its actionability is undercut by empty placeholder request bodies and it offers no workflow/validation guidance for the install and update operations. Filling in representative payloads and adding a validate-then-apply note would lift the weaker dimensions.

Suggestions

Replace the empty '{}' bodies on PUT /config, POST /import, and POST /test with representative JSON payloads showing the key fields, so the examples are copy-paste runnable.

Add a short workflow note for filter import (e.g. validate the TOML via POST /import before installing, check load diagnostics via GET /filters) to introduce validation checkpoints.

Drop or reword the duplicated Overview line so the body does not repeat the frontmatter description token-for-token.

DimensionReasoningScore

Conciseness

The body is lean with no concept over-explanation and concise per-endpoint curl blocks; the only padding is the Overview line duplicating the frontmatter description verbatim, a minor instance of over-explanation that could be trimmed.

4 / 5

Actionability

GET curl examples are executable, but the PUT/POST examples ship empty '{}' bodies with no real request fields, so the guidance is concrete yet incomplete and defers the actual payloads to the OpenAPI spec.

3 / 5

Workflow Clarity

The content is an endpoint catalog with no multi-step sequence, and potentially destructive operations like filter import/config update lack validation checkpoints or validate-then-apply feedback guidance.

3 / 5

Progressive Disclosure

Section headers (Overview, Authentication, Endpoints, Payloads) give good structure and the Payloads section signals a one-level reference to the OpenAPI spec, though the bulk of real detail is deferred rather than split into local bundle files.

4 / 5

Total

14

/

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 states concrete capabilities clearly but relies entirely on technical jargon and omits any 'when to use' trigger guidance, capping completeness. Adding natural trigger phrases and a Use-when clause would materially improve it.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when configuring RTK compression, tuning context-relay settings, or previewing prompt compression.'

Soften jargon by adding user-facing synonyms (e.g. 'prompt compression', 'context filters') alongside 'RTK' and 'context engineering rules' to improve trigger_term_quality.

Confirm the description is not duplicating the body Overview verbatim to keep the frontmatter as a distinct, scannable summary.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Configure RTK filters, context engineering rules, and context relay settings', 'Test compression with real prompt samples', 'manage context transformation pipelines'), though some objects like 'context engineering rules' are slightly abstract, leaving minor gaps versus a fully comprehensive list.

4 / 5

Completeness

It clearly answers 'what' the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the missing-trigger rule.

3 / 5

Trigger Term Quality

The description is dominated by technical jargon ('RTK filters', 'context engineering rules', 'context relay settings', 'context transformation pipelines') with no natural user-facing phrases or synonyms a non-specialist would say, missing the common trigger terms users actually voice.

2 / 5

Distinctiveness Conflict Risk

It carves a clear niche (omniroute RTK and context-relay configuration) with mostly distinct triggers, carrying only minor overlap risk with sibling context-management skills.

4 / 5

Total

13

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
diegosouzapw/OmniRoute
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.