ambaba/session-resume
Write session resume cards at end of work and restore them at session start.
93
96%
Does it follow best practices?
Impact
84%
1.23xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid, concise description that clearly communicates both purpose and trigger conditions. The 'Use when' clause with natural trigger phrases is well done. The main weakness is that the specificity of capabilities could be improved by describing what a session resume card actually contains or what information is captured/restored.
Suggestions
Add more detail about what session resume cards contain (e.g., 'Captures current task state, open files, pending items, and context into a resume card').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (session resume cards) and two actions (write at end, restore at start), but doesn't elaborate on what a 'session resume card' contains or what specific operations are involved beyond write/restore. | 2 / 3 |
Completeness | Clearly answers both 'what' (write session resume cards at end of work and restore them at session start) and 'when' (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural phrases users would actually say: 'save progress', 'where did I leave off', 'resume', 'continue', 'pick up' — these are excellent natural language triggers covering common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Session resume cards are a very specific niche concept unlikely to conflict with other skills. The trigger terms are focused on session continuity and progress saving, which is a distinct use case. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, lean skill that provides precise, actionable guidance for session resume card management. The good/bad example contrast is particularly effective at communicating quality expectations. The rules section adds important safety constraints (no PII, no secrets) without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what sessions are or how markdown works. The good/bad example contrast is efficient and highly informative without being verbose. | 3 / 3 |
Actionability | Provides a concrete file path, exact format template with date pattern, a good vs bad example that makes the quality bar crystal clear, and specific rules about what not to include. Claude knows exactly what to do. | 3 / 3 |
Workflow Clarity | Both save and resume workflows are clearly sequenced with numbered steps. The task is simple enough that no validation checkpoint is needed—there's no destructive or batch operation. The two workflows (save/resume) are cleanly separated. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with a single focused purpose, the content is well-organized with clear sections (when to use, file location, save steps, resume steps, rules). No external references are needed and none are artificially created. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents