Agent skill

Employee Biometric Data

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

Governs biometric data processing for employee timekeeping and access control under Art.

Apache-2.0Auto-check passedLegal & Compliance

Install Employee Biometric Data

skills CLI
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill employee-biometric-data -a claude-code

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

GitHub CLI
$ gh skill install mukul975/Privacy-Data-Protection-Skills employee-biometric-data --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/employee-biometric-data .claude/skills/employee-biometric-data && 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
employee-biometric-data
GitHub stars
301
Token cost
~4k tokens
SKILL.md length
1,862 words
Files
5 (incl. scripts, references, assets)
Skills in repo
280
Repo updated
First seen
Licence
Apache-2.0

At a glance

Governs biometric data processing for employee timekeeping and access control under Art.

  • Works in 3 steps: Define the Specific Purpose → Evaluate Less Intrusive Alternatives → Proportionality Assessment
  • Tasks that involve Privacy and GDPR
  • SKILL.md covers Overview, Legal Framework, Biometric Technologies in… and Necessity Test Framework, plus 4 more sections
  • Runs Python scripts from its folder

What it does

Employee Biometric Data is an agent skill from mukul975/Privacy-Data-Protection-Skills. Governs biometric data processing for employee timekeeping and access control under Art. 9 GDPR special category rules. Covers fingerprint, facial recognition, iris scanning, and voice recognition. Applies necessity tests, evaluates less intrusive alternatives, and implements employee objection procedures. Keywords: biometric data, Art. 9, fingerprint, facial recognition, access control, timekeeping, special category.

Its SKILL.md is about 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 and Authorization and RBAC. 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
  • Tasks that involve Authorization and RBAC

Example prompts

  • “Use the employee-biometric-data skill to govern biometric data processing for employee timekeeping and access control under Art”
  • “/employee-biometric-data”

Requirements

  • Python 3

Workflow steps

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

  1. Define the Specific Purpose
  2. Evaluate Less Intrusive Alternatives
  3. Proportionality Assessment

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

Employee Biometric Data loads about 4k tokens when it runs, and up to ~6.2k if it reads all its reference files. Until then it costs about 111 tokens; SKILL.md has 1,862 words of instructions outside code blocks.

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

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). 1,862 words, ~4,027 tokens.

Download SKILL.mdSave it as .claude/skills/employee-biometric-data/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
employee-biometric-data
description
Governs biometric data processing for employee timekeeping and access control under Art. 9 GDPR special category rules. Covers fingerprint, facial recognition, iris scanning, and voice recognition. Applies necessity tests, evaluates less intrusive alternatives, and implements employee objection procedures. Keywords: biometric data, Art. 9, fingerprint, facial recognition, access control, timekeeping, special category.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
employee-data-privacy
metadata.tags
biometric-data, article-9, fingerprint, facial-recognition, access-control, special-category

Employee Biometric Data

Overview

Biometric data is classified as a special category of personal data under Art. 9(1) GDPR when processed for the purpose of uniquely identifying a natural person. Processing biometric data for employee timekeeping and access control is one of the most frequently scrutinised activities by European supervisory authorities. The general prohibition on processing special category data under Art. 9(1) means that employers must identify a specific exception under Art. 9(2), satisfy the proportionality requirement, demonstrate that no less intrusive alternative exists, and implement robust safeguards. National DPAs have issued substantial fines for biometric processing that fails these tests, including the landmark Clearview AI enforcement actions and sector-specific decisions on workplace fingerprint systems.

Art. 4(14) — Definition of Biometric Data

"Biometric data means personal data resulting from specific technical processing relating to the physical, physiological or behavioural characteristics of a natural person, which allow or confirm the unique identification of that natural person, such as facial images or dactyloscopic data."

Art. 9(1) — General Prohibition

"Processing of [...] biometric data for the purpose of uniquely identifying a natural person [...] shall be prohibited."

Critical distinction: Biometric data processed for purposes other than unique identification may not be classified as special category data under Art. 9(1). However, in the employment context, biometric processing for timekeeping and access control is almost always for identification purposes.

Art. 9(2) — Exceptions Applicable to Employment
ExceptionArticleApplicability to Employment Biometrics
Explicit consentArt. 9(2)(a)Rarely valid due to employment power imbalance (see employment-consent-limits skill)
Employment law obligationArt. 9(2)(b)Valid where national law specifically mandates or authorises biometric processing for employment purposes
Substantial public interestArt. 9(2)(g)Valid where national law establishes biometric access control requirements for critical infrastructure
Not applicableArt. 9(2)(e)Data "manifestly made public" — employees do not manifestly make their biometric data public
Key National Derogations

France — Art. L.1121-1 Labour Code + CNIL Framework:

  • CNIL published dedicated guidance: "Règlement type biométrie" (Deliberation No. 2019-001, 10 January 2019)
  • Biometric access control is permitted for access to premises, devices, and applications where justified by the context
  • Storage preference hierarchy: (1) individual device held by employee (badge), (2) centralised database with employee control, (3) centralised database without employee control (requires strongest justification)
  • The employee must be informed and provided an alternative non-biometric access method

Germany — Section 26(3) BDSG:

  • Processing of special category data including biometrics is permitted for employment purposes where necessary for the exercise of rights or obligations under employment law, social security law, or social protection law
  • Works council co-determination rights under Section 87(1)(6) BetrVG apply

Netherlands — UAVG Art. 29:

  • Biometric processing is permitted for authentication or security purposes where necessary
  • The Dutch DPA (Autoriteit Persoonsgegevens) has issued specific guidance restricting biometric processing to high-security contexts

Italy — Workers' Statute Art. 4 + Garante Guidance:

  • Biometric access control requires trade union agreement or labour inspectorate authorisation
  • The Garante has issued multiple decisions restricting biometric timekeeping to specific sectors

Sweden — Datainspektionen Decisions:

  • The Swedish DPA fined a school SEK 200,000 for using facial recognition for attendance monitoring (DI-2019-2221), setting a strong precedent that biometric monitoring for attendance is disproportionate when simpler alternatives exist

Biometric Technologies in Employment

Fingerprint Recognition

Use cases: Timekeeping (clocking in/out), physical access control, device authentication.

Technical processing: Fingerprint scanner captures an image of friction ridges → image is processed to extract minutiae points → minutiae template is compared against stored templates → match/no-match result.

Privacy considerations:

  • Template storage: Store templates on individual smart cards held by the employee (less intrusive) rather than in a centralised database (more intrusive)
  • Revocability: Unlike passwords, fingerprints cannot be changed if compromised
  • False acceptance rate (FAR) and false rejection rate (FRR) must be documented
  • Employees with skin conditions, injuries, or disabilities affecting fingerprints must have an alternative access method

Atlas Manufacturing Group Example: Atlas installed fingerprint scanners for access to its R&D laboratory where proprietary formulations are developed. The DPO approved the deployment based on Art. 9(2)(b) (German BDSG Section 26(3)) for the R&D laboratory only, with the following conditions: (1) fingerprint templates stored on employee ID badges, not in a central database, (2) alternative PIN access available for employees who object or have medical conditions, (3) DPIA completed before deployment, (4) works council consulted and agreement obtained.

Facial Recognition

Use cases: Contactless access control, time and attendance, security zones.

Technical processing: Camera captures facial image → facial geometry is measured (distance between eyes, nose shape, jawline contour) → geometry data converted to mathematical template → template compared against enrolled images.

Privacy considerations:

  • Facial recognition is significantly more intrusive than fingerprint scanning because it can operate without the employee's active cooperation or awareness (passive vs. active biometric)
  • Continuous facial recognition in the workplace may constitute systematic monitoring, triggering additional DPIA requirements
  • Risk of function creep: facial recognition deployed for access may be expanded to emotion detection, attention monitoring, or behavioural analysis
  • Bias and accuracy: Facial recognition systems have documented higher error rates for certain demographic groups, creating discrimination risk

Supervisory Authority Position: Most European DPAs take the position that facial recognition for general time and attendance purposes is disproportionate when simpler alternatives (badge, PIN, fingerprint) are available. Facial recognition may be justified only for high-security access control where contactless verification is necessary (cleanroom environments, nuclear facilities).

Iris Scanning

Use cases: High-security access control, authentication in environments where hand-based biometrics are impractical (e.g., clean environments requiring gloves).

Privacy considerations:

  • Among the most accurate biometric modalities (FAR below 0.0001%)
  • Less affected by environmental factors than fingerprint
  • Generally limited to high-security contexts where the heightened intrusion is justified
Voice Recognition

Use cases: Telephone-based authentication, call centre agent verification, voice-activated systems.

Privacy considerations:

  • Voice data may reveal health information (fatigue, intoxication, emotional state), potentially creating additional Art. 9 issues
  • Voice templates are more susceptible to spoofing than other biometric modalities
  • Ambient noise and voice changes (illness, ageing) affect accuracy
Behavioural Biometrics

Use cases: Keystroke dynamics, gait analysis, mouse movement patterns.

Privacy considerations:

  • Often collected passively without explicit employee action
  • May reveal health conditions (tremor, cognitive impairment)
  • The EDPB has not yet issued specific guidance on behavioural biometrics in employment, but existing principles on proportionality and transparency apply

Necessity Test Framework

Before deploying any biometric system, the employer must demonstrate that the biometric processing is genuinely necessary and that no less intrusive alternative would achieve the same purpose.

Step 1: Define the Specific Purpose

The purpose must be concrete, documented, and limited:

  • "Controlling access to the R&D laboratory containing proprietary formulations" — acceptable
  • "Improving workforce management" — too vague
  • "Ensuring accurate time and attendance records" — biometric processing is unlikely to be necessary for this purpose
Show full SKILL.md (778 more words)Show less
Step 2: Evaluate Less Intrusive Alternatives
PurposeBiometric SolutionLess Intrusive AlternativeNecessity of Biometrics
Physical access to high-security areaFingerprint scannerSmart card + PINBiometric may be justified if tailgating/card sharing is a documented security concern
General building accessFacial recognitionBadge/proximity cardBiometric is disproportionate; badge provides equivalent security
Time and attendanceFingerprint clockBadge, PIN code, supervisor sign-offBiometric is disproportionate; buddy punching can be addressed through supervision
Device authenticationFingerprint/face unlockPassword, smart cardBiometric may be justified for high-sensitivity devices where password risk is documented
Cleanroom accessIris scanBadge + airlockBiometric may be justified where contactless identification is operationally necessary
Step 3: Proportionality Assessment

Even if biometric processing passes the necessity test, it must also be proportionate:

  • Is the security risk significant enough to justify processing special category data?
  • Is the biometric system targeted (limited to specific areas/roles) or blanket (all employees)?
  • Are adequate safeguards in place (template storage, retention, access controls)?
  • Is an alternative non-biometric method available for employees who object?

Employee Objection Procedures

Regardless of the lawful basis, employers must provide a meaningful objection mechanism:

Objection Process
  1. Information at enrolment: When employees are asked to enrol biometric data, they must be informed of:

    • The specific purpose of biometric processing
    • The lawful basis (Art. 9(2) condition and Art. 6(1) basis)
    • The availability of an alternative non-biometric method
    • Their right to object or withdraw (where consent is the basis)
    • Data retention period and deletion procedures
  2. Alternative access method: A non-biometric alternative must be available at all times:

    • PIN code + proximity badge for access control
    • Manual sign-in sheet or supervisor confirmation for timekeeping
    • Password or smart card for device authentication
  3. No adverse consequences: Employees who use the alternative method must not suffer any disadvantage:

    • No additional time required to use the alternative
    • No flagging in attendance systems
    • No negative note in personnel records
  4. Formal objection handling: Objections must be:

    • Recorded in the privacy management system
    • Acknowledged within 5 working days
    • Actioned immediately (switch to alternative method)
    • Reviewed by the DPO
Special Circumstances
  • Disability: Employees with conditions affecting biometric characteristics (skin conditions, prosthetics, facial differences) must be provided accessible alternatives without requirement to disclose their condition
  • Religious objections: Some employees may object to biometric collection on religious grounds; the alternative must accommodate this
  • Trade union representatives: Works council members may object on behalf of represented employees under national co-determination rights

Data Protection Safeguards

Template Storage Hierarchy (per CNIL Règlement Type Biométrie)
Storage MethodRisk LevelWhen Appropriate
Individual device (badge, token) held by employeeLowestDefault preferred method for all biometric deployments
Centralised database with employee-controlled access keyMediumWhere individual device storage is technically infeasible
Centralised database without employee controlHighestOnly for specific, documented security requirements with strongest justification
Technical Safeguards
  • Biometric templates must be encrypted at rest (AES-256 minimum) and in transit (TLS 1.3)
  • Raw biometric data (fingerprint images, facial photographs) must not be stored; only derived templates should be retained
  • Template format must be system-specific to prevent cross-system matching
  • Anti-spoofing measures (liveness detection) must be implemented
  • Biometric systems must be isolated from general IT networks
  • Access to biometric databases must be restricted to authorised security personnel with multi-factor authentication
  • Audit logs of all biometric system access must be maintained
Retention and Deletion
  • Biometric templates must be deleted immediately upon termination of employment
  • Biometric templates must be deleted immediately upon employee objection or consent withdrawal
  • Biometric templates must be deleted when the processing purpose ceases (e.g., employee transfers to a role that does not require access to the secured area)
  • Deletion must be verified and documented with certificates of destruction

Enforcement Precedents

AuthorityCaseFine/OutcomeKey Issue
Datainspektionen (Sweden)DI-2019-2221SEK 200,000School used facial recognition for student attendance — disproportionate, simpler alternatives available
CNIL (France)Clearview AI, 2022EUR 20,000,000Biometric processing (facial recognition) without lawful basis or DPIA
AEPD (Spain)PS/00218/2021EUR 20,000Employer required fingerprint for timekeeping without necessity assessment or alternative method
Garante (Italy)Provvedimento 9832838, 2021Processing prohibitedEmployer deployed facial recognition for access control without necessity analysis or Art. 9(2) condition
Autoriteit Persoonsgegevens (NL)2020 InvestigationWarning + cease orderEmployer used fingerprint timekeeping; AP found it disproportionate for attendance purposes
ICO (UK)Enforcement notice, 2022Processing ordered to ceaseEmployer deployed palm vein scanning for general access without DPIA

Integration Points

  • Employee Monitoring DPIA: Biometric systems must undergo DPIA (see employee-monitoring-dpia skill).
  • Employment Consent Limits: Consent for biometric processing is constrained by employment power imbalance (see employment-consent-limits skill).
  • HR System Privacy Config: Biometric integration with HR/timekeeping systems requires privacy configuration (see hr-system-privacy-config skill).
  • Background Check Privacy: Biometric data collected for access control must be separated from background check data (see background-check-privacy skill).

© 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/employee-biometric-data 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

Employee Biometric Data 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.

Employee Biometric Data compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Employee Biometric Data this skillmukul975/Privacy-Data-Protection-Skills301—~4kAutomated safety check: PassApache-2.0
Cis ControlsSushegaad/Claude-Skills-Governance-Risk-and-Compliance9461 repos~4.2kAutomated safety check: PassMIT
Tos Clause Scannerzebbern/claude-code-guide4.7k1 repos~3.3kAutomated safety check: PassMIT
Healthcare Phi Complianceaffaan-m/ECC276k1 repos~1.4kAutomated safety check: PassMIT
Policy OpaAgentSecOps/SecOpsAgentKit2201 repos~3.5kAutomated safety check: PassCustom licence
Fondo Security Basicsjeremylongshore/tons-of-skills-marketplace2.8k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Cis Controls

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

    Expert CIS Controls v8 (CIS Top 18) advisor — implementation group scoping (IG1/IG2/IG3), control gap assessments, safeguard-level guidance, asset inventory, software inventory, data protection…

    946 GitHub starsUsed in 1 repo~4.2k tokens
    Legal & ComplianceAuto-check passed
  • Tos Clause Scanner

    zebbern/claude-code-guide

    Audit Terms of Service, user agreements, and privacy policies for consumer risks, producing a structured report that flags unfair clauses, data traps, and liability issues.

    4.7k GitHub starsUsed in 1 repo~3.3k tokens
    Legal & ComplianceAuto-check passed
  • Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak…

    276k GitHub starsUsed in 1 repo~1.4k tokens
    Legal & ComplianceAuto-check passed
  • Policy Opa

    AgentSecOps/SecOpsAgentKit

    Policy-as-code enforcement and compliance validation using Open Policy Agent (OPA).

    220 GitHub starsUsed in 1 repo~3.5k tokens
    Legal & ComplianceAuto-check passed
  • Fondo Security Basics

    jeremylongshore/tons-of-skills-marketplace

    Apply security best practices for Fondo including OAuth token management, financial data protection, SOC 2 compliance, and access control.

    2.8k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check passed
  • 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

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 Employee Biometric Data

What does Employee Biometric Data do?

Governs biometric data processing for employee timekeeping and access control under Art. Employee Biometric Data is an agent skill from mukul975/Privacy-Data-Protection-Skills. Governs biometric data processing for employee timekeeping and access control under Art.

When should I use Employee Biometric Data?

Employee Biometric Data fits situations like: tasks that involve Privacy and GDPR; tasks that involve Authorization and RBAC.

How do I install Employee Biometric Data in Claude Code?

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

How do I install Employee Biometric Data in Codex?

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

Can I use Employee Biometric Data 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 employee-biometric-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/employee-biometric-data, .gemini/skills/employee-biometric-data, .github/skills/employee-biometric-data and .opencode/skills/employee-biometric-data in your project.

What does Employee Biometric Data need to run?

Going by SKILL.md and its folder, Employee Biometric Data needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Employee Biometric Data 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 Employee Biometric Data 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 Employee Biometric Data use?

Employee Biometric Data 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 Employee Biometric Data use?

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

What are the alternatives to Employee Biometric Data?

Skills that share tags, products or a category with Employee Biometric Data: Cis Controls (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Tos Clause Scanner (zebbern/claude-code-guide, 4.7k stars), Healthcare Phi Compliance (affaan-m/ECC, 276k stars) and Policy Opa (AgentSecOps/SecOpsAgentKit, 220 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Employee Biometric Data?

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.