shine-cookie-scan

Classify cookies from a public URL into GDPR compliance categories.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-cookie-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shine-cookie-scan
Source: https://github.com/diShine-digital-agency/SHINE-Code-System/tree/main/skills/shine-cookie-scan
Command: npx skills add https://github.com/diShine-digital-agency/SHINE-Code-System --skill shine-cookie-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans a public URL to detect cookies set by the page and classifies them into categories for GDPR compliance, privacy reporting, and cookie-consent audits.

Core Features & Use Cases

  • Primary: cookie-audit CLI (Playwright-based) detects JavaScript-injected cookies.
  • Secondary: curl -sI to capture Set-Cookie headers (may miss runtime cookies).
  • Fallback: WebFetch to observe document cookies, with documented limitations.
  • Classifies cookies into Strictly necessary, Preferences, Statistics, and Marketing to support GDPR/privacy workflows.

Quick Start

Provide a public URL to scan and obtain a categorized cookie report.

Frequently Asked Questions about shine-cookie-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify cookies on a public website for GDPR compliance?

You can classify cookies for GDPR compliance by providing a public URL to the scanner. It detects cookies via a primary CLI, curl headers, or WebFetch fallback, then outputs a categorized report with a GDPR verdict.

How does a cookie audit detect JavaScript-injected cookies versus server-set cookies?

A cookie audit detects JavaScript-injected cookies using a Playwright-based CLI, while server-set cookies are captured via curl -sI headers. A WebFetch fallback observes runtime document cookies to ensure comprehensive capture.

What cookie categories are used when generating a privacy report?

When generating a privacy report, detected cookies are classified into four GDPR categories: Strictly necessary, Preferences, Statistics, and Marketing. This categorization supports cookie-consent audits and privacy workflows.

Can I use a curl header scan to capture all runtime cookies on a webpage?

You cannot capture all runtime cookies using only a curl header scan, because curl -sI may miss JavaScript-injected cookies. The primary Playwright-based CLI or WebFetch fallback is required to observe dynamically set document cookies.

What are the limitations of using WebFetch for cookie scanning?

The limitation of using WebFetch for cookie scanning is its documented inability to reliably capture all dynamically injected cookies. It serves as a fallback observing document cookies when the primary CLI and curl approaches are unavailable.