Cookie debugging — diagnose cookies, auth, tracking and consent with Chrome DevTools MCP

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://github.com/chromedevtools/chrome-devtools-mcp/blob/main/skills/cookie-debugging/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 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.