CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

skill-resume

Pick up where you left off from a previous session — use after context resets, compaction, or new conversations

Quality

74%

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 ./.claude/skills/skill-resume/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%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 a strongly actionable, well-validated workflow: every phase has executable commands, expected outputs, and explicit stop/error paths, and the routing logic is unambiguous. Its weaknesses are redundancy (four example outputs plus summary/quick-reference/bottom-line sections repeating the same content) and the absence of any progressive disclosure — everything, including ~150 lines of auxiliary material, lives inline in one long file.

Suggestions

Collapse Examples 2-4 into one canonical restoration example (they repeat the Phase 5 template with only field values changed) and remove the 'Quick Reference' and 'The Bottom Line' sections, which restate 'When to Use' and the core principle — this would address the conciseness gap.

Move the example outputs, 'Integration with Other Skills', and 'Best Practices' into a references/ file (e.g. references/examples.md) linked one level deep from a short '## Examples' section, giving the SKILL.md a lean overview as progressive disclosure expects.

Resolve the two actionability gaps: specify how to locate scripts/octo-state.sh (e.g. via the same OCTO_ROOT resolution used for feature-contract.py) and give a concrete worked invocation of feature-contract.py resume instead of the '<feature directory or spec path, empty when omitted>' placeholder.

DimensionReasoningScore

Conciseness

The body is mostly concrete commands and tables with no over-explanation of concepts Claude already knows, but it is noticeably padded: four near-duplicate example outputs (~115 lines) repeat the Phase 5 summary template, and 'Quick Reference', 'The Bottom Line', and 'Best Practices' restate earlier sections. This sits between anchors 2 and 3 — the issue is duplication rather than over-explanation — so 'mostly efficient but could be tightened' is the best fit.

3 / 5

Actionability

The skill gives copy-paste-ready bash ('octopus state-path', './scripts/octo-state.sh read_state', the grep/sed extraction commands) with expected output formats and display templates. It falls short of anchor 5 due to minor gaps: the feature-contract.py invocation embeds a '<feature directory or spec path, empty when omitted>' placeholder, and the location of './scripts/octo-state.sh' is assumed without resolution.

4 / 5

Workflow Clarity

Phases 0-6 are explicitly sequenced with per-step validation checkpoints ('.octo/' existence check, handoff-file check, 'Stop here - do not proceed to Phase 2', 'exit 1' on unresolvable state) and error-recovery feedback loops (the failed-restoration path with next-step guidance, and a per-status routing table covering nine statuses). This matches anchor 5: clear sequence, explicit validation, and error recovery; the skill is read-only, so the destructive-operation cap does not apply.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are all absent), so the entire ~540-line skill is one inline file. Sections are well-organized and navigable, but content that clearly belongs in separate reference files is inlined — the four full example outputs, 'Integration with Other Skills', and 'Best Practices' total roughly 150 lines of auxiliary material. The under-50-line simple-skill exception does not apply, so this fits anchor 3 ('some structure... content that should be separate is inline') better than anchor 4.

3 / 5

Total

15

/

20

Passed

Description

70%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 compact, natural-sounding, and correctly answers both 'what' and 'when', with an explicit and well-chosen set of usage moments. Its main weakness is that the 'what' is colloquial rather than concrete — it says "pick up where you left off" without naming any of the actual actions the skill performs.

Suggestions

Replace the colloquial 'pick up where you left off' with 2-3 concrete actions, e.g. 'Restores prior session state, displays recent history and blockers, and routes to the next workflow step' — this would lift specificity from 3 toward 4-5.

Include the most common trigger words ('resume', 'continue', 'restore session') inside the description itself rather than only in the trigger and aliases fields, since the description is what gets matched for skill discovery.

Narrow the overly broad 'new conversations' trigger (which matches virtually any session) to something like 'starting a new conversation on an existing project'.

DimensionReasoningScore

Specificity

"Pick up where you left off from a previous session" names the session-resumption domain with one colloquial action, but never states the concrete operations (read persisted state, load context tier, display history/blockers, route by status). This matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive'; score 4 would require several specific listed actions.

3 / 5

Completeness

Both parts are present: the 'when' is explicit ("use after context resets, compaction, or new conversations") and the 'what' is present ("pick up where you left off from a previous session"). Not anchor 5 because the 'what' is colloquial and imprecise — it doesn't say what the skill actually does.

4 / 5

Trigger Term Quality

"pick up where you left off", "context resets", "compaction", and "new conversations" are natural phrases users would say, giving good coverage. It falls short of anchor 5 because the most common terms — "resume", "continue", "restore session" — appear only in the separate trigger/aliases fields, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

Session restoration is a clear niche with dedicated triggers ("previous session", "context resets", "compaction"), so conflict risk is low. Minor overlap risk comes from the broad trigger "new conversations", which could match many situations; this fits 'mostly distinct; minor overlap risk' rather than anchor 5's 'minimal conflict risk'.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (555 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

nyldn/claude-octopus

Path

.claude/skills/skill-resume/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.