CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-flow

Reorient in the current Claude Code session with an evidence-backed map of its goal, pivots, outcomes, current step, and open decisions.

Quality

82%

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

100%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 body is an exemplary instruction-only skill: dense but not padded, with exact markers, tool calls, status mappings, and an output template that make the behavior fully reproducible. Validation checkpoints around the destructive Task mutations and a fallback for missing tools make the workflow robust, and the compact single-file structure fits its scope perfectly.

DimensionReasoningScore

Conciseness

The ~40-line body is lean with zero padding: it never explains concepts Claude already knows (no "what a session is" or "what Tasks are" filler), and every sentence is an operating instruction, evidence rule, or format constraint that earns its place.

5 / 5

Actionability

Guidance is fully executable for an instruction-only skill: exact tool names (TaskList, TaskGet, TaskCreate, TaskUpdate) with exact statuses, a verbatim ownership marker line ("session-flow: managed stage"), explicit status-mapping rules, a 15-line budget, and a copy-paste output template with per-stage symbols — no pseudocode or vague direction.

5 / 5

Workflow Clarity

Nine clearly sequenced steps span three modes, and the destructive operation (deleting Tasks) is gated by explicit validation — inspect every [S<number>] candidate with TaskGet before mutating, ownership requires both the subject prefix and the exact marker, "Never edit, complete, delete, or reuse an unmarked Task" — plus an error-recovery fallback (step 9) when Task tools are unavailable.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no bundle files (references/, scripts/, assets/ are absent) and needs none; content is well organized into ## Modes, ## Workflow, and ## Output sections, which satisfies the simple-skill exception for a top progressive-disclosure score.

5 / 5

Total

20

/

20

Passed

Description

58%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 states a clear, specific "what" with an enumerated artifact scope, but omits any explicit "when to use" trigger guidance and lacks the natural phrasings a user would say when they need session reorientation. It is specific and mostly distinct, yet incomplete as a router signal.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user asks to reorient, catch up on, or summarize the current session, especially after switching sessions or compacting the conversation."

Include natural user phrasings and synonyms such as "session summary", "where were we", "what changed since last time", and "after compaction" to improve trigger-term coverage.

Mention the short/reset variants' existence in the description or hint so users can discover the lightweight catch-up mode.

DimensionReasoningScore

Specificity

The description enumerates concrete deliverable components — "evidence-backed map of its goal, pivots, outcomes, current step, and open decisions" — which is several specific elements, though they all serve one artifact (the map) rather than distinct operations, leaving minor coverage gaps versus a fully comprehensive action list.

4 / 5

Completeness

The "what" is clear and concrete (build an evidence-backed map with enumerated components), but the "when" is absent with no "Use when..." clause or equivalent explicit trigger guidance — "Reorient in the current session" only weakly implies the triggering situation, capping this at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like "Reorient", "current Claude Code session", "current step", and "open decisions" are relevant to the domain, but common natural variations users would actually say — e.g. "summarize the session", "catch me up", "where were we", "after compaction" — are missing.

3 / 5

Distinctiveness Conflict Risk

The description carves a fairly distinct niche — session reorientation mapping with evidence pointers — and its vocabulary (pivots, open decisions, current step) is unlikely to fire for unrelated skills, though it could slightly overlap with generic conversation-summarization skills.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

Yeachan-Heo/oh-my-claudecode

Path

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