sessions
Session management, conversation history, and checkpoints
65
51%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./src/skills/bundled/sessions/SKILL.mdQuality
Discovery
22%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 description is too abstract and noun-heavy, listing concepts rather than concrete capabilities. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill. The description needs to specify what actions can be performed and include explicit trigger conditions.
Suggestions
Add concrete action verbs describing what the skill does (e.g., 'Save and restore conversation state, create checkpoints, browse conversation history').
Include a 'Use when...' clause with explicit triggers (e.g., 'Use when the user wants to save progress, restore a previous session, or review past conversations').
Add natural language variations users might say (e.g., 'pick up where I left off', 'save my progress', 'go back to earlier conversation').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses abstract nouns ('session management', 'conversation history', 'checkpoints') without describing any concrete actions. It doesn't specify what operations can be performed with these concepts. | 1 / 3 |
Completeness | The description only vaguely addresses 'what' (listing concepts rather than capabilities) and completely lacks any 'when' guidance or explicit trigger conditions for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'session', 'conversation history', and 'checkpoints' that users might mention, but lacks common variations or natural phrases users would say (e.g., 'save progress', 'restore session', 'pick up where I left off'). | 2 / 3 |
Distinctiveness Conflict Risk | 'Session management' and 'conversation history' are somewhat specific to a domain, but without concrete actions or clear triggers, this could overlap with general state management or logging skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured API reference that excels in conciseness and actionability with clean, executable code examples. However, it lacks validation checkpoints for potentially destructive operations (like cleanup or restore) and could benefit from splitting advanced topics into separate files for better progressive disclosure.
Suggestions
Add validation/verification steps after checkpoint restore and session cleanup operations (e.g., 'Verify restoration: await sessions.getHistory(session.id) should show restored messages')
Include error handling examples for common failure scenarios (e.g., restoring non-existent checkpoint, encryption key mismatch)
Consider splitting encryption details and context window management into separate reference files with links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting API references and commands without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable TypeScript code examples that are copy-paste ready, along with concrete chat commands. All examples include realistic parameters and expected outputs. | 3 / 3 |
Workflow Clarity | While individual operations are clear, the skill lacks explicit validation checkpoints or error handling guidance. For operations like checkpoint restore or session cleanup, there's no feedback loop for verifying success or handling failures. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's a monolithic document with no references to external files for advanced topics. The encryption, context window management, and cleanup sections could be split into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- alsk1992/CloddsBot
- Commit
2a8c94e
- 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.