sessions

Session management, conversation history, and checkpoints

Quality

32%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./src/skills/bundled/sessions/SKILL.md

Quality

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 a bare noun-phrase list with no verbs, no explicit trigger guidance, and no concrete actions. It fails to communicate what the skill actually does or when Claude should select it. While the domain terms provide some signal, the description would be easily confused with other skills and gives Claude insufficient information to make a confident selection.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Saves and restores conversation sessions, searches chat history, creates and loads checkpoints for resuming work.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to save progress, resume a session, view past conversations, or create/restore checkpoints.'

Include common user-facing synonyms and variations such as 'save progress', 'resume', 'chat history', 'restore state', 'bookmark' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description lists abstract nouns ('session management', 'conversation history', 'checkpoints') but no concrete actions. There are no verbs describing what the skill actually does—it doesn't say 'save sessions', 'restore checkpoints', 'search conversation history', etc.	1 / 3
Completeness	The description only vaguely hints at 'what' (session management, history, checkpoints) without specifying concrete capabilities, and completely lacks any 'when' guidance or explicit trigger clause.	1 / 3
Trigger Term Quality	Terms like 'session', 'conversation history', and 'checkpoints' are somewhat relevant keywords a user might mention, but the description lacks common variations or natural phrasing (e.g., 'save progress', 'resume session', 'chat history', 'restore state').	2 / 3
Distinctiveness Conflict Risk	The terms 'session management' and 'checkpoints' provide some specificity to a niche, but 'conversation history' is broad enough to overlap with logging, analytics, or search skills. Without concrete actions, the boundaries are unclear.	2 / 3
	Total	6 / 12 Passed

Implementation

42%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads as a comprehensive API reference document rather than a focused skill file. While the code examples are excellent and fully actionable, the content is far too verbose for a SKILL.md — it should be a concise overview pointing to detailed reference files. The lack of a cohesive workflow tying the pieces together and the monolithic structure significantly reduce its effectiveness as a skill.

Suggestions

Split into a concise SKILL.md overview (quick start + key commands) with references to separate files like COMMANDS.md, API_REFERENCE.md, and ENCRYPTION.md

Add a sequenced workflow showing a typical session lifecycle: create → interact → checkpoint → restore → cleanup, with validation at key steps

Remove the best practices section (generic advice Claude already knows) and the encryption implementation details (move to a separate file)

Trim the TypeScript examples to 2-3 key operations in the main file, linking to a full API reference for the rest

Dimension	Reasoning	Score
Conciseness	This is essentially a full API reference dump that Claude doesn't need memorized in a skill file. It includes extensive code examples for every method, tables explaining basic concepts, and a best practices section with generic advice. Much of this could be in a separate REFERENCE.md, and Claude could infer most usage patterns from a few key examples.	1 / 3
Actionability	The code examples are concrete, executable TypeScript with realistic parameters and complete method signatures. Chat commands are clearly formatted with examples. Every API method has copy-paste ready code.	3 / 3
Workflow Clarity	Individual operations are clear, but there's no sequenced workflow showing how these pieces fit together (e.g., create session → add messages → checkpoint → restore flow). The checkpoint restore operation is destructive but lacks validation/confirmation steps.	2 / 3
Progressive Disclosure	This is a monolithic wall of content (~200 lines) with the entire API reference inline. The chat commands, TypeScript API, scopes, encryption details, and context window management should be split into separate reference files with the SKILL.md providing a concise overview and navigation.	1 / 3
	Total	7 / 12 Passed

Validation

90%

Warnings & errors only

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: e71a5f6

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.