CtrlK
BlogDocsLog inGet started
Tessl Logo

autonomous-session-manager

Session lifecycle management for autonomous coding. Use when starting new coding sessions, resuming work, detecting session type (init vs continue), or managing auto-continuation between sessions.

64

Quality

78%

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/autonomous-session-manager/SKILL.md

The canonical home for this skill is autonomous-session-manager in fernandezbaptiste/Skrillz

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.

A well-structured, actionable skill body with clean progressive disclosure to real bundle files. The main gap is workflow clarity: the lifecycle is sequenced but lacks explicit validation checkpoints for the batch-like auto-continuation loop, capping that dimension at 3.

Suggestions

Add an explicit validation checkpoint in the END/auto-continue phase, e.g. 'Verify session completed successfully before calling auto_continue; on failure, save state and halt rather than continuing.'

Tighten redundancy between the ASCII lifecycle diagram, the Key Features table, and the Quick Start snippets — consider collapsing the diagram or table into the workflow narrative to recover tokens.

Replace placeholders in the code snippets (the 'pass' branches and undefined 'prompt') with minimal concrete usage so the examples are copy-paste runnable end-to-end.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence with noconcept-over-explanation, but the ASCII lifecycle diagram, the Key Features table, and the Quick Start all restate overlapping workflow information, giving minor trim opportunities that keep it just below the lean anchor.

4 / 5

Actionability

Three concrete, executable Python snippets (detect, create, auto-continue) plus a configuration dict cover the common cases, but they contain placeholders ('pass', undefined 'prompt') and incomplete async wiring, leaving minor gaps versus copy-paste-ready code.

4 / 5

Workflow Clarity

The Session Workflow diagram gives a clear DETECT -> CREATE -> RUN -> END sequence, but validation checkpoints are only implicit ('Check completion status') and auto-continuation is a batch operation with no validate->fix->retry feedback loop, so per the batch-operation cap it cannot exceed 3.

3 / 5

Progressive Disclosure

The body is a well-organized overview with one-level-deep, clearly signaled references (references/SESSION-LIFECYCLE.md, references/CONFIGURATION.md) and scripts (session_manager.py, session_detector.py, auto_continue.py), all of which exist in the bundle, with detail appropriately split out.

5 / 5

Total

16

/

20

Passed

Description

83%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.

A strong description with an explicit 'Use when' trigger clause and several concrete actions covering the session lifecycle. The main weakness is the abstract lead phrase and some missing synonyms, which cap specificity and trigger coverage at 4.

DimensionReasoningScore

Specificity

Enumerates several concrete actions ('starting new coding sessions', 'resuming work', 'detecting session type (init vs continue)', 'managing auto-continuation'), but the lead phrase 'Session lifecycle management' is a category label rather than a fully enumerated action set, leaving minor coverage gaps.

4 / 5

Completeness

It explicitly answers both 'what' ('Session lifecycle management for autonomous coding') and 'when' via a concrete 'Use when...' clause enumerating init/continue/detect/auto-continue triggers, matching the anchor for clear what-and-when with concrete trigger phrases.

5 / 5

Trigger Term Quality

The 'Use when' clause supplies natural phrases a user would say ('starting new coding sessions', 'resuming work', 'auto-continuation'), with good keyword coverage, though common synonyms like 'resume session' or 'continue automatically' are absent.

4 / 5

Distinctiveness Conflict Risk

The autonomous-coding session niche is clear and triggers are distinct, but there is minor overlap risk with closely related skills (the body names autonomous-loop and context-state-tracker integration), keeping it just below the minimal-conflict anchor.

4 / 5

Total

17

/

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.

Validation15 / 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
fernandezbaptiste/Skrillz
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.