CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-lifecycle

Compatibility alias for the task skill. Use only when the user explicitly invokes the older session-lifecycle name; otherwise use task for safe lifecycle transitions.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an exemplary alias skill: maximally lean, unambiguous in its single action, and correctly structured as a pure redirect that defers all procedure to the canonical task skill. There is no redundancy, no over-explanation, and no navigational ambiguity.

DimensionReasoningScore

Conciseness

The body is three terse numbered directives with no padding and no explanation of concepts Claude already knows; every token earns its place, matching the lean-and-efficient anchor exactly.

5 / 5

Actionability

Although it contains no code, it is an instruction-only skill whose guidance is fully concrete: an exact path to read (`.agents/skills/task/SKILL.md`), an exact naming policy (`task` in recommendations and docs), and an explicit single-source-of-truth rule, which the scoring notes state should not be penalized for lacking code.

5 / 5

Workflow Clarity

This is a simple single-purpose skill whose single action (delegate to the task skill's SKILL.md) is unambiguous, and the three steps are clearly sequenced; the simple-skill exception applies and no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

The skill is well under 50 lines, organized under a clear heading with a numbered list, and its single external reference (`.agents/skills/task/SKILL.md`) is one level deep and clearly signaled; no bundle files exist to structure, so the simple-skill organization standard is fully met.

5 / 5

Total

20

/

20

Passed

Description

61%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 well-scoped and explicitly answers both what the skill is and when to use it, with excellent conflict avoidance for an alias. Its main weakness is that it never states what the task skill concretely does beyond the vague phrase 'safe lifecycle transitions', leaving specificity and natural trigger coverage low.

Suggestions

Name 1-2 concrete capabilities of the underlying task skill (e.g., 'saves, restores, and cleanly ends agent sessions') instead of the generic phrase 'safe lifecycle transitions' to lift specificity.

Add natural trigger phrases users actually say when they need lifecycle help (e.g., 'end the session', 'save state', 'resume the session') so the description matches how requests are phrased.

Briefly state what a 'lifecycle transition' entails so the 'what' half of the description is as concrete as the 'when' half.

DimensionReasoningScore

Specificity

"Compatibility alias for the task skill" and "safe lifecycle transitions" name the domain but describe no concrete actions of the underlying capability, matching the anchor for minimal/generic actions rather than the 1-2 concrete actions required for a 3.

2 / 5

Completeness

Both 'what' (a compatibility alias for the task skill) and 'when' (use only on explicit invocation of the old name; otherwise use task) are explicitly present, but the 'what' is thin about actual capabilities, so it does not reach the fully concrete level of a 5.

4 / 5

Trigger Term Quality

The trigger is precise ("Use only when the user explicitly invokes the older session-lifecycle name") but the only keyword is the skill name itself; natural phrases users would say when they need lifecycle help (e.g., end session, save state, resume) are missing, matching the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The description actively deflects to the canonical skill ("otherwise use task") and scopes itself to explicit invocation of a specific legacy name, giving it a clear niche with minimal conflict risk.

5 / 5

Total

14

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

BigSimmo/PsychSift

Path

.agents/skills/session-lifecycle/SKILL.md

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.