CtrlK
BlogDocsLog inGet started
Tessl Logo

cookie-debugging

Uses Chrome DevTools MCP for inspecting, debugging, and testing cookies, session state, authentication issues, and cookie consent compliance. Use when diagnosing 401/403 errors, authentication redirects, session expiration, Cookie/Set-Cookie header issues, cookie banner consent conformance, or third-party cookie/SameSite/Partitioned cookie warnings.

76

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 dense, highly actionable skill body with well-sequenced workflows, explicit validation checkpoints, and executable examples. Minor conciseness gains are possible by trimming well-known cookie-attribute explanations.

Suggestions

Tighten the cookie-attribute explanations in the 401/403 workflow (Path/Domain/Secure/SameSite bullets) to rely on Claude's existing knowledge, keeping only the DevTools-MCP-specific diagnostic steps.

Consider moving the Lighthouse deep-audit and CHIPS partitioning details into a referenced file so the core SKILL.md stays a lean overview.

The HttpOnly-vs-client-side intro re-explains a browser security concept; condense to the tool-implication difference only.

DimensionReasoningScore

Conciseness

Mostly lean with dense tables and copy-paste snippets, but retains some explanation of cookie semantics Claude already knows (Path/Domain mismatch, Secure-on-HTTP, SameSite=Strict blocking) that could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout — exact tool calls (get_network_request, list_network_requests, evaluate_script), JSON configs, cookieStore code blocks, and a bash one-liner for Lighthouse report extraction.

5 / 5

Workflow Clarity

Four numbered workflows with explicit validation/verification checkpoints (baseline cookie recording, consent-difference assertion, console issue checks) and teardown (close_page) plus error-recovery guidance in Troubleshooting.

5 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections (Core Concepts, Workflow Patterns, Troubleshooting) and no nested references, though a 150-line doc with four detailed workflows could optionally split advanced material into referenced files.

4 / 5

Total

18

/

20

Passed

Description

100%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 tightly scoped, third-person description that pairs concrete capabilities with a rich 'Use when' trigger clause. It is comprehensive, distinct, and free of fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'inspecting, debugging, and testing cookies, session state, authentication issues, and cookie consent compliance' — with comprehensive coverage of the domain.

5 / 5

Completeness

Explicitly answers both 'what' (inspect/debug/test cookies and session/auth state) and 'when' via a 'Use when diagnosing...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural user/dev phrases are densely covered: '401/403 errors', 'authentication redirects', 'session expiration', 'Cookie/Set-Cookie header issues', 'SameSite/Partitioned cookie warnings', including synonyms and spec-specific terms.

5 / 5

Distinctiveness Conflict Risk

Narrow Chrome DevTools MCP + cookie/auth niche with highly specific triggers (Set-Cookie, SameSite, Partitioned/CHIPS) yields minimal overlap with other skills.

5 / 5

Total

20

/

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
ChromeDevTools/chrome-devtools-mcp
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.