Automated summary
Guides the implementation of compliant cookie consent: cookie audit, categorization, banner, blocking before consent, consent records, and a withdrawal mechanism.
Strengths
- Covers the full lifecycle from cookie audit through to storing consent records
- Requires blocking non-essential cookies until consent is given, a step that is often skipped
- Explicitly includes consent withdrawal and granular preference management
Limitations
- Ships no ready-made code or banner template
- Stays generic about jurisdiction-specific requirements (CNIL, TCF, etc.)
- Does not cover non-browser aspects such as legal notices, privacy policy, or DPO responsibilities
Use it when a site serving EU/EEA users needs a cookie consent flow or consent-gated analytics.
Skip it when the site has no EU/EEA audience or only sets strictly necessary cookies that need no consent.
Security analysis
SafeThe skill contains only plain procedural guidance for implementing cookie consent UI and preference management. It declares no tools, runs no commands, touches no credentials, and performs no network or filesystem operations, so there is no meaningful execution risk.
No concerns found
How this analysis is madeExamples
Add a GDPR-compliant cookie banner to my Next.js site (no third-party CMP) with granular toggles for analytics and marketing, and make sure no analytics or marketing script fires before consent.Audit all the cookies and localStorage keys my app sets, categorize them as necessary, analytics, or marketing, and point to the code location where each one is set.Add a 'change my preferences' link in the footer that lets users withdraw consent and deletes any non-essential cookies already set.Cookie Consent Manager
Implement compliant cookie consent for websites.
When to Use
- Deploying websites in EU/EEA
- Need cookie preference management
- Implementing consent-based analytics
Instructions
- Audit all cookies used by the application
- Categorize cookies (necessary, analytics, marketing)
- Implement consent banner UI
- Add granular preference management
- Block non-essential cookies before consent
- Store consent records for compliance
- Implement consent withdrawal mechanism
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
No external provenance is recorded: only the copy on this page is available.
This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/cookie-consent-manager-d51ebe/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/cookie-consent-manager-d51ebe' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/cookie-consent-manager-d51ebe/download' --output '.skill-downloads/cookie-consent-manager-d51ebe/SKILL.md.part' && mv '.skill-downloads/cookie-consent-manager-d51ebe/SKILL.md.part' '.skill-downloads/cookie-consent-manager-d51ebe/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
This file does not provide a usable name/description header for this native procedure. It remains available to download and inspect; use the manual method below.
Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/cookie-consent-manager-d51ebe/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.