Cookie debugging — diagnose cookies, auth, tracking and consent with Chrome DevTools MCP
Inspect cookie attributes (Secure, HttpOnly, SameSite, Partitioned), debug login failures, third-party cookie breakage, consent banners, and trace cross-site auth flows in Chrome
- What
- Inspect cookie attributes (Secure, HttpOnly, SameSite, Partitioned), debug login failures, third-party cookie breakage, consent banners, and trace cross-site auth flows in Chrome
- Cost
- Free
- Needs
- the Chrome DevTools MCP server configured in the agent environment — the skill is a diagnostic playbook the agent executes through it, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @chromedevtools's cookie-debugging skill: a diagnostic playbook for cookies, authentication, tracking and consent, run through the Chrome DevTools MCP. Inspect cookie attributes (Secure, HttpOnly, SameSite, Partitioned/CHIPS), debug why logins fail, diagnose third-party cookie breakage after Chrome's deprecation, fix consent-banner interactions, and trace cross-site authentication flows — with a testing checklist for cookie-related regressions. Honest caveats: requires the Chrome DevTools MCP server configured in your agent environment — without it the agent can't execute the diagnostics; this is a debugging guide, not a privacy tool. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Cookie debugging is a free diagnostic playbook for cookies, authentication, tracking and consent, run through the Chrome DevTools MCP. It inspects cookie attributes like Secure, HttpOnly, SameSite and Partitioned, debugs login failures, diagnoses third-party cookie breakage, handles consent banners, and traces cross-site auth flows in Chrome.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 3712dfdStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: the Chrome DevTools MCP server configured in the agent environment — the skill is a diagnostic playbook the agent executes through it, not software Install "Cookie debugging — diagnose cookies, auth, tracking and consent with Chrome DevTools MCP" for me. It gives my agent @chromedevtools's cookie diagnostic playbook: inspect cookie attributes (Secure, HttpOnly, SameSite, Partitioned/CHIPS), debug login failures, diagnose third-party cookie breakage, fix consent-banner interactions, trace cross-site auth flows, plus a cookie testing checklist. NOTE: the Chrome DevTools MCP must be configured or the agent can't execute the diagnostics. Apache-2.0 licensed. Repository: https://raw.githubusercontent.com/chromedevtools/chrome-devtools-mcp/3712dfd60d57460a666f8dfe484ced03779255c3/skills/cookie-debugging/SKILL.md Pinned version: install the code at commit 3712dfd60d57460a666f8dfe484ced03779255c3 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "cookie-debugging". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. confirm the Chrome DevTools MCP server is configured in my agent environment; nothing else — it's a diagnostic playbook). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 3712dfd · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.