CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

Quality

73%

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/ctx-insight/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 a model of a minimal single-purpose skill: exact tool invocation, expected behavior, the precise user-facing message, and a fallback path, all in ~20 lines with no padding. Its only blemish is one promotional line about sign-in and pricing that could be cut.

DimensionReasoningScore

Conciseness

The body is lean and imperative ("Call the `ctx_insight` MCP tool (no parameters)", "Display the tool's output"), assuming Claude's competence with no concept explanations. It falls short of 5 because "The landing page at context-mode.com/insight is the single source of truth for sign-in and pricing details" is marketing filler that does not earn its tokens.

4 / 5

Actionability

Fully executable guidance: exact tool name (`ctx_insight`), explicit "no parameters", the URL it opens, the expected return ("a confirmation line"), the exact message to relay, and a fallback branch if the browser fails. Nothing is left to inference.

5 / 5

Workflow Clarity

This is a simple single-task skill with an unambiguous three-step sequence (call tool → display output → tell the user X), which qualifies for the simple-skill exception to score 5. It even includes an error-recovery branch ("If the browser did not open automatically, share the URL"), and no destructive or batch operations require validation.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent and nothing in the body cites them), so per the rubric's simple-skill note a well-organized single-file layout earns 5. The title, one-line summary, and Instructions section are cleanly organized with no content that belongs in a separate file.

5 / 5

Total

19

/

20

Passed

Description

41%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 states a single concrete action and identifies a distinct product niche, but its trigger guidance is limited to the literal slash command with no natural-language "use when" phrasing, and it uses second-person voice. The feature-list line pads the description without adding actionable capability statements.

Suggestions

Add a natural-language trigger clause, e.g. "Use when the user wants to open or view the Insight dashboard, check engineering analytics, or asks about per-engineer productivity or blockers".

Rewrite in third person and lead with capability verbs: "Opens the context-mode Insight dashboard in the user's default browser and reports the URL".

Trim the product marketing list ("per-engineer productive rate, retry waste, blocker detection, role-narrowed views") or reframe it as trigger keywords, since it describes the product rather than what this skill does.

DimensionReasoningScore

Specificity

The only concrete action is "Open the context-mode Insight dashboard in your default browser"; the rest ("per-engineer productive rate, retry waste, blocker detection, role-narrowed views") describes product features rather than skill actions. It reads as one concrete action (an anchor-3 fit), but the second-person phrasing "in your default browser" triggers the rubric's −1 voice penalty, landing at 2.

2 / 5

Completeness

The "what" is clear (open the hosted Insight dashboard in the browser), but the "when" is limited to the exact slash command with no "Use when..." clause or natural-language situations, which caps completeness at 3. It is above 2 because the what is concrete and a trigger line is present, but below 4 because the when-clause is narrow and implicit for natural invocation.

3 / 5

Trigger Term Quality

The sole explicit trigger is the literal slash command "Trigger: /context-mode:ctx-insight", with no natural phrases a user would say (e.g. "open the insight dashboard", "show engineering analytics"). This matches "one or two generic keywords; missing the natural phrases users say"; it does not reach 3 because there is no coverage of common variations or synonyms.

2 / 5

Distinctiveness Conflict Risk

The unique product name ("context-mode Insight dashboard") and distinct slash-command trigger give it a clear niche with minimal conflict risk, matching "mostly distinct; minor overlap risk". It falls short of 5 because generic terms like "dashboard" and "analytics" could still overlap with other dashboard/analytics skills when invoked in natural language.

4 / 5

Total

11

/

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

skills/ctx-insight/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.