CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

session-cookie-flags

Use when reviewing server-side session management, setting up authentication middleware, or auditing cookie configuration in HTTP response headers.

Quality

74%

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 ./skills/session-cookie-flags/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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, well-structured review skill body that defers implementation detail appropriately to a verified reference file, with concrete review criteria. Its main inefficiency is re-explaining basic cookie-flag security concepts that Claude already knows, both in the intro paragraph and again in the Quick Reference.

Suggestions

Cut or merge the intro paragraph and Quick Reference — both explain what Secure/HttpOnly/SameSite prevent, which Claude already knows; keep only the non-obvious guidance (e.g., the SameSite=None caveat).

Add a short re-verification step after Fix (e.g., re-inspect Set-Cookie headers to confirm flags are applied) to close the workflow's validation gap.

DimensionReasoningScore

Conciseness

The opening paragraph explains attack concepts Claude already knows ("Without Secure, session tokens are transmitted in plain text over HTTP...", "Without HttpOnly, any XSS payload can exfiltrate the session token"), and the Quick Reference bullets re-explain the same flags ("Secure — cookie is only sent over HTTPS"), duplicating that material. The body is short and well-organized, so it is not noticeably padded (anchor 2), but the known-concept explanation and duplication keep it below anchor 4's efficient bar.

3 / 5

Actionability

Concrete, specific guidance: "Flag any cookies missing the HttpOnly flag, absent Secure flag, or an unspecified or overly permissive SameSite setting" and "include Secure, HttpOnly, and SameSite=Strict (or Lax) on all session and auth cookies" give precise criteria. Per the rubric's instruction-only note, missing inline code is not penalized, but no example (e.g., a correct Set-Cookie line) appears in the body itself — it lives one reference hop away — so it falls short of anchor 5's copy-paste-ready examples.

4 / 5

Workflow Clarity

Clear task-oriented structure (Check → Fix → Explain → Code Review) with unambiguous review instructions naming exact targets ("Review all Set-Cookie headers and cookie creation code"). Minor gaps: no re-verification step after applying the fix, and the Check section overlaps the more specific Code Review section, keeping it below anchor 5.

4 / 5

Progressive Disclosure

The body is under 50 lines with well-organized sections and a single, clearly signaled one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md". Verified against the actual bundle: references/rule.md exists and delivers exactly what is promised (Set-Cookie code example, framework-specific implementation guidance).

5 / 5

Total

16

/

20

Passed

Description

66%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 trigger-focused description with an explicit, well-targeted "when" clause covering three concrete scenarios, but it omits any statement of what the skill actually does. Adding a what-clause (e.g., "Set or verify Secure, HttpOnly, and SameSite flags on session cookies") plus the flag names would raise both completeness and trigger quality.

Suggestions

Lead with a what-statement before the trigger clause, e.g. "Set and verify Secure, HttpOnly, and SameSite flags on session and authentication cookies. Use when reviewing session management, setting up authentication middleware, or auditing Set-Cookie headers."

Include the flag names users naturally mention — "Secure", "HttpOnly", "SameSite", "cookie flags", "Set-Cookie" — to improve trigger term coverage.

Avoid the slightly generic "setting up authentication middleware" trigger, which overlaps broader auth-setup skills; prefer cookie-specific phrasing.

DimensionReasoningScore

Specificity

The description lists several concrete action contexts — "reviewing server-side session management", "setting up authentication middleware", "auditing cookie configuration in HTTP response headers" — each with specific technical objects. It falls short of 5 because it never states the skill's own action (setting or verifying the Secure, HttpOnly, and SameSite flags), leaving a coverage gap.

4 / 5

Completeness

The "when" is explicit and detailed (three concrete trigger scenarios in "Use when reviewing... setting up... or auditing..."), which exceeds the vague when-only pattern of anchor 2. However, no "what" is ever stated — the description never says the skill sets or verifies cookie flags — so it cannot reach anchor 4's both-what-and-when bar.

3 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say: "session management", "authentication middleware", "cookie configuration", "HTTP response headers". Not 5 because the most distinctive natural triggers for this exact skill are missing — "Secure", "HttpOnly", "SameSite", "cookie flags", "Set-Cookie", "session cookies".

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (session cookie configuration in HTTP headers) with distinct trigger terms, so conflict risk is low. Minor overlap remains with broader authentication-setup or general security-review skills, e.g. "setting up authentication middleware" could also match a general auth-configuration skill.

4 / 5

Total

15

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/session-cookie-flags/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.