CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-report

Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts.

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/session-report/skills/session-report/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A tight, highly actionable skill body that stays lean and gives exact commands and markup, with a clear step sequence and sensible contingencies. Its main weaknesses are the absence of any post-edit validation step and that the two bundled files it depends on are not actually present in the skill directory.

Suggestions

Add an explicit validation checkpoint before reporting the path, e.g. confirm the embedded JSON blob parses (or spot-check that the hero total renders from overall.input_tokens.total) so a truncated or malformed embed is caught.

Ship the referenced bundle files (analyze-sessions.mjs and template.html) in the skill directory, or document their flags and template placeholders inline so the skill is self-contained and verifiable.

Replace the <skill-dir> placeholder guidance with a concrete resolution note (e.g. how to derive the skill directory at runtime) so the commands are truly copy-paste ready.

DimensionReasoningScore

Conciseness

The ~40-line body is lean and imperative throughout — numbered steps, exact shell commands, exact HTML markup for findings, and a short Notes section — with zero explanation of concepts Claude already knows and no padding, matching the 'every token earns its place' anchor.

5 / 5

Actionability

Concrete, near-executable guidance: exact commands ("node <skill-dir>/analyze-sessions.mjs --json --since 7d > /tmp/session-report.json", "cp <skill-dir>/template.html ./session-report-$(date +%Y%m%d-%H%M).html"), verbatim output markup, and named JSON fields to read. It falls short of fully copy-paste-ready because of the unresolved <skill-dir> placeholder and reliance on a bundled script whose flags cannot be verified (the referenced analyze-sessions.mjs is not present in the skill directory).

4 / 5

Workflow Clarity

A clear 5-step sequence with a contingency (trim top_prompts/cache_breaks if JSON >2MB) and a preservation guard ("use Edit, not Write — preserve the template's JS/CSS"), but there is no explicit validation checkpoint (e.g. verifying the embedded JSON parses or the report renders) before reporting the file path. This is a minor validation gap rather than the feedback-loop-rich 5 anchor; the operations are non-destructive, so the destructive/batch cap at 3 does not apply.

4 / 5

Progressive Disclosure

The body itself is well organized into Steps/Notes and appropriately delegates implementation to two bundled files, but those referenced files (analyze-sessions.mjs and template.html, referenced via "<skill-dir>/...") do not exist in the skill directory — no scripts/, references/, or assets/ bundles are present — so the references cannot be verified and the skill's structure is incomplete as shipped, fitting the 'some structure but could be better organized / references not verifiable' middle anchor.

3 / 5

Total

16

/

20

Passed

Description

66%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 specific, well-scoped description with strong natural keywords and a clearly distinct niche, but it omits any "when to use" trigger guidance, which caps completeness. Adding a "Use when..." clause naming the situations and phrasings users would naturally employ would lift it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks about their Claude Code token usage, session costs, cache efficiency, or wants a session/cost report."

Include common user phrasings as synonyms ("token spend", "cost report", "usage breakdown") so natural requests match the description.

Optionally mention that the report surfaces anomalies and optimization suggestions, since that analysis is a real capability of the skill not reflected in the description.

DimensionReasoningScore

Specificity

"Generate an explorable HTML report of Claude Code session usage (tokens, cache, subagents, skills, expensive prompts) from ~/.claude/projects transcripts" names a concrete action, the report's coverage areas, and the data source, with only minor gaps (no mention of the anomaly/optimization analysis the body actually performs). It falls short of the 5 anchor because it lists one primary action rather than multiple distinct concrete actions, and is well above 3, which covers only 1-2 actions with no scope detail.

4 / 5

Completeness

The "what" is clear and specific, but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description; the judging guidelines explicitly cap completeness at 3 for a missing "when", and this is not the vague-"what" case of 2.

3 / 5

Trigger Term Quality

Good natural keyword coverage — "session usage", "tokens", "cache", "subagents", "expensive prompts", "transcripts" — but common user phrasings like "token spend", "cost report", or "usage breakdown" are absent, matching the 'good coverage, a few natural terms missing' anchor rather than the comprehensive-synonym coverage of 5.

4 / 5

Distinctiveness Conflict Risk

The niche is clear and unusually specific (Claude Code session transcripts from ~/.claude/projects rendered as an HTML report), with minimal overlap risk; it stops short of 5 because without explicit triggers it could collide with adjacent cost/usage-analysis skills, fitting 'mostly distinct; minor overlap risk'.

4 / 5

Total

15

/

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

anthropics/claude-plugins-official

Path

plugins/session-report/skills/session-report/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.