Agent skill

Bcr Establishment

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

Guides development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international data transfers.

Apache-2.0Auto-check passedLegal & Compliance

Install Bcr Establishment

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

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

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

At a glance

Guides development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international data transfers.

  • Works in 8 steps: Preparation (Months 1-3) → Lead SA Identification (Month 3) → Formal Submission (Month 4) → …
  • Tasks that involve Privacy and GDPR
  • SKILL.md covers Overview, Art. 47(2) Content Requirements, BCR Approval Process and WP256 Rev.01 Referential (BCR…, plus 2 more sections
  • Runs Python scripts from its folder

What it does

Bcr Establishment is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international data transfers. Covers Art. 47(2)(a)-(n) content requirements, BCR approval process with lead supervisory authority, and WP256/WP257 referentials. Keywords: BCR, binding corporate rules, intra-group transfers, Art. 47.

Its SKILL.md is about 3.7k 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 bcr-establishment skill to guide development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international…”
  • “/bcr-establishment”

Requirements

  • Python 3

Workflow steps

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

  1. Preparation (Months 1-3)
  2. Lead SA Identification (Month 3)
  3. Formal Submission (Month 4)
  4. Lead SA Review (Months 4-9)
  5. Cooperation Procedure (Months 9-12)
  6. Consistency Mechanism (Months 12-14)
  7. Formal Approval (Months 14-18)
  8. Implementation and Rollout (Post-Approval)

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

Bcr Establishment loads about 3.7k tokens when it runs, and up to ~6.7k if it reads all its reference files. Until then it costs about 87 tokens; SKILL.md has 1,983 words of instructions outside code blocks.

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

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

Safety

Auto-check passed

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

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

SKILL.md

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

Download SKILL.mdSave it as .claude/skills/bcr-establishment/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
bcr-establishment
description
Guides development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international data transfers. Covers Art. 47(2)(a)-(n) content requirements, BCR approval process with lead supervisory authority, and WP256/WP257 referentials. Keywords: BCR, binding corporate rules, intra-group transfers, Art. 47.
license
Apache-2.0
metadata.author
mukul975
metadata.version
1.0
metadata.domain
privacy
metadata.subdomain
cross-border-transfers
metadata.tags
bcr, binding-corporate-rules, article-47, intra-group-transfers, gdpr-chapter-5

Establishing Binding Corporate Rules

Overview

Binding Corporate Rules (BCRs) are internal data protection policies adopted by a multinational group of undertakings or enterprises to permit transfers of personal data from EU/EEA entities to group members in third countries under GDPR Article 47. BCRs provide a legally binding framework that ensures an essentially equivalent level of protection for personal data transferred within the corporate group, regardless of the destination country. The approval process involves a lead supervisory authority, a cooperation procedure among concerned SAs, and typically spans 12 to 18 months from initial submission to final approval.

Art. 47(2) Content Requirements

(a) Structure and Contact Details of the Group

The BCR must specify the structure of the group of undertakings or enterprises, including the identity and contact details of each member bound by the BCR.

Athena Global Logistics implementation:

  • Group parent entity: Athena Global Logistics GmbH, Friedrichstrasse 112, 10117 Berlin, Germany
  • Group DPO: Elisa Brandt, elisa.brandt@athenalogistics.eu, +49 30 1234 5678
  • Bound entities: All wholly-owned subsidiaries and majority-controlled affiliates listed in BCR Annex A (currently 47 entities across 31 jurisdictions)
  • Structure chart: Updated annually and annexed to the BCR as Annex A, reflecting the legal entity hierarchy from the parent to each subsidiary
(b) Data Transfers Covered

The BCR must describe the data transfers or set of transfers, including the categories of personal data, the type of processing and its purposes, the type of data subjects affected, and the identification of the third country or countries.

Implementation requirements:

  • Scope document specifying all intra-group transfer categories: HR data (employee records, payroll, benefits), customer data (shipment records, billing, communications), supplier data (contact details, contractual records), and operational data (vehicle tracking, warehouse access logs)
  • Purpose register linking each transfer category to one or more specified purposes: employment administration, freight operations, financial reporting, regulatory compliance, IT support
  • Data subject taxonomy: employees, contractors, temporary workers, customers (individual and corporate contacts), suppliers, business partners, website visitors
  • Destination country register: all non-EEA jurisdictions where bound group entities operate
(c) Legally Binding Nature

The BCR must establish the legally binding nature of the rules, both internally and externally.

Implementation elements:

  • Intra-group agreement signed by all bound entities, creating contractual obligations enforceable between group members
  • BCR adopted as a binding corporate policy by resolution of the board of the parent company, with cascading adoption resolutions by each subsidiary board
  • Employee handbook incorporation: BCR summary and compliance obligations included in all employment contracts and data handling procedures
  • External enforceability: explicit third-party beneficiary clause granting data subjects the right to enforce the BCR provisions directly against any bound entity
(d) Application of the General Data Protection Principles

The BCR must demonstrate the application of all general data protection principles under Article 5, including purpose limitation, data minimisation, limited storage periods, data quality, data protection by design and by default, legal basis, special category data processing, and measures to ensure data security.

Required content:

  • Purpose limitation: data transferred under the BCR may be processed only for the purposes specified in the BCR scope document; any new purpose requires a compatibility assessment under Art. 6(4) and BCR amendment procedure
  • Data minimisation: transfers limited to data adequate, relevant, and necessary for the specified purpose; group-wide data classification policy mandating review of data elements before transfer
  • Storage limitation: retention schedules specified per data category and jurisdiction; automated deletion or anonymisation upon expiry
  • Accuracy: procedures for data subjects to request correction; data quality checks at transfer points
  • Security: minimum security standards applicable to all bound entities per BCR Annex C (aligned with ISO 27001:2022)
(e) Third-Party Beneficiary Rights

Data subjects must be able to enforce the BCR as third-party beneficiaries and have the right to:

  • Receive compensation for material and non-material damages resulting from BCR violations
  • Lodge complaints with the competent supervisory authority
  • Exercise all data subject rights (access, rectification, erasure, restriction, portability, objection) against any bound entity
(f) Acceptance of Liability

The BCR must include acceptance of liability by the entity established in the EU (the BCR Lead) for any breach committed by a non-EU bound entity, with the burden of proof on the BCR Lead to demonstrate the non-EU entity was not responsible.

Athena Global Logistics implementation:

  • BCR Lead: Athena Global Logistics GmbH (Berlin)
  • Liability clause: The BCR Lead accepts liability for breaches by any non-EU bound entity and agrees to take necessary action to remedy the breach and pay compensation
  • Insurance: professional indemnity insurance covering BCR-related claims with a minimum coverage of EUR 10,000,000 per claim
(g) Information Provided to Data Subjects

The BCR must specify the information provided to data subjects about the BCR and their rights, including:

  • The BCR and a summary in plain language published on the company website
  • Information about the complaints procedure and the right to lodge a complaint with the SA
  • Information about the right to seek judicial remedies
  • The identity and contact details of the BCR Lead and the DPO
(h) DPO Tasks

The BCR must describe the tasks of the Data Protection Officer (or equivalent responsible person/entity), including:

  • Monitoring BCR compliance across all bound entities
  • Conducting or overseeing BCR audits
  • Handling data subject complaints related to BCR transfers
  • Serving as the contact point for supervisory authorities
  • Reporting to the board on BCR compliance status
(i) Complaint Procedures

The BCR must establish a complaints mechanism enabling data subjects to:

  • Submit complaints to any bound entity or the BCR Lead
  • Receive a response within 30 calendar days
  • Escalate unresolved complaints to the DPO, then to the competent SA
  • Access mediation or arbitration as an alternative dispute resolution mechanism
(j) Compliance Verification Mechanisms

The BCR must describe mechanisms for ensuring compliance:

  • Internal BCR audit programme: conducted by the internal audit function, with at least one full-cycle audit every three years covering all bound entities
  • Annual compliance self-assessments by each bound entity, reported to the DPO
  • Monitoring tools: data transfer logging, access reviews, policy adherence metrics
  • Results reported to the BCR Lead's management and, upon request, to the competent SA
(k) Change Reporting Mechanisms

The BCR must establish reporting and recording mechanisms for changes:

  • Amendment procedure: any change to the BCR requires approval by the BCR Lead, notification to the lead SA, and communication to all bound entities
  • Annual update cycle for the entity list (Annex A) and security standards (Annex C)
  • Material changes (new countries, new data categories, structural changes) must be notified to the SA before implementation
(l) Cooperation with the Supervisory Authority

The BCR must establish a cooperation mechanism with the SA:

  • The BCR Lead will submit to the jurisdiction of the competent SA
  • The BCR Lead will make audit results available to the SA upon request
  • The BCR Lead will comply with SA advice regarding BCR interpretation and application
  • Annual BCR compliance report submitted to the lead SA
(m) Local Law Reporting

The BCR must require any bound entity to report to the BCR Lead any legal requirement in its jurisdiction that is likely to have a substantial adverse effect on the guarantees provided by the BCR.

Implementation:

  • Annual local law survey conducted by outside counsel in each jurisdiction
  • Immediate escalation procedure for new legislation or government access demands that conflict with BCR commitments
  • Assessment protocol: evaluate whether the local law requirement materially undermines BCR protections and, if so, notify the SA and suspend affected transfers
Show full SKILL.md (774 more words)Show less
(n) Training

The BCR must describe appropriate data protection training for personnel with access to transferred data:

  • Mandatory onboarding training for all new employees with data access
  • Annual refresher training on BCR requirements, data subject rights, and breach reporting
  • Role-specific training for IT administrators, HR staff, and customer-facing personnel
  • Training records maintained centrally and available for SA audit

BCR Approval Process

Step 1: Preparation (Months 1-3)
  1. Draft the BCR document against the WP256 rev.01 referential (BCR for controllers) or WP257 rev.01 referential (BCR for processors).
  2. Map all intra-group data flows to identify the transfers covered by the BCR.
  3. Prepare the Annex A entity list, Annex B transfer scope, and Annex C security standards.
  4. Conduct a gap analysis against the referential checklist.
  5. Prepare the BCR application form for the lead SA.
Step 2: Lead SA Identification (Month 3)
  1. Identify the lead SA per the EDPB criteria: the SA of the Member State where the BCR Lead (typically the parent or the entity with delegated data protection responsibility) is established.
  2. For Athena Global Logistics: the lead SA is the Berliner Beauftragte fuer Datenschutz und Informationsfreiheit (BlnBDI).
  3. Identify concerned SAs: all SAs of Member States where bound entities are established.
Step 3: Formal Submission (Month 4)
  1. Submit the BCR application to the lead SA with all supporting documentation.
  2. Include: BCR text, entity list, data flow maps, gap analysis results, evidence of internal approval, DPO contact details.
Step 4: Lead SA Review (Months 4-9)
  1. The lead SA reviews the BCR for completeness and compliance with Art. 47(2).
  2. Expect multiple rounds of questions and amendments.
  3. Maintain a correspondence log and amendment tracker.
  4. Typical duration: 4-6 months of iterative review.
Step 5: Cooperation Procedure (Months 9-12)
  1. The lead SA circulates the reviewed BCR to all concerned SAs.
  2. Concerned SAs have a defined period (typically 2 months) to raise objections or comments.
  3. The lead SA consolidates feedback and works with the applicant to address concerns.
  4. If consensus is reached, the lead SA provides a positive opinion.
Step 6: Consistency Mechanism (Months 12-14)
  1. Under Art. 63-64 GDPR, the lead SA may submit the draft approval to the EDPB for an opinion if there are unresolved objections.
  2. The EDPB issues an opinion within 8 weeks (extendable by 6 weeks).
Step 7: Formal Approval (Months 14-18)
  1. The lead SA issues the formal BCR approval decision.
  2. The approval may include conditions or recommendations.
  3. The BCR Lead must implement any conditions before relying on the BCR for transfers.
  4. Publish the approved BCR summary on the EDPB BCR register and the company website.
Step 8: Implementation and Rollout (Post-Approval)
  1. Communicate the approved BCR to all bound entities.
  2. Execute the intra-group agreement binding all entities.
  3. Deploy the training programme.
  4. Activate the audit programme.
  5. Begin the monitoring and reporting cycle.

WP256 Rev.01 Referential (BCR for Controllers) — Key Elements Checklist

ElementWP256 SectionStatus
Binding nature of the BCRSection 1Required
Scope — data, transfers, entitiesSection 2Required
Application of GDPR principlesSection 3Required
Rights of data subjects and enforcementSection 4Required
Liability and jurisdictionSection 5Required
Cooperation duty with SAsSection 5.4Required
How to handle requests from authoritiesSection 5.5Required
Complaint handlingSection 6Required
Training programmeSection 7Required
Audit programmeSection 7Required
Network of privacy officersSection 7.3Required
Update and change managementSection 8Required
Local law conflictsSection 5.5Required
Description of conflict resolutionSection 6Required

WP257 Rev.01 Referential (BCR for Processors) — Additional Elements

ElementDescription
Instructions-based processingProcessor BCR must confirm processing only on documented instructions
Sub-processor managementProcedures for sub-processor authorisation, due diligence, and contractual flow-down
Controller notificationObligation to inform the controller of any inability to comply
Data return/deletionProcedures upon termination of the processing relationship
Audit facilitationObligation to make available all information necessary to demonstrate compliance

Post-Approval Ongoing Obligations

  1. Annual compliance audit: At least one comprehensive BCR audit per year, with each bound entity audited within a three-year rolling cycle.
  2. Entity list maintenance: Annex A updated whenever entities join or leave the group; SA notified of material changes.
  3. Incident reporting: Any breach involving BCR-covered data reported to the BCR Lead and, where required, to the competent SA per Art. 33.
  4. Local law monitoring: Continuous monitoring of legal developments in third countries that may affect BCR protections.
  5. Training records: Maintained and available for SA review at all times.
  6. BCR review and amendment: Full BCR review at least every three years, with interim amendments as needed for material changes.

© 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/bcr-establishment 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

Bcr Establishment 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.

Bcr Establishment compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bcr Establishment this skillmukul975/Privacy-Data-Protection-Skills297—~3.7kAutomated 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-Compliance9431 repos~3.9kAutomated safety check: PassMIT
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance9431 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…

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

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

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

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

    297 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).

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

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

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

Questions about Bcr Establishment

What does Bcr Establishment do?

Guides development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international data transfers. Bcr Establishment is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides development and approval of Binding Corporate Rules under GDPR Article 47 for intra-group international data transfers.

When should I use Bcr Establishment?

Bcr Establishment fits situations like: tasks that involve Privacy and GDPR.

How do I install Bcr Establishment in Claude Code?

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

How do I install Bcr Establishment in Codex?

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

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

What does Bcr Establishment need to run?

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

Does Bcr Establishment 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 Bcr Establishment 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 Bcr Establishment use?

Bcr Establishment 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 Bcr Establishment use?

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

What are the alternatives to Bcr Establishment?

Skills that share tags, products or a category with Bcr Establishment: 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, 943 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bcr Establishment?

mukul975 (a GitHub user) maintains it in mukul975/Privacy-Data-Protection-Skills, which has 297 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.