C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Provides GDPR Article 13 information at the point of direct data collection, covering all required elements under Art.
Install Direct Collection Notice
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill direct-collection-notice -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills direct-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/direct-collection-notice .claude/skills/direct-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 "direct-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/direct-collection-notice into .claude/skills/direct-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direct-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/direct-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 direct-collection-notice -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills direct-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/direct-collection-notice .agents/skills/direct-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 "direct-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/direct-collection-notice into .agents/skills/direct-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direct-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 direct-collection-notice -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills direct-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/direct-collection-notice .cursor/skills/direct-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 "direct-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/direct-collection-notice into .cursor/skills/direct-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direct-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/direct-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 direct-collection-notice -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills direct-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/direct-collection-notice .gemini/skills/direct-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 "direct-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/direct-collection-notice into .gemini/skills/direct-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direct-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 direct-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 direct-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/direct-collection-notice .github/skills/direct-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 "direct-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/direct-collection-notice into .github/skills/direct-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direct-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 direct-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 direct-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/direct-collection-notice .opencode/skills/direct-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 "direct-collection-notice" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/direct-collection-notice into .opencode/skills/direct-collection-notice/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "direct-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
direct-collection-notice- GitHub stars
- 301
- Token cost
- ~2.2k tokens
- SKILL.md length
- 1,134 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 13 information at the point of direct data collection, covering all required elements under Art.
- Works in 4 steps: Controller identity (name) → Each specific purpose for which data is… → Any processing that may be unexpected or… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, Legal Foundation, Layered Notice Design for… and Collection Scenario Templates, plus 1 more section
- Runs Python scripts from its folder
What it does
Direct Collection Notice is an agent skill from mukul975/Privacy-Data-Protection-Skills. Provides GDPR Article 13 information at the point of direct data collection, covering all required elements under Art. 13(1)(a)-(f) and Art. 13(2)(a)-(g), layered notice design, and timing requirements. Activate for Art. 13, direct collection notice, privacy notice at collection, data collection information queries.
Its SKILL.md is about 2.2k 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 direct-collection-notice skill to provide GDPR Article 13 information at the point of direct data collection, covering all required elements…”
- “/direct-collection-notice”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Controller identity (name)
- Each specific purpose for which data is being collected
- Any processing that may be unexpected or objectionable
- Link to the full privacy notice (Layer 2)
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
Direct Collection Notice loads about 2.2k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 86 tokens; SKILL.md has 1,134 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). 1,134 words, ~2,230 tokens.
Download SKILL.mdSave it as
.claude/skills/direct-collection-notice/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- direct-collection-notice
- description
- Provides GDPR Article 13 information at the point of direct data collection, covering all required elements under Art. 13(1)(a)-(f) and Art. 13(2)(a)-(g), layered notice design, and timing requirements. Activate for Art. 13, direct collection notice, privacy notice at collection, data collection information queries.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- data-subject-rights
- metadata.tags
- direct-collection-information, gdpr-article-13, privacy-notice, data-collection, layered-notice
Providing Direct Collection Information
Overview
GDPR Article 13 requires controllers to provide specific information to data subjects at the time personal data is collected directly from them. This information must be provided at the point of collection, not afterwards. This skill provides the complete checklist of required elements, guidance on layered notice design, and templates for common collection scenarios.
Legal Foundation
GDPR Article 13 — Information to Be Provided Where Personal Data Are Collected from the Data Subject
Art. 13(1) — First Layer (Mandatory at Point of Collection)
Where personal data relating to a data subject are collected from the data subject, the controller shall, at the time when personal data are obtained, provide the data subject with all of the following information:
| Element | Article | Description |
|---|---|---|
| Controller identity | Art. 13(1)(a) | Identity and contact details of the controller and, where applicable, of the controller's representative |
| DPO contact | Art. 13(1)(b) | Contact details of the data protection officer, where applicable |
| Purposes and legal basis | Art. 13(1)(c) | The purposes of the processing and the legal basis under Art. 6 |
| Legitimate interests | Art. 13(1)(d) | Where processing is based on Art. 6(1)(f), the legitimate interests pursued by the controller or by a third party |
| Recipients | Art. 13(1)(e) | The recipients or categories of recipients of the personal data, if any |
| International transfers | Art. 13(1)(f) | Where applicable, that the controller intends to transfer data to a third country or international organisation, the existence or absence of an adequacy decision, or reference to appropriate safeguards and means of obtaining a copy or where they have been made available |
Art. 13(2) — Second Layer (Necessary for Fair Processing)
In addition to the information referred to in paragraph 1, the controller shall, at the time when personal data are obtained, provide the data subject with the following further information necessary to ensure fair and transparent processing:
| Element | Article | Description |
|---|---|---|
| Retention period | Art. 13(2)(a) | The period for which the personal data will be stored, or if that is not possible, the criteria used to determine that period |
| Data subject rights | Art. 13(2)(b) | The existence of the right to request access, rectification, erasure, restriction, object, and portability |
| Right to withdraw consent | Art. 13(2)(c) | Where processing is based on Art. 6(1)(a) or Art. 9(2)(a), the right to withdraw consent at any time, without affecting the lawfulness of processing based on consent before its withdrawal |
| Right to complain | Art. 13(2)(d) | The right to lodge a complaint with a supervisory authority |
| Statutory/contractual requirement | Art. 13(2)(e) | Whether the provision of personal data is a statutory or contractual requirement, or a requirement necessary to enter into a contract, and whether the data subject is obliged to provide the data and the possible consequences of failure to provide |
| Automated decision-making | Art. 13(2)(f) | The existence of automated decision-making including profiling, meaningful information about the logic, significance, and envisaged consequences |
| Further processing | Art. 13(2)(g) | Where the controller intends to further process for a purpose other than the original, provide information on that other purpose and any relevant further information under Art. 13(2) |
Timing (Art. 13(1) First Sentence)
All Art. 13 information must be provided at the time when personal data are obtained — before or at the moment of collection, not after.
Exemption (Art. 13(4))
Art. 13(1)-(3) shall not apply where and insofar as the data subject already has the information.
Layered Notice Design for Direct Collection
Principle
The EDPB Guidelines on Transparency (WP260 rev.01) recommend a layered approach for direct collection to balance completeness with usability:
Layer 1: Just-In-Time Notice
Displayed directly at the point of data collection (e.g., on the form, above the submit button, within the app screen):
Required elements at minimum:
- Controller identity (name)
- Each specific purpose for which data is being collected
- Any processing that may be unexpected or objectionable
- Link to the full privacy notice (Layer 2)
Format guidance:
- Maximum 150 words
- Visible without scrolling on the collection interface
- No click-through required to see the core information
- Use icons where appropriate (per Art. 12(7))
Layer 2: Full Privacy Notice
Linked from Layer 1, containing ALL Art. 13(1)(a)-(f) and Art. 13(2)(a)-(g) elements.
Show full SKILL.md (458 more words)Show less
Layer 3: Detailed Supplementary Information
Available on request or via contextual links:
- Full legitimate interest assessments
- Complete international transfer mechanism documentation
- Detailed automated decision-making logic explanations
Collection Scenario Templates
Scenario 1: Online Registration Form
Collection point: Account registration page Data collected: Name, email, password, company name, job title Purpose: Account creation and service provision
Just-in-time notice text:
Meridian Analytics Ltd will use the information you provide to create and manage your account and deliver our analytics services. We may also use your email to send you service-related communications. Read our full privacy notice for details on how we use your data, who we share it with, and your rights.
Scenario 2: Newsletter Signup
Collection point: Newsletter subscription form Data collected: Email address, name (optional) Purpose: Marketing communications
Just-in-time notice text:
By subscribing, you consent to Meridian Analytics Ltd sending you marketing emails about our products and services. You can unsubscribe at any time by clicking the link in any email. We will not share your email address with third parties for marketing. Read our full privacy notice.
Scenario 3: Contact Form / Support Request
Collection point: Contact us / support form Data collected: Name, email, company, message content Purpose: Responding to enquiry
Just-in-time notice text:
Meridian Analytics Ltd will use the details you provide to respond to your enquiry. We will retain your message for 3 years to maintain service quality. Read our full privacy notice.
Scenario 4: Event Registration
Collection point: Event/webinar registration form Data collected: Name, email, company, dietary requirements (if in-person) Purpose: Event management and follow-up
Just-in-time notice text:
Meridian Analytics Ltd will use your details to manage your event registration and send you event-related communications. If you provide dietary requirements, this information will be processed under your explicit consent and shared only with the catering provider for this event. Read our full privacy notice.
Compliance Checklist
For every new data collection point, verify:
- Art. 13(1)(a): Controller name and contact details displayed
- Art. 13(1)(b): DPO contact details accessible (directly or via link to full notice)
- Art. 13(1)(c): Each purpose and legal basis stated
- Art. 13(1)(d): Legitimate interests specified (if Art. 6(1)(f) relied upon)
- Art. 13(1)(e): Recipients identified (directly or via link to full notice)
- Art. 13(1)(f): International transfer information provided (if applicable)
- Art. 13(2)(a): Retention period or criteria stated
- Art. 13(2)(b): Data subject rights listed with exercise mechanism
- Art. 13(2)(c): Right to withdraw consent stated (if consent-based)
- Art. 13(2)(d): Right to complain to ICO stated
- Art. 13(2)(e): Whether provision is required and consequences of non-provision
- Art. 13(2)(f): Automated decision-making disclosure (if applicable)
- Information provided at or before the moment of collection
- Layered approach: just-in-time notice + link to full notice
- Language is clear, plain, and appropriate for the audience
- Notice is visible without requiring additional clicks or scrolling
© 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/direct-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
Direct 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 |
|---|---|---|---|---|---|---|
| Direct Collection Notice this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.2k | 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 Direct Collection Notice
What does Direct Collection Notice do?
Provides GDPR Article 13 information at the point of direct data collection, covering all required elements under Art. Direct Collection Notice is an agent skill from mukul975/Privacy-Data-Protection-Skills. Provides GDPR Article 13 information at the point of direct data collection, covering all required elements under Art.
When should I use Direct Collection Notice?
Direct Collection Notice fits situations like: tasks that involve Privacy and GDPR.
How do I install Direct Collection Notice in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill direct-collection-notice -a claude-code`. Or copy the skill folder (skills/privacy/direct-collection-notice in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/direct-collection-notice in your project. Claude Code loads it when a task matches its description.
How do I install Direct Collection Notice in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill direct-collection-notice -a codex`. Or copy the skill folder (skills/privacy/direct-collection-notice in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/direct-collection-notice in your project. Codex loads it when a task matches its description.
Can I use Direct 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 direct-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/direct-collection-notice, .gemini/skills/direct-collection-notice, .github/skills/direct-collection-notice and .opencode/skills/direct-collection-notice in your project.
What does Direct Collection Notice need to run?
Going by SKILL.md and its folder, Direct Collection Notice needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Direct 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 Direct 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 Direct Collection Notice use?
Direct 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 Direct Collection Notice use?
About 2.2k tokens (SKILL.md is roughly 8.9k 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.4k tokens, read only when the agent opens those files.
What are the alternatives to Direct Collection Notice?
Skills that share tags, products or a category with Direct 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 Direct 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.