CtrlK
BlogDocsLog inGet started
Tessl Logo

evaluate-sessions

Evaluate the build trail of a PR — read the claude -p sessions the harness ran to build it, find where the project's context (Expert / AGENTS.md / skill / spec) served or failed the agents, then capture the learnings as evals (regression tests over the harness's own skills/context) and context fixes. Use when resolving a STUCK (diagnosis-first), auditing how a converged PR was built, or auditing a /learn memory PR. Human-driven and conversational — the trail-evaluating sibling of /evaluate-pr. Outcomes land on a branch (the PR's, or a fresh capture branch if you'll discard the PR) and reach memory via merge + /learn. Triggers - evaluate-sessions, evaluate sessions, review the build trail, diagnose stuck, audit how this was built, session observability.

72

Quality

88%

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

The canonical home for this skill is evaluate-sessions in tdg-ninja/context-specs-factory-ai

SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured, actionable instruction-only skill with a clear multi-step workflow, validation checkpoints, and excellent progressive disclosure to real bundle files. Its main weakness is conciseness — the motivational framing is repeated across the body and references — and a few exact commands for the discard path are deferred rather than inlined.

Suggestions

State the 'flywheel / bigger picture — tell the human' framing once (in the philosophy block) and drop its repetitions in the intro and in references/evals.md to recover token budget without losing the point.

Inline the exact git commands for the discard/capture-branch path in Step 6 (e.g. 'git checkout -b capture/<slug> origin/main', commit, 'git push -u origin capture/<slug>', 'gh pr create') instead of prose deferring to references/outcomes.md, making the workflow fully copy-paste executable.

Trim the 'Why this is exciting (tell the human)' pep-talk sections in the references to a single sentence each; the discipline content they surround is what earns the tokens.

DimensionReasoningScore

Conciseness

The body is mostly efficient and project-specific (it does not explain concepts Claude already knows), but the motivational 'bigger picture / tell the human this framing' pep-talk recurs in the intro, the S-philosophy block, and the references, and could be tightened to a single statement.

3 / 5

Actionability

Provides concrete, executable guidance — 'scripts/resolve-sessions.sh <PR#|feature>', 'gh pr view <pr> --json comments', 'git push origin HEAD:<branch>', 'git checkout main', the four lenses, and the S9 routing destinations — but the discard/capture-branch path in Step 6 is prose deferring exact git commands to references/outcomes.md, a minor gap.

4 / 5

Workflow Clarity

Steps 0–7 are clearly sequenced with explicit validation checkpoints — clean-tree preflight, human-confirmed classification in Step 4, explicit human choice before landing in Step 6, return-to-main in Step 7 — plus the 'Hard nevers' checklist, so the destructive/branch cap does not apply.

5 / 5

Progressive Disclosure

The body is an overview pointing to four real one-level-deep references (trace-reading.md, evals.md, outcomes.md, observability-tooling.md) and one real script (resolve-sessions.sh), each clearly signaled with a description of its contents and hackable-seam markers; navigation is easy and nothing is nested beyond one level.

5 / 5

Total

17

/

20

Passed

Description

100%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, third-person description that explicitly states concrete actions, includes both a 'Use when' clause and a dedicated triggers list, and cleanly distinguishes itself from the sibling /evaluate-pr skill. It is somewhat long but conciseness is not a scored dimension here and the content is substantive rather than padded.

DimensionReasoningScore

Specificity

Names multiple concrete actions — 'read the claude -p sessions the harness ran', 'find where the project's context... served or failed the agents', 'capture the learnings as evals (regression tests over the harness's own skills/context) and context fixes', 'Outcomes land on a branch' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly answers both 'what' (evaluate the build trail, capture evals and context fixes) and 'when' (the 'Use when...' clause with concrete trigger phrases), matching the anchor that explicitly answers both with concrete triggers.

5 / 5

Trigger Term Quality

Both an explicit 'Use when resolving a STUCK..., auditing how a converged PR was built, or auditing a /learn memory PR' clause and a dedicated 'Triggers - evaluate-sessions, evaluate sessions, review the build trail, diagnose stuck, audit how this was built, session observability' list provide comprehensive natural-term coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

Carves a clear niche — 'the trail-evaluating sibling of /evaluate-pr', evaluating how a PR was built rather than what was built — with distinct triggers and minimal overlap risk.

5 / 5

Total

20

/

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
tdg-ninja/context-specs-claude-code
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.