Agent skill

Age Verification Methods

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

Evaluates and implements age estimation and verification technologies for online services.

Apache-2.0Auto-check passedLegal & Compliance

Install Age Verification Methods

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill age-verification-methods -a claude-code

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

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills age-verification-methods --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/age-verification-methods .claude/skills/age-verification-methods && 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
age-verification-methods
GitHub stars
295
Token cost
~4.4k tokens
SKILL.md length
2,207 words
Files
5 (incl. scripts, references, assets)
Skills in repo
278
Repo updated
First seen
Licence
Apache-2.0

At a glance

Evaluates and implements age estimation and verification technologies for online services.

  • Works in 3 steps: Classify Service Risk Level → Select Minimum Verification Level → Apply Proportionality Test
  • Tasks that involve Privacy and GDPR
  • SKILL.md covers Overview, Regulatory Context, Age Verification Methods and Accuracy vs. Privacy Tradeoff…, plus 4 more sections
  • Runs Python scripts from its folder

What it does

Age Verification Methods is an agent skill from mukul975/Privacy-Data-Protection-Skills. Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.

Its SKILL.md is about 4.4k 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

  • “Use the age-verification-methods skill to evaluate and implements age estimation and verification technologies for online services”
  • “/age-verification-methods”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Classify Service Risk Level
  2. Select Minimum Verification Level
  3. Apply Proportionality Test

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

Age Verification Methods loads about 4.4k tokens when it runs, and up to ~8.5k if it reads all its reference files. Until then it costs about 105 tokens; SKILL.md has 2,207 words of instructions outside code blocks.

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

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). 2,207 words, ~4,363 tokens.

Download SKILL.mdSave it as .claude/skills/age-verification-methods/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
age-verification-methods
description
Evaluates and implements age estimation and verification technologies for online services. Covers facial age estimation, digital ID verification, self-declaration with risk assessment, AI-based age estimation, and the accuracy versus privacy tradeoff. Includes ICO guidance and euCONSENT framework. Keywords: age verification, age estimation, facial analysis, digital ID, children, online safety.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
children-data-protection
metadata.tags
age-verification, age-estimation, facial-analysis, digital-id, children, online-safety

Age Verification and Estimation Methods

Overview

Age verification and age estimation are distinct but complementary approaches to determining whether a user is a child for the purpose of applying appropriate data protection safeguards. Age verification provides a definitive confirmation of age through documentary or transactional evidence. Age estimation provides a probabilistic assessment of age using technological methods such as facial analysis, behavioural analysis, or device signals. The selection of an appropriate method requires balancing accuracy, privacy impact, accessibility, and proportionality. This skill covers the full spectrum of available methods, their regulatory context under the GDPR, UK AADC, COPPA, and emerging legislation such as the EU Digital Services Act (DSA) and the UK Online Safety Act 2023, and provides implementation guidance based on ICO and CNIL recommendations.

Regulatory Context

GDPR Article 8(2)

"The controller shall make reasonable efforts to verify in such cases that consent is given or authorised by the holder of parental responsibility over the child, taking into consideration available technology."

The "reasonable efforts" standard is context-dependent. The EDPB has not prescribed specific technologies but expects controllers to adopt verification proportionate to the risk of the processing.

UK AADC Standard 3 — Age-Appropriate Application

"Take a risk-based approach to recognising the age of individual users and ensure you effectively apply the standards in this code to child users." The ICO guidance states that the level of certainty required depends on the risks to children from the processing. Higher risks demand more robust age assurance methods.

UK Online Safety Act 2023

Section 11(3) requires providers of regulated user-to-user services and search services to use "proportionate systems or processes" designed to prevent children from encountering primary priority content that is harmful to children. Ofcom's codes of practice specify age verification as a recommended measure for pornographic content and age estimation for broader content categories.

EU Digital Services Act — Article 28

Providers of online platforms accessible to minors must put in place appropriate and proportionate measures to ensure a high level of privacy, safety, and security of minors on their service. This includes age verification for services with content restrictions.

France — Loi SREN (2024)

France's law to regulate and secure the digital space requires age verification for access to pornographic websites, mandating technical solutions certified by CNIL that verify age without identifying the user. The CNIL-approved reference system requires a "double-blind" architecture where the identity verification provider and the content provider cannot link the user's identity to the content access.

Age Verification Methods

Method 1: Document-Based Verification

Description: User uploads or presents a government-issued identity document (passport, national ID card, driver's licence) which is verified against document security features and optionally against government databases.

Technical Implementation:

  • Optical Character Recognition (OCR) extracts date of birth and document details
  • Machine Readable Zone (MRZ) validation for passports and ID cards conforming to ICAO Doc 9303
  • Document authenticity checks: hologram detection, microprint analysis, UV feature verification (for physical presentation)
  • Optional: NFC chip reading for ePassports conforming to ICAO 9303 Part 10
  • Optional: Liveness check to confirm the person presenting the document matches the photo

Accuracy: Very high (99%+ when combined with liveness detection)

Privacy Considerations:

  • Collects highly sensitive identity data (ID number, full name, address, photo)
  • Data minimisation: extract only date of birth, discard full document image immediately after verification
  • Storage: do not retain the document image or full identity data; retain only a binary age-confirmed flag and a verification token
  • DPIA required under Art. 35 due to large-scale processing of identity documents

Accessibility: Excludes individuals without government-issued ID (estimated 1.5 million UK adults lack photo ID per Electoral Commission 2021 data). Not appropriate as the sole method.

Use Cases: Age-restricted content (gambling, alcohol, adult content), high-risk services

Method 2: Facial Age Estimation (AI-Based)

Description: Machine learning models estimate a user's age from a facial image captured by the device camera. The estimation provides an age range (e.g., "over 18" or "13-17") rather than a precise age.

Technical Implementation:

  • Convolutional Neural Network (CNN) trained on large-scale age-labelled facial datasets
  • Real-time processing on-device (edge computing) to avoid transmitting facial images to servers
  • Liveness detection to prevent spoofing via photographs or video replay
  • Age estimation outputs a confidence interval (e.g., estimated age 14 +/- 2 years with 95% confidence)
  • The facial image is processed in volatile memory and not stored

Accuracy: Mean Absolute Error (MAE) of 1.5-3 years depending on the model and demographic. Accuracy varies by: age group (lower accuracy for children under 8 and adults over 65), ethnicity (documented bias in some commercial systems), lighting and image quality.

Privacy Considerations:

  • Facial images constitute biometric data under GDPR Art. 4(14) and Art. 9(1) if used for unique identification
  • When used solely for age estimation (not identification), the processing may not constitute "biometric data for the purpose of uniquely identifying" under Art. 9 — the ICO has confirmed this interpretation in its Children's Code guidance
  • On-device processing with no server transmission significantly reduces privacy risk
  • DPIA is recommended even when processing is on-device due to sensitivity of facial data

Key Providers: Yoti (Age Estimation), VerifyMyAge (EstimateMyAge), Privately SA

ICO Position: The ICO has stated that facial age estimation technology that processes images locally, does not store images, and does not identify the individual can be a proportionate method for age assurance. The ICO conducted a joint audit with the Australian Information Commissioner (OAIC) of Yoti's age estimation technology in 2022 and concluded it met data protection requirements when implemented with appropriate safeguards.

Method 3: Digital Identity Verification

Description: User authenticates through a trusted digital identity provider (eID, digital wallet, Open Banking) that confirms age without disclosing full identity to the relying party (service provider).

Technical Implementation:

  • OpenID Connect for Identity Assurance (OIDC4IDA) protocol for attribute-based verification
  • The identity provider confirms a specific attribute (e.g., "is_over_18": true) via a signed assertion
  • The relying party receives only the age attribute, not the user's name, address, or other identity data
  • EU Digital Identity Wallet (eIDAS 2.0 Regulation, expected 2026 rollout) will enable selective attribute disclosure
  • UK Digital Identity and Attributes Trust Framework (DIATF) provides a certification scheme for identity providers

Accuracy: Very high (dependent on the identity provider's verification of the underlying identity)

Privacy Considerations:

  • Minimal data disclosure: only the specific age attribute is shared
  • The identity provider knows the user's identity but not which service they are accessing (if double-blind architecture is used)
  • The service provider knows the user is accessing their service but not their full identity
  • Aligns with CNIL's recommended "double-blind" approach for age verification

Use Cases: EU/EEA services preparing for eIDAS 2.0 Digital Identity Wallet; UK services using DIATF-certified providers

Method 4: Self-Declaration with Risk Mitigation

Description: User declares their age through a date-of-birth field or age-range selector. The declaration is treated as the baseline, supplemented by risk-based measures to detect false declarations.

Technical Implementation:

  • Neutral age prompt: "What is your date of birth?" with a scrollable date picker (no calendar default to current date)
  • No indication of the "correct" answer or the age threshold being applied
  • Behavioural signals that may indicate false declaration: immediate re-entry with a different date, cookie evidence of prior declaration, typing speed patterns inconsistent with the declared age
  • If false declaration is suspected, escalate to a higher-assurance verification method

Accuracy: Low as a standalone method. Children commonly misrepresent their age online. Ofcom's 2023 research found that 33% of UK 8-17 year olds have a social media profile despite being below the platform's minimum age.

Privacy Considerations: Minimal data collection (only declared date of birth). No biometric processing. No identity document collection.

Use Cases: Low-risk services as a first-line screening measure, always combined with additional safeguards for medium and high-risk services

Show full SKILL.md (942 more words)Show less
Method 5: Credit Card or Payment Verification

Description: User's age is inferred from possession of a credit card (typically issued only to adults 18+) through a monetary transaction.

Technical Implementation:

  • Micro-transaction (USD/EUR/GBP 0.50) charged and refunded within 48 hours
  • The card must be a credit card (not a debit card or prepaid card, which may be issued to minors)
  • Transaction notification sent to the cardholder provides an audit trail
  • Some implementations use 3D Secure (3DS2) authentication for additional identity assurance

Accuracy: Moderate. Establishes that the person has access to a credit card, which correlates with being over 18. Does not verify the specific age of the cardholder. Children may use a parent's card.

Privacy Considerations: Payment card data is subject to PCI DSS requirements. The service should not store full card details. Only the transaction confirmation and a binary "has credit card" flag should be retained.

Method 6: Mobile Network Operator (MNO) Verification

Description: The mobile network operator confirms the user's age bracket based on the subscriber information associated with the SIM/eSIM, without disclosing the user's identity to the requesting service.

Technical Implementation:

  • API call to MNO (via aggregator such as GBG, boku, or Sinch) with the user's mobile number
  • MNO returns a binary response (e.g., "is_over_18": true/false) without disclosing identity
  • Relies on the age data the MNO collected during subscriber registration (ID check at point of sale)

Accuracy: High for determining over/under 18, since MNO registration typically involves ID verification. Lower certainty for granular age (e.g., distinguishing 13 from 15) as MNOs may not record precise birth dates.

Privacy Considerations: The service learns only the age bracket. The MNO learns which service the user is accessing (unless intermediary architecture prevents this). DPIA recommended for the MNO's processing.

Accuracy vs. Privacy Tradeoff Matrix

MethodAccuracyPrivacy ImpactProportionate For
Document-BasedVery HighVery High (ID collection)Age-restricted products (gambling, alcohol)
Facial Age EstimationHigh (MAE 1.5-3y)Medium (on-device) to High (server-side)General online services, social media
Digital IdentityVery HighLow (attribute-only disclosure)Any service; best privacy-accuracy balance
Self-DeclarationLowVery LowInitial screening; low-risk services only
Credit CardModerateMedium (payment data)Supplementary verification for parental consent
MNO VerificationHighLow-MediumMobile-first services; supplementary check

Risk-Based Selection Framework

Step 1: Classify Service Risk Level
Risk LevelCriteriaExamples
HighDirect messaging with strangers, user-generated content visible to strangers, age-restricted content, monetisation features targeting childrenSocial media, dating apps, gambling, online marketplaces
MediumContent personalisation, in-app purchases, community features with moderation, educational services with profilingEdTech platforms, gaming, streaming services
LowStatic content delivery, no social features, no data sharing, no profilingInformational websites, single-player offline games
Step 2: Select Minimum Verification Level
Risk LevelMinimum VerificationRecommended Approach
HighDocument-Based OR Facial Estimation + LivenessDocument-based with digital identity as alternative
MediumFacial Age Estimation (on-device) OR Self-Declaration + Risk SignalsFacial age estimation with escalation path
LowSelf-Declaration + Neutral PromptSelf-declaration with cookie-based re-entry detection
Step 3: Apply Proportionality Test

For each selected method, document:

  1. Why is this method necessary to protect children?
  2. Could a less intrusive method achieve the same level of protection?
  3. What safeguards minimise the privacy impact of the method (data minimisation, on-device processing, immediate deletion)?
  4. How does this method account for accessibility (users without ID, users with disabilities)?

BrightPath Learning Inc. — Age Verification Implementation

BrightPath Learning Inc. operates an educational platform classified as Medium risk (educational content with progress tracking and personalisation, no social features with strangers).

Implemented Approach: Layered Verification

  1. Layer 1 — Self-Declaration: During registration, a neutral date-of-birth prompt with scrollable date picker. Determines initial routing (child vs. adult account).
  2. Layer 2 — Parental Account: For users declaring an age below the applicable threshold, the parental consent flow is triggered. The parent creates an account and verifies via credit card micro-transaction.
  3. Layer 3 — Anomaly Detection: Behavioural signals monitored for inconsistencies: IP address mismatch between child and parent accounts, identical email domains suggesting self-verification, multiple child accounts from the same parent in short succession.
  4. Layer 4 — Escalation: If anomalies are detected, the parent is asked to complete a video verification call or upload a government-issued ID (with immediate deletion after verification).

Data Retention for Age Verification:

  • Self-declared date of birth: retained for account lifecycle
  • Credit card transaction record: retained for 90 days (reconciliation), then deleted; only "parent verified" flag retained
  • Government ID image: processed in memory, not stored; verification outcome retained
  • Facial images: not collected (BrightPath does not use facial age estimation)

Emerging Standards and Legislation

IEEE 2089.1-2024 — Age-Appropriate Digital Services Framework

Published standard providing a framework for implementing age-appropriate design in digital services, including guidance on age assurance methods and their application across different risk contexts.

ISO/IEC 27566 — Age Assurance Systems (Under Development)

Working draft standard for age assurance systems covering both age verification and age estimation. Addresses accuracy, privacy, accessibility, interoperability, and governance requirements.

EU Digital Identity Wallet (eIDAS 2.0)

The revised eIDAS Regulation mandates that EU Member States offer digital identity wallets to citizens by 2026. The wallet will support selective attribute disclosure, enabling users to prove they are over a specific age without revealing their full identity or date of birth. This will become the preferred age verification method for EU services.

Integration Points

  • GDPR Parental Consent: Age verification is a prerequisite for determining whether parental consent is required under Art. 8
  • UK AADC Implementation: AADC Standard 3 requires risk-proportionate age assurance
  • Age-Gating Services: Age verification results drive the age-gating decision (admit, redirect, or block)
  • COPPA Compliance: COPPA requires age screening as part of the parental consent flow
  • Children's Privacy Notice: The age verification result determines which version of the privacy notice to display (child-friendly vs. standard)

© 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/age-verification-methods 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

Age Verification Methods 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.

Age Verification Methods compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Age Verification Methods this skillmukul975/Privacy-Data-Protection-Skills295—~4.4kAutomated 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-terms586—~2.9kAutomated safety check: PassApache-2.0
Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9421 repos~3.9kAutomated safety check: PassMIT
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9421 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.

    586 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…

    942 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.

    942 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.

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

More from mukul975/Privacy-Data-Protection-Skills

All 278 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.

    295 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.

    295 GitHub stars~1.9k 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).

    295 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.

    295 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.

    295 GitHub stars~880 tokensUpdated 6 mo ago
    Auto-check passed
  • Retention Schedule

    mukul975/Privacy-Data-Protection-Skills

    Designs and implements data retention schedules compliant with GDPR Article 5(1)(e) storage limitation principle.

    295 GitHub stars~3.3k tokensUpdated 6 mo ago
    Auto-check passed

Questions about Age Verification Methods

What does Age Verification Methods do?

Evaluates and implements age estimation and verification technologies for online services. Age Verification Methods is an agent skill from mukul975/Privacy-Data-Protection-Skills. Evaluates and implements age estimation and verification technologies for online services.

When should I use Age Verification Methods?

Age Verification Methods fits situations like: tasks that involve Privacy and GDPR.

How do I install Age Verification Methods in Claude Code?

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

How do I install Age Verification Methods in Codex?

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

Can I use Age Verification Methods 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 age-verification-methods -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/age-verification-methods, .gemini/skills/age-verification-methods, .github/skills/age-verification-methods and .opencode/skills/age-verification-methods in your project.

What does Age Verification Methods need to run?

Going by SKILL.md and its folder, Age Verification Methods needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Age Verification Methods 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 Age Verification Methods 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 Age Verification Methods use?

Age Verification Methods 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 Age Verification Methods use?

About 4.4k tokens (SKILL.md is roughly 17k 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 4.1k tokens, read only when the agent opens those files.

What are the alternatives to Age Verification Methods?

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

Who maintains Age Verification Methods?

mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 295 GitHub stars. The repository holds 278 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.