C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Provides GDPR Article 14 information for personal data obtained from sources other than the data subject, covering timing requirements (within reasonable period, max one month), source disclosure…
Install Indirect Collection Notice
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills indirect-collection-notice --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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/indirect-collection-notice .claude/skills/indirect-collection-notice && rm -rf skills-srcUse ~/.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/
Install the "indirect-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-notice into .claude/skills/indirect-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indirect-collection-notice", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-noticeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills indirect-collection-notice --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/privacy/indirect-collection-notice .agents/skills/indirect-collection-notice && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "indirect-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-notice into .agents/skills/indirect-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indirect-collection-notice", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills indirect-collection-notice --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/privacy/indirect-collection-notice .cursor/skills/indirect-collection-notice && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "indirect-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-notice into .cursor/skills/indirect-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indirect-collection-notice", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mukul975/Privacy-Data-Protection-Skills.git --path skills/privacy/indirect-collection-notice--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills indirect-collection-notice --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/privacy/indirect-collection-notice .gemini/skills/indirect-collection-notice && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "indirect-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-notice into .gemini/skills/indirect-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indirect-collection-notice", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mukul975/Privacy-Data-Protection-Skills indirect-collection-noticeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/privacy/indirect-collection-notice .github/skills/indirect-collection-notice && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "indirect-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-notice into .github/skills/indirect-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indirect-collection-notice", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills indirect-collection-notice --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/privacy/indirect-collection-notice .opencode/skills/indirect-collection-notice && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "indirect-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/indirect-collection-notice into .opencode/skills/indirect-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "indirect-collection-notice", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
indirect-collection-notice- GitHub stars
- 301
- Token cost
- ~2.1k tokens
- SKILL.md length
- 987 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Provides GDPR Article 14 information for personal data obtained from sources other than the data subject, covering timing requirements (within reasonable period, max one month), source disclosure…
- Works in 6 steps: Identify Indirect Data Acquisition → Determine the Timing Obligation → Prepare the Art. 14 Notice → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Common Indirect Collection… and Indirect Collection…
- Runs Python scripts from its folder
What it does
Indirect Collection Notice is an agent skill from mukul975/Privacy-Data-Protection-Skills. Provides GDPR Article 14 information for personal data obtained from sources other than the data subject, covering timing requirements (within reasonable period, max one month), source disclosure, all required elements, and exemptions under Art. 14(5). Activate for Art. 14, indirect collection, third-party data source, indirect data notice queries.
Its SKILL.md is about 2.1k 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 indirect-collection-notice skill to provide GDPR Article 14 information for personal data obtained from sources other than the data subject…”
- “/indirect-collection-notice”
Requirements
- Python 3
Workflow steps
6 steps, taken from the step headings in SKILL.md.
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
Indirect Collection Notice loads about 2.1k tokens when it runs, and up to ~3.3k if it reads all its reference files. Until then it costs about 94 tokens; SKILL.md has 987 words of instructions outside code blocks.
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). 987 words, ~2,086 tokens.
Download SKILL.mdSave it as
.claude/skills/indirect-collection-notice/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- indirect-collection-notice
- description
- Provides GDPR Article 14 information for personal data obtained from sources other than the data subject, covering timing requirements (within reasonable period, max one month), source disclosure, all required elements, and exemptions under Art. 14(5). Activate for Art. 14, indirect collection, third-party data source, indirect data notice queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- indirect-collection, gdpr-article-14, third-party-data, source-disclosure, privacy-notice
Providing Indirect Collection Information
Overview
GDPR Article 14 applies when a controller obtains personal data from a source other than the data subject — such as from third-party data brokers, publicly available sources, other controllers, or through automated observation by third parties. The controller must still provide the data subject with comprehensive information about the processing, but the timing and content requirements differ from Art. 13.
Legal Foundation
GDPR Article 14 — Information Where Personal Data Have Not Been Obtained from the Data Subject
Required Information (Art. 14(1)-(2))
All elements required under Art. 13(1)(a)-(f) and Art. 13(2)(a)-(g) PLUS:
| Element | Article | Description |
|---|---|---|
| Categories of personal data | Art. 14(1)(d) | The categories of personal data concerned (not required under Art. 13 because the subject already knows what they provided) |
| Source of data | Art. 14(2)(f) | From which source the personal data originate, and if applicable, whether it came from publicly accessible sources |
Timing Requirements (Art. 14(3))
The controller must provide the information:
- Art. 14(3)(a) — Default: Within a reasonable period after obtaining the personal data, but at the latest within one month, having regard to the specific circumstances in which the personal data are processed.
- Art. 14(3)(b) — Communication with data subject: If the personal data are to be used for communication with the data subject, at the latest at the time of the first communication to that data subject.
- Art. 14(3)(c) — Disclosure to another recipient: If a disclosure to another recipient is envisaged, at the latest when the personal data are first disclosed.
The earliest applicable deadline governs.
Exemptions Under Art. 14(5)
Art. 14(1)-(4) shall not apply where and insofar as:
- Art. 14(5)(a) — Data subject already has the information: The data subject already has the information.
- Art. 14(5)(b) — Impossible or disproportionate effort: The provision of such information proves impossible or would involve a disproportionate effort, in particular for processing for archiving purposes in the public interest, scientific or historical research, or statistical purposes under Art. 89(1). In such cases, the controller must take appropriate measures to protect the data subject's rights and freedoms, including making the information publicly available.
- Art. 14(5)(c) — Union or Member State law: Obtaining or disclosure is expressly laid down by Union or Member State law which provides appropriate measures to protect the data subject's legitimate interests.
- Art. 14(5)(d) — Professional secrecy: The personal data must remain confidential subject to an obligation of professional secrecy regulated by Union or Member State law, including a statutory obligation of secrecy.
Common Indirect Collection Scenarios at Meridian Analytics Ltd
| Scenario | Data Source | Categories | Timing Obligation |
|---|---|---|---|
| Client employee data received from employer client | Employer (another controller) | Name, email, job title, access permissions | Within 1 month of receipt, or at first communication |
| Companies House / public registry data | Publicly accessible source | Director names, registered address, filing history | Within 1 month; note public source in notice |
| Credit reference agency data | Credit reference agency (Experian, Equifax) | Credit score, payment history, financial indicators | At first communication or within 1 month |
| Referral from existing client | Existing client | Name, email, company | At first communication with referred person |
| Data enrichment from third-party provider | Data enrichment provider | Firmographic data, industry classification | Within 1 month of enrichment |
Indirect Collection Information Workflow
Step 1: Identify Indirect Data Acquisition
- Map all sources of personal data that are not the data subjects themselves.
- For each source, document:
- Source identity and type (controller, publicly accessible, data broker)
- Categories of personal data received
- Legal basis for receiving the data
- Date of receipt
- Purpose of processing
Step 2: Determine the Timing Obligation
Apply the earliest applicable deadline from Art. 14(3)(a)-(c):
[Data Received from Third Party]
│
▼
[Will data be used to contact the subject?]
├── Yes ──► Notify at or before first communication
└── No ──► [Will data be disclosed to another recipient?]
├── Yes ──► Notify before or at disclosure
└── No ──► Notify within reasonable period (max 1 month)Show full SKILL.md (393 more words)Show less
Step 3: Prepare the Art. 14 Notice
The notice must contain all elements specified in Art. 14(1) and (2). Use the following structure:
- Controller identity: Meridian Analytics Ltd, 47 Canary Wharf Tower, London E14 5AB
- DPO contact: Dr Sarah Chen, dpo@meridiananalytics.co.uk
- Purposes and legal basis: State each purpose and its legal basis
- Categories of personal data: List the categories obtained (since the subject did not provide them directly)
- Recipients: Identify recipients or categories
- International transfers: Describe any transfers and safeguards
- Retention period: State period or criteria
- Data subject rights: List all applicable rights
- Right to withdraw consent: If applicable
- Right to complain: ICO details
- Source of data: Identify the source and whether it is publicly accessible
- Automated decision-making: If applicable
- Further processing: If applicable
Step 4: Assess Exemptions
Before deciding not to provide Art. 14 information, assess each exemption strictly:
| Exemption | Assessment | Documentation Required |
|---|---|---|
| Art. 14(5)(a) — Already has info | Verify the subject has received materially equivalent information from another source | Record the source and date of prior information |
| Art. 14(5)(b) — Impossible/disproportionate effort | Conduct and document proportionality assessment considering: number of data subjects, age of data, compensatory measures available | Written proportionality assessment, approved by DPO, with compensatory measures (e.g., publish information on website) |
| Art. 14(5)(c) — Law requires acquisition | Identify the specific legal provision | Citation of the provision |
| Art. 14(5)(d) — Professional secrecy | Identify the statutory obligation of secrecy | Citation of the provision |
The EDPB Guidelines on Transparency (WP260 rev.01) state that the Art. 14(5)(b) exemption should be interpreted restrictively and that the mere inconvenience or cost of providing information is not sufficient to constitute "disproportionate effort."
Step 5: Deliver the Notice
- Email: If the subject's email address is available, send the Art. 14 notice by email.
- Postal mail: If only a postal address is available, send by first-class post.
- Combined with first communication: Where the first communication is an email or letter, include the Art. 14 information in or with that communication.
- Published notice: Where the Art. 14(5)(b) exemption applies and compensatory measures are required, publish the information on the controller's website.
Step 6: Document and Record
- Record the date of each Art. 14 notification.
- Record the method of delivery.
- Record any exemption relied upon and its justification.
- Retain the record for 3 years.
© 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/indirect-collection-notice 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
Indirect Collection Notice 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Indirect Collection Notice this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| C15tc15t/c15t | 1.9k | 1 repos | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Korean Privacy Termskimlawtech/korean-privacy-terms | 587 | — | ~2.9k | Automated safety check: Pass | Apache-2.0 | |
| Gdpr ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Safe Harbor Coverage Audit
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
Korean Privacy Terms
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
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…
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
Pii Contract Analyze
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
More from mukul975/Privacy-Data-Protection-Skills
All 280 skills in this repoAge Gating Services
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
AI Data Retention
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
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.
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).
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.
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.
Related
Categories
Questions about Indirect Collection Notice
What does Indirect Collection Notice do?
Provides GDPR Article 14 information for personal data obtained from sources other than the data subject, covering timing requirements (within reasonable period, max one month), source disclosure…. Indirect Collection Notice is an agent skill from mukul975/Privacy-Data-Protection-Skills. Provides GDPR Article 14 information for personal data obtained from sources other than the data subject, covering timing requirements (within reasonable period, max one month), source disclosure, all required elements, and exemptions under Art.
When should I use Indirect Collection Notice?
Indirect Collection Notice fits situations like: tasks that involve Privacy and GDPR.
How do I install Indirect Collection Notice in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a claude-code`. Or copy the skill folder (skills/privacy/indirect-collection-notice in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/indirect-collection-notice in your project. Claude Code loads it when a task matches its description.
How do I install Indirect Collection Notice in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill indirect-collection-notice -a codex`. Or copy the skill folder (skills/privacy/indirect-collection-notice in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/indirect-collection-notice in your project. Codex loads it when a task matches its description.
Can I use Indirect Collection Notice 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 indirect-collection-notice -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/indirect-collection-notice, .gemini/skills/indirect-collection-notice, .github/skills/indirect-collection-notice and .opencode/skills/indirect-collection-notice in your project.
What does Indirect Collection Notice need to run?
Going by SKILL.md and its folder, Indirect Collection Notice needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Indirect Collection Notice 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 Indirect Collection Notice 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 Indirect Collection Notice use?
Indirect Collection Notice 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 Indirect Collection Notice use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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.2k tokens, read only when the agent opens those files.
What are the alternatives to Indirect Collection Notice?
Skills that share tags, products or a category with Indirect Collection Notice: C15t (c15t/c15t, 1.9k stars), HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), Korean Privacy Terms (kimlawtech/korean-privacy-terms, 587 stars) and Gdpr Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Indirect Collection Notice?
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.