Agent skill

Whistleblower Data

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

Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR.

Apache-2.0Auto-check passedLegal & Compliance

Install Whistleblower Data

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

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

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

At a glance

Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR.

  • Works in 5 steps: Proportionality: Whistleblowing schemes… → Confidentiality: The identity of the… → Anonymous reports: Organisations should… → …
  • Tasks that involve Privacy and GDPR
  • SKILL.md covers Overview, Legal Framework, Data Protection Design for… and Access Restrictions, plus 6 more sections
  • Runs Python scripts from its folder

What it does

Whistleblower Data is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019/1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.

Its SKILL.md is about 4.6k 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 whistleblower-data skill to implement data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR”
  • “/whistleblower-data”

Requirements

  • Python 3

Workflow steps

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

  1. Proportionality: Whistleblowing schemes should be limited to serious matters (financial misconduct, health and safety, environmental…
  2. Confidentiality: The identity of the whistleblower must be kept confidential from the accused and from anyone not directly involved in the…
  3. Anonymous reports: Organisations should not actively encourage anonymous reporting, but must be prepared to handle anonymous reports when…
  4. Accused person's rights: The accused must be informed of the allegations as soon as doing so does not jeopardise the investigation
  5. Retention: Reports and investigation data should be deleted within 2 months of completing the investigation, unless legal proceedings are…

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

Whistleblower Data loads about 4.6k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 2,281 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~4.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.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,281 words, ~4,628 tokens.

Download SKILL.mdSave it as .claude/skills/whistleblower-data/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
whistleblower-data
description
Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR. Covers anonymous reporting channels, identity protection for whistleblowers and accused persons, retention limits, access restrictions, and retaliation prevention. Addresses national transpositions and DPA guidance. Keywords: whistleblower, Directive 2019/1937, anonymous reporting, identity protection, retaliation, retention, reporting channel.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
employee-data-privacy
metadata.tags
whistleblower, directive-2019-1937, anonymous-reporting, identity-protection, retaliation, retention

Whistleblower Data Protection

Overview

The EU Whistleblowing Directive 2019/1937 (Directive on the protection of persons who report breaches of Union law) establishes mandatory internal reporting channels for organisations with 50 or more employees. The Directive creates a fundamental tension with GDPR: whistleblowing channels collect sensitive allegations about identified individuals (the accused), while simultaneously requiring confidentiality protection for the whistleblower. The data protection framework must balance the whistleblower's right to protection, the accused person's right to be informed and to defend themselves, and the organisation's obligation to investigate while complying with data minimisation, purpose limitation, and storage limitation principles.

This skill provides a data protection compliance framework for whistleblowing systems that satisfies both the Directive and GDPR requirements, incorporating guidance from CNIL, the Article 29 Working Party (WP117), and national transposition laws.

EU Whistleblowing Directive 2019/1937

Scope: Applies to reporting of breaches of EU law in areas including public procurement, financial services, product safety, transport safety, environmental protection, food safety, public health, consumer protection, data protection, and competition law.

Organisational requirements:

  • Organisations with 250+ employees: internal reporting channel operational since 17 December 2021
  • Organisations with 50-249 employees: internal reporting channel required since 17 December 2023 (with possible national extensions)
  • Public sector entities regardless of size

Key data protection provisions:

ArticleProvision
Art. 16(1)Member States shall ensure that reporting channels and the actions taken following a report are designed, established, and operated in a secure manner that ensures the confidentiality of the identity of the reporting person and any third party mentioned in the report
Art. 16(2)Personal data that is manifestly not relevant to the handling of a specific report shall not be collected or, if accidentally collected, shall be deleted without undue delay
Art. 16(3)The reporting person and the accused person shall be informed of the processing of their personal data in accordance with GDPR Art. 13 and 14, subject to the limitations in Art. 14(5) and Art. 23
Art. 17(1)Reporting persons shall have access to a balanced, comprehensive, and easily accessible information set about procedures and prerequisites for external reporting
Art. 18Records of every report received shall be kept in compliance with confidentiality requirements; reports shall be stored for no longer than necessary and proportionate
GDPR Intersection

Lawful basis for whistleblowing data processing:

  • Art. 6(1)(c) legal obligation: The Directive (as transposed into national law) creates a legal obligation to operate the reporting channel
  • Art. 6(1)(e) public interest: Investigation of reported breaches serves the public interest
  • Art. 6(1)(f) legitimate interest: The organisation has a legitimate interest in investigating misconduct

Special category data: Whistleblowing reports may contain special category data (e.g., allegations of racial discrimination, health-related misconduct). Where special category data is processed:

  • Art. 9(2)(b) employment obligations: Processing necessary for obligations in the field of employment law
  • Art. 9(2)(g) substantial public interest: Where national law provides a basis for processing special category data in the public interest

Criminal offence data — Art. 10: Whistleblowing reports frequently contain allegations of criminal conduct. Art. 10 processing must be authorised by national law.

WP29 Opinion 1/2006 (WP117)

The Article 29 Working Party's Opinion on whistleblowing schemes, while pre-GDPR, established principles that remain relevant:

  1. Proportionality: Whistleblowing schemes should be limited to serious matters (financial misconduct, health and safety, environmental violations) — not used for routine HR complaints
  2. Confidentiality: The identity of the whistleblower must be kept confidential from the accused and from anyone not directly involved in the investigation
  3. Anonymous reports: Organisations should not actively encourage anonymous reporting, but must be prepared to handle anonymous reports when received
  4. Accused person's rights: The accused must be informed of the allegations as soon as doing so does not jeopardise the investigation
  5. Retention: Reports and investigation data should be deleted within 2 months of completing the investigation, unless legal proceedings are initiated
National Transpositions
JurisdictionTranspositionKey Data Protection Provisions
FranceLoi Waserman (Law No. 2022-401, 21 March 2022)CNIL reference framework for whistleblowing (Délibération No. 2019-139); retention limit of 2 months post-investigation closure; mandatory DPIA for whistleblowing channels
GermanyHinweisgeberschutzgesetz (HinSchG, effective 2 July 2023)Art. 10 — confidentiality of reporting persons' identity; Art. 11 — data retention for 3 years after investigation closure; DPO must be involved in channel design
ItalyD.Lgs. 24/2023Garante del Privacy guidelines on whistleblowing data protection; mandatory DPIA; prohibition on using data for purposes other than the investigation
NetherlandsWet bescherming klokkenluiders (effective 18 February 2023)Enhanced identity protection; external reporting channel via Huis voor Klokkenluiders
SpainLey 2/2023 (effective 13 March 2023)Anonymous reporting must be accepted; retention limit 3 months post-investigation unless proceedings initiated

Data Protection Design for Whistleblowing Channels

Channel Architecture

The whistleblowing channel must be designed to enforce confidentiality by default:

Technical requirements:

RequirementImplementation
End-to-end encryptionAll communications between whistleblower and the channel must be encrypted in transit (TLS 1.3) and at rest (AES-256)
Access segregationOnly designated persons (typically ethics/compliance officers) have access to reports; IT administrators have system access but not content access
Audit loggingAll access to reports is logged with user identity, timestamp, and action
Secure communicationThe channel must provide a secure way for the whistleblower to receive feedback and provide additional information without revealing their identity
Anonymous optionThe system must support anonymous reporting where the whistleblower chooses not to identify themselves
Separate systemThe whistleblowing system should be logically separated from HR systems to prevent data leakage

Dedicated third-party platforms: Many organisations use specialised platforms (EQS Integrity Line, NAVEX Global EthicsPoint, WhistleB, Convercent) that provide:

  • External hosting separated from the organisation's IT infrastructure
  • Anonymous two-way communication channels
  • Encryption and access controls by design
  • Configurable retention and deletion
  • Audit trail and compliance reporting
Anonymous Reporting

Directive position: Art. 6(2) leaves it to Member States to decide whether internal and external reporting channels must accept anonymous reports. Several Member States mandate acceptance of anonymous reports (France, Spain, Italy).

Data protection considerations for anonymous reports:

  • The organisation must process the report based on its content, not the identity of the reporter
  • If the anonymous reporter voluntarily identifies themselves during the investigation, confidentiality protections apply from that point
  • Anonymous reports may be more difficult to investigate; the organisation should still conduct a reasonable investigation
  • IP addresses and metadata that could identify the anonymous reporter must not be logged by the reporting system
Identity Protection

Whistleblower identity:

  • The whistleblower's identity may only be disclosed to persons directly responsible for receiving and following up on reports
  • Disclosure to the accused or to others (including management, HR, or legal counsel not involved in the investigation) requires the explicit consent of the whistleblower
  • In the event of judicial proceedings, disclosure may be required by national procedural law — the whistleblower must be informed before disclosure

Accused person's identity:

  • The accused person has Art. 14 GDPR rights (right to be informed) but these may be restricted under Art. 14(5)(b) (where informing would seriously impair the objectives of the processing) or Art. 23 (restriction to safeguard important objectives of general public interest)
  • The accused must be informed as soon as doing so would no longer jeopardise the investigation (typically after evidence has been secured and witnesses have been interviewed)
  • The accused must not be informed of the whistleblower's identity unless required by judicial order

Third parties mentioned in reports: Witnesses, bystanders, and others mentioned in reports have data protection rights. Their data must be:

  • Minimised to what is relevant to the investigation
  • Protected with the same confidentiality measures
  • Deleted when no longer necessary for the investigation

Access Restrictions

Designated Persons Model
RoleAccessRestriction
Ethics/Compliance OfficerFull access to reports and investigation filesOnly designated officers; typically 2-3 persons in the organisation
Investigation team memberAccess to specific assigned casesAssigned on a case-by-case basis; access revoked when the investigation concludes
DPOAccess to processing records and DPIA; no routine access to report contentMay access content if required for a data protection assessment of the channel itself
Legal counselAccess to assigned cases where legal advice is soughtSubject to legal professional privilege; access documented
CEO/BoardInformed of investigation outcomes; not routine access to report contentException: where the report concerns the Ethics/Compliance Officer, the CEO or Board receives the report directly
Line managersNo accessLine managers are frequently the subjects of reports; they must not have access to the channel
HRNo access unless specifically assigned to an investigationHR involvement must be authorised by the Ethics Officer
ITSystem administration; no access to report contentContent encryption prevents IT access
Show full SKILL.md (870 more words)Show less
Conflict of Interest Protocols
  • If a report names the Ethics/Compliance Officer, the report must be routed to an alternative recipient (typically the Chair of the Audit Committee or an external ombudsperson)
  • If a report names a Board member, the report must be routed to an external legal counsel or the supervisory authority
  • If a report names the DPO, the GDPR oversight function must be temporarily assigned to an alternative

Data Retention

Retention Framework (aligned with strictest national requirements)
Data CategoryRetention PeriodTrigger
Report and investigation file — no misconduct found2 months after investigation closure (CNIL) / 3 years (Germany HinSchG) — apply stricter of applicable national lawInvestigation closure date
Report and investigation file — misconduct confirmed, no proceedings2 months after investigation closure (CNIL) or per national lawInvestigation closure date
Report and investigation file — legal proceedings initiatedDuration of proceedings + statutory limitation periodConclusion of proceedings
Whistleblower identity (where disclosed)Same as investigation fileSame trigger
Anonymous report metadataSame as investigation fileSame trigger
Manifestly unfounded reportsDelete immediately after determinationDetermination date
Data manifestly not relevant (Art. 16(2))Delete without undue delayUpon identification
Retention Implementation
  • Configure the whistleblowing platform's retention automation to apply the applicable national retention period
  • Set automated alerts for retention review at the end of the retention period
  • Ensure that deletion is complete: all copies, backups, and references must be removed
  • Maintain a deletion log (recording that a report was received, investigated, and deleted — without retaining the substance of the report)

Retaliation Prevention — Data Protection Dimension

The Directive prohibits retaliation against whistleblowers (Art. 19). The data protection dimension includes:

  • Monitoring whistleblowers: The organisation must not use monitoring systems (email, internet, CCTV) to identify anonymous reporters
  • Performance data: Performance reviews, absence records, and disciplinary actions following a report must be reviewed for possible retaliatory motivation
  • Access logs: Access logs of the whistleblowing system must be monitored to detect unauthorised access attempts (which may indicate attempts to identify the whistleblower)
  • HR system restrictions: If the whistleblower's identity is known to the Ethics Officer, the HR system must not link the employee record to the whistleblowing file

DPIA Requirement

Whistleblowing channels require a DPIA because the processing:

  • Involves vulnerable data subjects (employees reporting on their employer or colleagues)
  • May involve criminal offence data (Art. 10)
  • Involves systematic collection of data about identified individuals (accused persons)
  • Has significant consequences for data subjects (potential disciplinary action, dismissal, or criminal referral)

The DPIA must assess:

  • Risks to whistleblower confidentiality (identity disclosure)
  • Risks to accused persons' rights (right to be informed, right of defence)
  • Risks of function creep (using the channel for non-whistleblowing purposes)
  • Data security risks (unauthorised access to reports)
  • Cross-border transfer risks (where the whistleblowing platform is hosted outside the EEA)

Atlas Manufacturing Group Example

Atlas Manufacturing Group implemented a whistleblowing channel using EQS Integrity Line for its 2,400 employees across four EU jurisdictions.

Configuration:

  1. Anonymous and identified reporting both accepted
  2. Access restricted to two designated Ethics Officers (Chief Compliance Officer and Deputy)
  3. Where a report concerns the CCO, the report is automatically routed to the Chair of the Board Audit Committee
  4. Retention configured at 2 months post-investigation closure (aligned with CNIL requirements for the French entity — the strictest applicable standard)
  5. Reports involving potential criminal conduct are flagged for legal review; retention extends to the duration of any proceedings
  6. DPIA completed before channel launch, reviewed annually
  7. The DPO conducted an Art. 28 assessment of EQS as a data processor, verified EU data hosting, and confirmed TLS 1.3 encryption in transit and AES-256 at rest
  8. Privacy notice provided to all employees explaining the channel, data processing, confidentiality measures, and rights of both reporters and accused persons

Incident: An employee submitted an anonymous report alleging that a production manager was falsifying safety inspection records. The Ethics Officer initiated an investigation, securing documentary evidence before informing the accused manager. The manager was informed of the substance of the allegations but not the identity of the reporter (which was unknown due to anonymity). The investigation confirmed the allegations, and the manager was dismissed. The investigation file was retained for the duration of the unfair dismissal proceedings and deleted 6 months after the tribunal decision.

Enforcement Precedents

AuthorityCaseFine/OutcomeKey Issue
CNIL (France)Deliberation SAN-2020-015EUR 100,000Whistleblowing system retained reports for 5 years — excessive; CNIL requires 2 months post-investigation
Garante (Italy)Provvedimento 2022-0178Processing restrictionWhistleblowing channel did not ensure confidentiality; IT staff had access to report content
AEPD (Spain)PS/00123/2023EUR 150,000Organisation disclosed whistleblower identity to the accused person without consent or legal requirement
BfDI (Germany)2023 AuditCorrective measuresWhistleblowing channel did not support anonymous reporting as required by HinSchG
Autoriteit Persoonsgegevens (NL)2023 InvestigationWarningOrganisation failed to conduct DPIA for whistleblowing channel

Integration Points

  • Employee Monitoring DPIA: Whistleblowing channels are subject to DPIA (see employee-monitoring-dpia skill).
  • Employee DSAR Response: DSARs from accused persons must be balanced against whistleblower confidentiality (see employee-dsar-response skill).
  • Employment Consent Limits: Consent is not the lawful basis for whistleblowing processing (see employment-consent-limits skill).
  • HR System Privacy Config: Whistleblowing data must be separated from HR system data (see hr-system-privacy-config skill).
  • Background Check Privacy: Investigation findings may inform background check requirements for future roles (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/whistleblower-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

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

Whistleblower Data compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Whistleblower Data this skillmukul975/Privacy-Data-Protection-Skills295—~4.6kAutomated 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 yesterday
    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 Whistleblower Data

What does Whistleblower Data do?

Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR. Whistleblower Data is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implements data protection compliance for whistleblowing systems under EU Directive 2019/1937 and GDPR.

When should I use Whistleblower Data?

Whistleblower Data fits situations like: tasks that involve Privacy and GDPR.

How do I install Whistleblower Data in Claude Code?

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

How do I install Whistleblower Data in Codex?

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

Can I use Whistleblower 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 whistleblower-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/whistleblower-data, .gemini/skills/whistleblower-data, .github/skills/whistleblower-data and .opencode/skills/whistleblower-data in your project.

What does Whistleblower Data need to run?

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

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

Whistleblower 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 Whistleblower Data use?

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

What are the alternatives to Whistleblower Data?

Skills that share tags, products or a category with Whistleblower Data: 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 Whistleblower Data?

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.