CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-management

Implements secure session management with JWT tokens, Redis storage, refresh flows, and proper cookie configuration. Use when building authentication systems, managing user sessions, or implementing secure logout functionality.

Quality

83%

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

76%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 lean, code-driven skill that stays token-efficient and provides concrete implementation snippets for all major session-management concerns. Its main weaknesses are the absence of a sequenced implementation workflow with explicit validation checkpoints, and small gaps (undefined `cookieOptions`, missing imports, middleware shown only as a bullet) that keep the code from being fully copy-paste ready.

Suggestions

Add a short sequenced workflow (generate tokens → issue cookie → validate on each request via middleware → refresh → logout/invalidate) with explicit validation checkpoints, instead of presenting isolated thematic sections.

Define `cookieOptions` and show the per-request token-validation middleware as executable code so all snippets are copy-paste runnable.

Include a logout endpoint example (clearing cookies and calling `invalidateAll`) since 'secure logout functionality' is promised in the description but not shown in the body.

DimensionReasoningScore

Conciseness

The body is lean and code-first: each section opens with a heading and immediately shows code, with zero explanation of concepts Claude already knows (no "what is JWT" or "Redis is an in-memory store" padding). Every token earns its place — a direct match for anchor 5.

5 / 5

Actionability

Concrete, mostly executable code covers the common cases (token generation, Redis session store, cookie config, refresh endpoint), but there are minor gaps: `cookieOptions` is used but never defined, `crypto.randomUUID()` appears without an import, and per-request token-validation middleware exists only as a bullet. Anchor 4, not 5, because the snippets are not fully copy-paste ready.

4 / 5

Workflow Clarity

The body is organized as thematic sections rather than a sequenced process — there is no explicit generate → issue cookie → validate request → refresh → logout order, and validation appears only as an implicit bullet ("Validate signatures on every request") rather than as checkpointed steps. This matches anchor 3; it is above anchor 2 because the section ordering roughly implies a flow, but below anchor 4 which requires most checkpoints to be present in sequence.

3 / 5

Progressive Disclosure

No bundle files exist, and the ~100-line body is appropriately self-contained with clear section headers and no content that demands external files. It scores anchor 4 rather than 5 because it exceeds the under-50-line simple-skill threshold and offers no overview or navigation linking the sections into a whole — just well-organized but unconnected parts.

4 / 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 that clearly and explicitly states both what the skill does and when to use it, with concrete technology-specific triggers. The main weaknesses are minor: some natural trigger synonyms (login, sign-in) are missing and the broad authentication trigger slightly raises overlap risk with a general auth skill.

DimensionReasoningScore

Specificity

"JWT tokens, Redis storage, refresh flows, and proper cookie configuration" lists several specific capabilities with only minor gaps (the 'what' omits logout mechanics despite it appearing in the trigger clause). It falls short of anchor 5 because it uses a single verb ("Implements") with a component list rather than multiple concrete actions, and exceeds anchor 3's 1-2 actions.

4 / 5

Completeness

Explicitly answers both: the "what" ("Implements secure session management with JWT tokens, Redis storage, refresh flows, and proper cookie configuration") and the "when" ("Use when building authentication systems, managing user sessions, or implementing secure logout functionality") with concrete trigger phrases — a direct match for anchor 5.

5 / 5

Trigger Term Quality

"building authentication systems, managing user sessions, or implementing secure logout functionality" gives good coverage of natural phrases a user would say, but misses common variations like "login", "sign-in", or "token-based auth". Solidly anchor 4, not 5 (synonyms/extension-level coverage absent) and not 3 (several natural terms present).

4 / 5

Distinctiveness Conflict Risk

Session management with JWT/Redis/cookies is a clear niche, but the broad trigger "building authentication systems" creates minor overlap risk with a general authentication or login skill. Anchor 4 fits; anchor 5 would require narrower, less conflicting triggers.

4 / 5

Total

17

/

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

secondsky/claude-skills

Path

plugins/session-management/skills/session-management/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.