CtrlK
BlogDocsLog inGet started
Tessl Logo

ctx-insight

Open the context-mode Insight analytics dashboard in the browser. Shows personal metrics: session activity, tool usage, error rate, parallel work patterns, project focus, and actionable insights. First run installs dependencies (~30s). Subsequent runs open instantly. Trigger: /context-mode:ctx-insight

64

Quality

76%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/ctx-insight/SKILL.md
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.

This is a well-structured, concise skill for a simple single-action task. It efficiently communicates what Claude needs to do (call an MCP tool and relay results) without over-explaining. The main weakness is that the optional parameter documentation is slightly confusing with the dual naming convention (sessionDir/insightSessionDir), and a concrete tool call example would improve actionability.

Suggestions

Add a concrete example of the MCP tool call with optional parameters, e.g., `ctx_insight({ port: 4747, sessionDir: '/path/to/sessions' })` to clarify the dual naming convention and make the skill more copy-paste ready.

DimensionReasoningScore

Conciseness

The content is lean and efficient. It doesn't explain what an analytics dashboard is or how MCP tools work. Every line provides actionable information Claude needs to execute the task.

3 / 3

Actionability

It provides concrete guidance on calling the MCP tool and what to tell the user, but the instructions are more descriptive than executable — there's no actual code example showing the tool call syntax, and the optional parameter documentation (sessionDir/insightSessionDir, contentDir/insightContentDir) is somewhat confusing without concrete examples.

2 / 3

Workflow Clarity

For this simple single-task skill, the workflow is clear and unambiguous: call the tool, relay output, inform the user. Steps are well-sequenced and the user communication checklist in step 4 is a nice touch. No destructive or batch operations require validation checkpoints.

3 / 3

Progressive Disclosure

For a simple, short skill under 50 lines with no need for external references, the content is well-organized with clear sections. The instructions are appropriately concise and don't need to be split across files.

3 / 3

Total

11

/

12

Passed

Description

67%

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 does a good job specifying concrete capabilities and metrics the dashboard provides, and it occupies a clear niche that won't conflict with other skills. However, it lacks an explicit 'Use when...' clause describing natural user scenarios, and the trigger is a slash command rather than natural language terms users would say, which limits discoverability in a multi-skill selection context.

Suggestions

Add an explicit 'Use when...' clause describing natural scenarios, e.g., 'Use when the user wants to review their session analytics, check tool usage stats, or view error rates and work patterns.'

Include natural language trigger terms users might say, such as 'show my stats', 'usage analytics', 'performance dashboard', or 'how am I using tools'.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions and metrics: 'session activity, tool usage, error rate, parallel work patterns, project focus, and actionable insights.' Also describes behavior differences between first run and subsequent runs.

3 / 3

Completeness

The 'what' is well-covered (opens analytics dashboard, shows personal metrics). However, the 'when' is only expressed as a slash command trigger rather than an explicit 'Use when...' clause describing scenarios or user intents that should activate this skill.

2 / 3

Trigger Term Quality

Includes some relevant terms like 'analytics dashboard', 'metrics', 'session activity', 'tool usage', 'error rate', but the primary trigger is a slash command '/context-mode:ctx-insight' which is not a natural user phrase. Missing natural terms a user might say like 'show my stats', 'performance overview', or 'usage analytics'.

2 / 3

Distinctiveness Conflict Risk

Very specific niche: a context-mode Insight analytics dashboard with a unique slash command trigger. Unlikely to conflict with other skills due to the specific tool name and distinct set of metrics described.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

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.