CtrlK
BlogDocsLog inGet started
Tessl Logo

sessions

Core principles and workflow router for changes to the Agents Window under src/vs/sessions.

61

Quality

71%

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 ./.github/skills/sessions/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 skill body is a well-structured, lean workflow router with explicit sequencing, proportional validation checkpoints, and clean one-level-deep routing to focused specifications. The only minor gap is that actionable detail lives in referenced specs rather than inline, which is appropriate for a router skill.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it routes to specifications and lists principles as terse bullets with no padding, no concept explanations, and every line earning its place.

5 / 5

Actionability

It gives concrete, executable pointers ('Register Sessions menu IDs in browser/menus.ts', 'npm run valid-layers-check', named services and entry points), but the bulk is routing/principle guidance rather than copy-paste code, leaving minor gaps.

4 / 5

Workflow Clarity

The seven numbered sections form an explicit sequence (principles → identify area → inspect → implement → validate → record feedback → maintain), and §5 provides proportional validation checkpoints including a 'documentation-only changes' exception; §4 also routes updates back to the owning spec.

5 / 5

Progressive Disclosure

It is a clean overview that routes to a README and a one-level-deep table of focused specifications (LAYERS.md, SESSIONS.md, etc.), explicitly instructing reading only relevant specs and searching the learning inbox by heading — well-signaled, single-depth navigation with no bundle files present.

5 / 5

Total

19

/

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 is domain-specific and reasonably clear about scope, but it omits an explicit 'Use when...' trigger and lists only minimal concrete actions. Adding a trigger clause and one or two concrete verbs would lift completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when implementing, reviewing, or designing changes to the Agents Window under src/vs/sessions'.

Name a couple of concrete actions (e.g. 'routes work to the owning specification, enforces layering, and picks validation checks') to raise specificity.

Include a natural user-spoken synonym such as 'Agents Window feature work' to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('changes to the Agents Window under src/vs/sessions') and one concrete action ('workflow router') plus 'core principles', but it is not a comprehensive list of concrete actions; it stops just below the 'several specific actions' bar.

3 / 5

Completeness

It gives a clear 'what' (core principles and workflow router for Agents Window changes) but no explicit 'Use when...' trigger clause, so the 'when' is only weakly implied by 'for changes to'.

3 / 5

Trigger Term Quality

It names the natural target ('Agents Window', 'src/vs/sessions') and the activity ('changes', 'workflow router'), but lacks common user-spoken variations like 'Agents Window feature', 'sessions code', or synonyms a user would naturally say.

3 / 5

Distinctiveness Conflict Risk

The path-scoped niche ('src/vs/sessions', 'Agents Window') is fairly distinct from other skills, with only minor overlap risk against neighboring VS Code workbench skills; it is above the 'somewhat specific' anchor but short of a fully concrete trigger niche.

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
posit-dev/positron
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.