Agent skill

Managing Consent For Children

by mukul975 in mukul975/Privacy-Data-Protection-Skills

Guide for managing consent for children's personal data under GDPR Article 8 and COPPA.

Apache-2.0Auto-check passedLegal & Compliance

Install Managing Consent For Children

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-children -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills managing-consent-for-children --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/privacy/managing-consent-for-children .claude/skills/managing-consent-for-children && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
managing-consent-for-children
GitHub stars
301
Token cost
~2.5k tokens
SKILL.md length
948 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guide for managing consent for children's personal data under GDPR Article 8 and COPPA.

  • Works in 4 steps: Credit Card Verification: Parent… → Government ID Verification: Parent… → Video Call Verification: Live video call… → …
  • Tasks that involve Privacy and GDPR
  • SKILL.md covers Overview, Country-Specific Age…, Age Verification Methods and Parental Authorization Workflow, plus 2 more sections
  • Runs Python scripts from its folder

What it does

Managing Consent For Children is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for managing consent for children's personal data under GDPR Article 8 and COPPA. Covers parental consent mechanisms, age verification methods, country-specific age thresholds (ranging from 13 to 16), parental authorization workflows, and age-appropriate design per the UK ICO Children's Code.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/standards.md` and `references/workflows.md`).

It sits in Legal & Compliance, covering Privacy and GDPR. The repository describes itself as: 282+ structured privacy & data protection skills for AI agents. GDPR, CCPA, EU AI Act, HIPAA, LGPD, PIPL, DPDP Act. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Privacy and GDPR

Example prompts

  • “/managing-consent-for-children”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Credit Card Verification: Parent provides credit card details with a micro-transaction (refundable) to verify adult status. Used widely…
  2. Government ID Verification: Parent uploads government-issued ID (passport, national ID). Must comply with data minimization — ID should be…
  3. Video Call Verification: Live video call with parent presenting ID. Highest assurance but lowest scalability.
  4. Digital Identity Systems: eIDAS-compliant electronic identification (e.g., BankID in Nordic countries, SPID in Italy).

What it can do on your machine

Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file in scripts/ (Python), which the agent can run.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Managing Consent For Children loads about 2.5k tokens when it runs, and up to ~5.7k if it reads all its reference files. Until then it costs about 82 tokens; SKILL.md has 948 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~82
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 948 words, ~2,548 tokens.

Download SKILL.mdSave it as .claude/skills/managing-consent-for-children/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
managing-consent-for-children
description
Guide for managing consent for children's personal data under GDPR Article 8 and COPPA. Covers parental consent mechanisms, age verification methods, country-specific age thresholds (ranging from 13 to 16), parental authorization workflows, and age-appropriate design per the UK ICO Children's Code.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
consent-management
metadata.tags
children-consent, article-8, coppa, age-verification, parental-consent

Overview

GDPR Article 8 establishes special rules for processing children's personal data in the context of information society services offered directly to a child. Where processing is based on consent under Article 6(1)(a), the controller must make reasonable efforts to verify that consent is given or authorized by the holder of parental responsibility over the child. Member States may set the age threshold between 13 and 16 years.

In the United States, the Children's Online Privacy Protection Act (COPPA, 15 U.S.C. Section 6501-6506) requires verifiable parental consent before collecting personal information from children under 13.

Country-Specific Age Thresholds under GDPR Article 8(1)

Member States may provide by law for a lower age threshold, provided it is not below 13 years:

CountryAge ThresholdLegal Basis
Austria14Austrian Data Protection Act (DSG) Section 4(4)
Belgium13Law of 30 July 2018, Art. 7
Croatia16GDPR default (no national derogation)
Czech Republic15Act No. 110/2019, Section 7
Denmark13Danish Data Protection Act Section 12
Estonia13Personal Data Protection Act Section 8
Finland13Data Protection Act 1050/2018, Section 5
France15Law No. 2018-493 (Loi Informatique et Libertés), Art. 45
Germany16GDPR default (no national derogation)
Greece15Law 4624/2019, Art. 21
Hungary16GDPR default (no national derogation)
Ireland16Data Protection Act 2018, Section 31
Italy14Legislative Decree 101/2018, Art. 2-quinquies
Latvia13Personal Data Processing Law, Section 9
Lithuania14Law on Legal Protection of Personal Data, Art. 5
Luxembourg16GDPR default (no national derogation)
Netherlands16GDPR default (no national derogation)
Poland16GDPR default (no national derogation)
Portugal13Law 58/2019, Art. 16
Romania16GDPR default (no national derogation)
Slovakia16GDPR default (no national derogation)
Slovenia16GDPR default (no national derogation)
Spain14Organic Law 3/2018, Art. 7
Sweden13Data Protection Act (2018:218), Chapter 2 Section 4
United Kingdom13Data Protection Act 2018, Section 9 (UK GDPR retained)

Age Verification Methods

Article 8(2) requires "reasonable efforts" to verify parental consent, "taking into consideration available technology." The EDPB and national supervisory authorities have identified the following methods ranked by assurance level:

High Assurance Methods
  1. Credit Card Verification: Parent provides credit card details with a micro-transaction (refundable) to verify adult status. Used widely under COPPA in the US.
  2. Government ID Verification: Parent uploads government-issued ID (passport, national ID). Must comply with data minimization — ID should be verified and immediately deleted per EDPB guidance.
  3. Video Call Verification: Live video call with parent presenting ID. Highest assurance but lowest scalability.
  4. Digital Identity Systems: eIDAS-compliant electronic identification (e.g., BankID in Nordic countries, SPID in Italy).
Medium Assurance Methods
  1. Knowledge-Based Verification: Parent answers questions only an adult would know (e.g., financial questions from credit bureaus).
  2. Signed Consent Form: Parent downloads, signs, and uploads a consent form. Can be combined with electronic signatures (eIDAS Regulation).
  3. Email-Plus Verification: Email to parent followed by a secondary verification step (phone callback, reply with code).
Low Assurance Methods (May Not Be Sufficient Alone)
  1. Self-Declaration: User states their age via a date-of-birth input. Insufficient as the sole mechanism for high-risk processing, per CNIL guidance on age verification (June 2022).
  2. Checkbox Confirmation: "I am over [age] years old" checkbox. EDPB considers this inadequate for children's consent.
Show full SKILL.md (396 more words)Show less
CloudVault SaaS Inc. Implementation

CloudVault SaaS Inc. implements a tiered verification approach:

  • Tier 1 (Account Creation): Date-of-birth collection during registration. If age is below the applicable threshold for the user's country, the sign-up flow routes to the parental consent workflow.
  • Tier 2 (Parental Email Verification): An email is sent to the parent's email address with a unique verification link. The link expires after 48 hours.
  • Tier 3 (Credit Card Micro-Transaction): For processing activities classified as high-risk (profiling, data sharing), the parent must complete a $0.50 refundable credit card transaction to verify adult status.

Parental Authorization Workflow

START: Child enters date of birth during CloudVault SaaS Inc. sign-up
  │
  ├─► Calculate age based on date of birth
  │
  ├─► Determine applicable age threshold based on country
  │     (e.g., 16 for Ireland/Germany, 13 for UK/Denmark/Belgium)
  │
  ├─► IF age >= threshold:
  │     └─ Proceed with standard consent flow (child can consent independently)
  │
  └─► IF age < threshold:
        │
        ├─► Step 1: Inform child that parental consent is required
        │     "Because you're under [threshold] in [country], we need your
        │      parent or guardian's permission before you can use CloudVault."
        │
        ├─► Step 2: Collect parent/guardian email address
        │     ├─ Validate email format
        │     └─ Ensure parent email differs from child's email
        │
        ├─► Step 3: Send verification email to parent
        │     ├─ Subject: "CloudVault SaaS Inc. — Parental Consent Required"
        │     ├─ Body includes:
        │     │   ├─ What service the child wants to use
        │     │   ├─ What personal data will be collected
        │     │   ├─ Processing purposes (with per-purpose consent options)
        │     │   ├─ Data retention periods
        │     │   ├─ Child's rights under GDPR Article 8
        │     │   ├─ Parent's right to withdraw consent at any time
        │     │   └─ Link to consent form (expires in 48 hours)
        │     └─ Verification link contains: child_id, timestamp, HMAC signature
        │
        ├─► Step 4: Parent clicks verification link
        │     ├─ Display full consent form with per-purpose options
        │     ├─ For high-risk purposes: require credit card micro-transaction
        │     └─ Parent reviews and grants/denies consent per purpose
        │
        ├─► Step 5: Record parental consent
        │     ├─ Parent subject_id (derived from email verification)
        │     ├─ Child subject_id
        │     ├─ Relationship: "parent_guardian"
        │     ├─ Consent decisions per purpose
        │     ├─ Verification method used
        │     ├─ Timestamp, IP address, user agent
        │     └─ Consent text version hash
        │
        ├─► Step 6: Activate child's account
        │     ├─ Enable only purposes for which parental consent was granted
        │     └─ Apply age-appropriate default settings
        │
        └─► Step 7: Ongoing monitoring
              ├─ Age re-verification at appropriate intervals
              ├─ Parent can manage child's consent via parent dashboard
              └─ When child reaches age threshold, transition to self-consent

Age-Appropriate Design Considerations

The UK ICO Age Appropriate Design Code (Children's Code, effective September 2, 2021) establishes 15 standards for online services likely to be accessed by children:

  1. Best Interests of the Child: Processing must be in the child's best interest.
  2. Data Protection Impact Assessments: Required for services likely accessed by children.
  3. Age-Appropriate Application: Risk-assess and apply age-appropriate standards.
  4. Transparency: Provide privacy information in age-appropriate language.
  5. Detrimental Use: Do not use children's data in ways detrimental to their wellbeing.
  6. Default Settings: Settings must be "high privacy" by default.
  7. Data Minimization: Collect only the minimum data necessary.
  8. Data Sharing: Do not disclose children's data unless there is a compelling reason.
  9. Geolocation: Switch off geolocation by default.
  10. Parental Controls: If provided, give the child age-appropriate information about them.
  11. Profiling: Switch off profiling by default (unless there is a compelling reason).
  12. Nudge Techniques: Do not use nudge techniques to lead children to weaken privacy settings.
  13. Connected Toys and Devices: Apply all standards to connected devices/toys.
  14. Online Tools: Provide prominent accessible tools for children to exercise their rights.
  15. Policies and Community Standards: Uphold published policies and community standards.

Key Regulatory References

  • GDPR Article 8 — Conditions applicable to child's consent in relation to information society services
  • GDPR Article 8(1) — Age threshold (16 years, Member States may lower to 13)
  • GDPR Article 8(2) — Reasonable efforts to verify parental consent
  • COPPA (15 U.S.C. Section 6501-6506) — US children's privacy requirements
  • FTC COPPA Rule (16 CFR Part 312) — Implementing regulations for COPPA
  • UK ICO Age Appropriate Design Code — 15 standards for children's online services
  • CNIL Guidance on Age Verification (June 2022) — Methods and adequacy assessment
  • EDPB Guidelines 05/2020 on Consent — Section on children's consent
  • eIDAS Regulation (EU) No 910/2014 — Electronic identification for parental verification

© mukul975, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/managing-consent-for-children of mukul975/Privacy-Data-Protection-Skills.

  • SKILL.md
  • assets/template.md
  • references/standards.md
  • references/workflows.md
  • scripts/process.py

Open the folder on GitHubat commit 9b2ef9e

Compare with similar skills

Managing Consent For Children next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Managing Consent For Children compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Managing Consent For Children this skillmukul975/Privacy-Data-Protection-Skills301—~2.5kAutomated safety check: PassApache-2.0
C15tc15t/c15t1.9k1 repos~1.6kAutomated safety check: PassApache-2.0
HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed5.5k—~1.7kAutomated safety check: PassApache-2.0
Korean Privacy Termskimlawtech/korean-privacy-terms587—~2.9kAutomated safety check: PassApache-2.0
Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~3.9kAutomated safety check: PassMIT
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~2.3kAutomated safety check: PassMIT

Similar skills

  • C15t

    c15t/c15t

    Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.

    1.9k GitHub starsUsed in 1 repo~1.6k tokens
    Legal & ComplianceAuto-check passed
  • Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.

    5.5k GitHub stars~1.7k tokensUpdated today
    Legal & ComplianceAuto-check passed
  • Korean Privacy Terms

    kimlawtech/korean-privacy-terms

    처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.

    587 GitHub stars~2.9k tokensUpdated 1 mo ago
    Legal & ComplianceAuto-check passed
  • Gdpr Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert GDPR compliance assistant covering all four core workflows: (1) auditing code and systems for GDPR violations, (2) drafting GDPR-compliant documents such as privacy policies, Data Processing…

    946 GitHub starsUsed in 1 repo~3.9k tokens
    Legal & ComplianceAuto-check passed
  • Hipaa Compliance

    Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

    Expert HIPAA compliance assistant for healthcare and software contexts.

    946 GitHub starsUsed in 1 repo~2.3k tokens
    Legal & ComplianceAuto-check passed
  • Pii Contract Analyze

    gregmos/PII-Shield

    Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.

    150 GitHub stars~8.9k tokensUpdated 3 mo ago
    Legal & ComplianceAuto-check: notes

More from mukul975/Privacy-Data-Protection-Skills

All 280 skills in this repo
  • Age Gating Services

    mukul975/Privacy-Data-Protection-Skills

    Implements age-gating mechanisms for online services to restrict access based on user age.

    301 GitHub stars~3.7k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Data Retention

    mukul975/Privacy-Data-Protection-Skills

    Manages AI model retention and machine unlearning requirements.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • AI Dpia

    mukul975/Privacy-Data-Protection-Skills

    Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.

    301 GitHub stars~3.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Dpia Mitigation Plan

    mukul975/Privacy-Data-Protection-Skills

    Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).

    301 GitHub stars~846 tokensUpdated 6 mo ago
    Auto-check passed
  • Gdpr Accountability

    mukul975/Privacy-Data-Protection-Skills

    Guides implementation of the GDPR accountability principle under Articles 5(2) and 24, including documentation requirements for policies, DPIAs, RoPA, training records, and breach logs.

    301 GitHub stars~1.9k tokensUpdated 6 mo ago
    Auto-check passed
  • Pia Threshold Screening

    mukul975/Privacy-Data-Protection-Skills

    Conducts pre-DPIA threshold screening to determine whether a full Data Protection Impact Assessment is required under GDPR Article 35.

    301 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed

Questions about Managing Consent For Children

What does Managing Consent For Children do?

Guide for managing consent for children's personal data under GDPR Article 8 and COPPA. Managing Consent For Children is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guide for managing consent for children's personal data under GDPR Article 8 and COPPA.

When should I use Managing Consent For Children?

Managing Consent For Children fits situations like: tasks that involve Privacy and GDPR.

How do I install Managing Consent For Children in Claude Code?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-children -a claude-code`. Or copy the skill folder (skills/privacy/managing-consent-for-children in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/managing-consent-for-children in your project. Claude Code loads it when a task matches its description.

How do I install Managing Consent For Children in Codex?

Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-children -a codex`. Or copy the skill folder (skills/privacy/managing-consent-for-children in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/managing-consent-for-children in your project. Codex loads it when a task matches its description.

Can I use Managing Consent For Children in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill managing-consent-for-children -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/managing-consent-for-children, .gemini/skills/managing-consent-for-children, .github/skills/managing-consent-for-children and .opencode/skills/managing-consent-for-children in your project.

What does Managing Consent For Children need to run?

Going by SKILL.md and its folder, Managing Consent For Children needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Managing Consent For Children access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Managing Consent For Children safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Managing Consent For Children use?

Managing Consent For Children is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Managing Consent For Children use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.1k tokens, read only when the agent opens those files.

What are the alternatives to Managing Consent For Children?

Skills that share tags, products or a category with Managing Consent For Children: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Managing Consent For Children?

mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 301 GitHub stars. The repository holds 280 skills in this directory. The repository was last updated on March 16, 2026.

Source: mukul975/Privacy-Data-Protection-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.