CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sessions

Session management, conversation history, and checkpoints

55

Quality

69%

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 ./src/skills/bundled/sessions/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 highly actionable and token-efficient, packed with executable code and tables. Its weaknesses are structural: it inlines a large API reference with no separate reference files, and destructive/batch operations lack validation checkpoints.

Suggestions

Move the bulk TypeScript API reference into a separate references file (e.g. REFERENCES.md) and keep only a quick-start example in SKILL.md.

Add explicit validation/confirmation steps for destructive and batch operations (e.g. verify checkpoint exists before delete, confirm before cleanup of old sessions).

Provide a short sequenced workflow (create session -> add messages -> checkpoint before risky change -> restore on error) with feedback checkpoints.

DimensionReasoningScore

Conciseness

The body is mostly lean code, commands, and tables with almost no padding of concepts Claude already knows; only minor prose (Best Practices, encryption bullets) could be trimmed, fitting the 'efficient; minor over-explanation' anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript and chat-command examples covering the common cases (create session, add/get/clear history, checkpoints, export, cleanup), matching the top anchor.

5 / 5

Workflow Clarity

This is a reference catalog rather than a sequenced workflow, and destructive/batch operations (clearHistory, reset, cleanup, deleteCheckpoint) lack validation or confirmation steps; per the rubric this caps workflow clarity at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the full TypeScript API reference (~150 lines) is inlined in SKILL.md with clear section headers but no external references, fitting the 'some structure but content that should be separate is inline' anchor.

3 / 5

Total

15

/

20

Passed

Description

53%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 a concise third-person capability statement with a clear niche, but it lacks an explicit 'Use when...' trigger clause and offers only generic verbs. It sits at the midpoint: a clear 'what' with weak 'when' guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when managing conversation sessions, history, checkpoints, or resets across channels'.

Replace generic nouns with concrete verbs (e.g. 'Create, reset, and checkpoint conversation sessions and export history').

Include natural synonyms/file markers users might say (e.g. 'session history', 'conversation log', 'checkpoints').

DimensionReasoningScore

Specificity

Names the session domain plus three concrete capability areas ("Session management, conversation history, and checkpoints"), but the verbs are generic and no concrete operations are enumerated, matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Provides a clear 'what' (session management, history, checkpoints) but no 'when'/'Use when...' trigger clause; per the rubric a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant natural terms ("session", "conversation history", "checkpoints") a user might say, but misses common variations/synonyms and explicit trigger phrases, fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The sessions niche is clearly scoped and unlikely to overlap with unrelated skills, with only minor overlap risk against closely related state/history skills, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

13

/

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

alsk1992/CloddsBot

Path

src/skills/bundled/sessions/SKILL.md

Revision

c930628

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill