CtrlK
BlogDocsLog inGet started
Tessl Logo

ctx-insight

Open the context-mode Insight dashboard in your default browser. Insight is the hosted analytics layer for AI-assisted engineering teams — per-engineer productive rate, retry waste, blocker detection, role-narrowed views. Trigger: /context-mode:ctx-insight

61

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The content is a tight, fully actionable single-task skill with a clear sequenced workflow and clean organization. Its only real weakness is minor redundancy — the URL and dashboard-opening intent are restated — which slightly undercuts token efficiency.

Suggestions

State the URL once (in step 1) and reference it in step 3 rather than repeating the full https://context-mode.com/insight string three times.

Drop or trim the 'single source of truth for sign-in and pricing details' line unless it is needed to prevent Claude from inventing pricing info.

Merge the intro sentence with step 1 to avoid restating 'Open the Insight dashboard in the default browser' twice.

DimensionReasoningScore

Conciseness

The body is short and largely efficient, but it repeats the dashboard-opening intent across the intro and step 1, restates the URL three times (step 1, step 3 bullet 1, and the manual-open bullet), and includes a mildly padded line about 'single source of truth for sign-in and pricing details' that could be tightened.

2 / 3

Actionability

It gives fully executable guidance — 'Call the `ctx_insight` MCP tool (no parameters)' — plus the exact URL and a concrete scripted message to show the user, leaving no ambiguity about what to do.

3 / 3

Workflow Clarity

This is a simple single-action skill with a clear 1-2-3 sequence and an unambiguous primary action; per the simple-skills note, workflow clarity can score 3 when the single action is unambiguous, and no destructive or batch operation requires a validation checkpoint.

3 / 3

Progressive Disclosure

At well under 50 lines with no need for external references and no bundle files present, the well-organized '# Context Mode Insight' / '## Instructions' structure satisfies the simple-skills bar for a top progressive-disclosure score.

3 / 3

Total

11

/

12

Passed

Description

57%

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 is concrete and distinctive, naming a specific product and its analytics features with an explicit trigger. Its main weakness is the absence of a natural-language 'Use when...' scenario and trigger-term breadth, leaving the 'when' guidance as a slash command only.

Suggestions

Add a 'Use when...' clause naming natural scenarios, e.g. 'Use when the user wants to view engineering analytics, productive rates, or blocker insights.'

Broaden trigger terms beyond the slash command to include phrases users would naturally say, such as 'analytics', 'engineering metrics', or 'productivity dashboard'.

Frame the listed metrics as actions the skill enables rather than only product features, to better match the 'multiple specific concrete actions' top anchor.

DimensionReasoningScore

Specificity

The description names the domain ('hosted analytics layer for AI-assisted engineering teams') and concrete features ('per-engineer productive rate, retry waste, blocker detection, role-narrowed views'), but the skill's only actual action is 'Open the context-mode Insight dashboard in your default browser' — a single action rather than the multiple concrete actions the top anchor expects.

2 / 3

Completeness

It clearly answers 'what' (open the Insight dashboard), and provides an explicit trigger line ('Trigger: /context-mode:ctx-insight'), but it lacks a 'Use when...' scenario clause describing when Claude should invoke it, which the guidelines say caps completeness at 2.

2 / 3

Trigger Term Quality

It surfaces some relevant keywords ('Insight dashboard', 'context-mode', '/context-mode:ctx-insight'), but the trigger is a slash command rather than natural phrases a user would say, and it omits common variations like 'analytics', 'productive rate', or 'engineering metrics'.

2 / 3

Distinctiveness Conflict Risk

The named product ('context-mode Insight'), unique slash command, and specific analytics niche make it clearly distinguishable and unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

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
mksglu/context-mode
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.