CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

analyse-sessions

Use when reading the session-performance cards to find where agent effort is going — running the report over `.claude/metrics/`, interpreting it without the traps that have already produced two wrong findings, and reporting what is actually supported. Also the step before proposing any change to how work is dispatched.

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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.

An exemplary instruction-only skill: copy-paste-ready commands, a validated workflow with explicit gates, and hard-won project-specific judgment (the six traps) that Claude could not reconstruct on its own. The only trimmable fat is slight narrative padding around the historical failures, and the long inline traps section is a marginal disclosure opportunity.

DimensionReasoningScore

Conciseness

The body is dense and earns nearly every token: commands, project-specific data (median 3.6M vs mean 15.4M), and failure cases Claude could not know. It sits at 4 rather than 5 because the two-wrong-findings narrative in "Why the order below matters" and a handful of long rhetorical sentences (e.g., "offering the answerable ones as though they were the whole picture is how a partial view becomes a wrong one") could be tightened without losing content.

4 / 5

Actionability

Guidance is fully executable: copy-paste-ready commands (`bun run --cwd tools/pr-metrics report -- --coverage`, the `gh pr diff … | grep -E` dependency-bump check), concrete flag semantics (`--json` carries notes, `--split-at <commit>`), and a precise output contract (number, sample, exclusions, what would overturn it). This matches the 5 anchor for an instruction-only skill per the code_vs_instruction scoring note.

5 / 5

Workflow Clarity

The sequence is explicit and justified (Step 0 coverage → Step 1 run what you need → Step 2 report) with real validation gates: "write them down before continuing", "If nothing is rated, say so at the top of your answer", per-claim exclusions and falsifiers, and a hard rule against unsupported recommendations. These are explicit checkpoints with error-recovery guidance, matching the 5 anchor; the 4 anchor's "minor validation gaps" is not in evidence.

5 / 5

Progressive Disclosure

No bundle files exist, so this scores on body structure: clear section headers, well-signaled one-level pointers to external material (`tools/pr-metrics/queries.sql`, `wiki/conventions/session-metrics.md`, `tools/pr-metrics/README.md` in "What consumes this"), and appropriately routed handoffs to sibling skills. It stops short of 5 because at ~139 lines everything is inlined — the six-traps section (~60 lines) is arguably reference material — and the skill exceeds the under-50-lines exception for a sections-only 5.

4 / 5

Total

18

/

20

Passed

Description

83%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.

A strong, niche-appropriate description with an explicit Use-when clause, concrete actions, and a real path reference. Its only weaknesses are mild: a few missing natural synonyms (spend/cost/tokens) and no explicit differentiation from the sibling `retro` skill.

DimensionReasoningScore

Specificity

The description names several concrete actions — "reading the session-performance cards", "running the report over `.claude/metrics/`", "interpreting it without the traps", "reporting what is actually supported" — with a concrete path. It falls short of the 5 anchor because coverage is not comprehensive: the report tool itself and the SQL fallback are only identified in the body, and "find where agent effort is going" states the goal rather than an action.

4 / 5

Completeness

Both halves are explicit: the what ("running the report over `.claude/metrics/`, interpreting it … and reporting what is actually supported") and two concrete when clauses ("Use when reading the session-performance cards", "Also the step before proposing any change to how work is dispatched"). This matches the 5 anchor's explicit what-and-when with concrete triggers; the 4 anchor's "when could be more explicit" does not apply.

5 / 5

Trigger Term Quality

Natural domain terms are present — "session-performance cards", "agent effort", "`.claude/metrics/`", "how work is dispatched" — phrases a user of this repo would plausibly say. It sits below the 5 anchor because common variations like "spend", "cost", "tokens", or "session metrics" as a plain phrase are absent, leaving a few natural entry points uncovered.

4 / 5

Distinctiveness Conflict Risk

The corpus-level scope ("reading the session-performance cards", ".claude/metrics/", dispatch changes) carves a clear niche with low conflict risk. It is not a 5 because the body reveals a closely related sibling skill (`retro`, per-session card analysis) that the description never distinguishes itself from, leaving minor overlap risk on card-related requests.

4 / 5

Total

17

/

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

englishstreetventures/osn

Path

.claude/skills/analyse-sessions/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.