C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Guides implementation of the NIST Privacy Framework IDENTIFY function covering ID.BE business environment, ID.DA data actions, ID.IM improvement, and ID.RA risk assessment subcategories.
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-privacy-identify -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-privacy-identify --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/nist-privacy-identify .claude/skills/nist-privacy-identify && 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 "nist-privacy-identify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-privacy-identify into .claude/skills/nist-privacy-identify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-privacy-identify", 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/nist-privacy-identifyType 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 nist-privacy-identify -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-privacy-identify --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/nist-privacy-identify .agents/skills/nist-privacy-identify && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nist-privacy-identify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-privacy-identify into .agents/skills/nist-privacy-identify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-privacy-identify", 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 nist-privacy-identify -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-privacy-identify --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/nist-privacy-identify .cursor/skills/nist-privacy-identify && 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 "nist-privacy-identify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-privacy-identify into .cursor/skills/nist-privacy-identify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-privacy-identify", 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/nist-privacy-identify--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 nist-privacy-identify -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-privacy-identify --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/nist-privacy-identify .gemini/skills/nist-privacy-identify && 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 "nist-privacy-identify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-privacy-identify into .gemini/skills/nist-privacy-identify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-privacy-identify", 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 nist-privacy-identifyInstalls 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 nist-privacy-identify -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/nist-privacy-identify .github/skills/nist-privacy-identify && 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 "nist-privacy-identify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-privacy-identify into .github/skills/nist-privacy-identify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-privacy-identify", 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 nist-privacy-identify -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 nist-privacy-identify --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/nist-privacy-identify .opencode/skills/nist-privacy-identify && 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 "nist-privacy-identify" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-privacy-identify into .opencode/skills/nist-privacy-identify/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-privacy-identify", 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.
nist-privacy-identifyGuides implementation of the NIST Privacy Framework IDENTIFY function covering ID.BE business environment, ID.DA data actions, ID.IM improvement, and ID.RA risk assessment subcategories.
Nist Privacy Identify is an agent skill from mukul975/Privacy-Data-Protection-Skills. Guides implementation of the NIST Privacy Framework IDENTIFY function covering ID.BE business environment, ID.DA data actions, ID.IM improvement, and ID.RA risk assessment subcategories. Maps NIST PF controls to GDPR requirements for dual-framework compliance. Keywords: NIST Privacy Framework, IDENTIFY function, ID.BE, ID.DA, ID.IM, ID.RA, privacy risk assessment, data actions.
Its SKILL.md is about 2.3k 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.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 9b2ef9e. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Nist Privacy Identify loads about 2.3k tokens when it runs, and up to ~2.7k if it reads all its reference files. Until then it costs about 101 tokens; SKILL.md has 1,013 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.
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.
The full file from mukul975/Privacy-Data-Protection-Skills at commit 9b2ef9e, republished under its Apache-2.0 licence (© mukul975). 1,013 words, ~2,327 tokens.
.claude/skills/nist-privacy-identify/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.The NIST Privacy Framework Version 1.0 (January 2020) provides a voluntary enterprise risk management tool structured around five core functions: IDENTIFY, GOVERN, CONTROL, COMMUNICATE, and PROTECT. The IDENTIFY function develops the organisational understanding to manage privacy risk arising from data processing. This skill covers the four IDENTIFY subcategories: Inventory and Mapping (ID.IM), Business Environment (ID.BE), Risk Assessment (ID.RA), and Data Processing Ecosystem Risk Management (ID.DE).
Data processing inventory and mapping activities are understood by the organisation.
| Subcategory | Description | Implementation |
|---|---|---|
| ID.IM-P1 | Systems/products/services that process data are inventoried | Maintain a comprehensive register of all systems processing personal data, including SaaS tools, internal databases, and third-party integrations |
| ID.IM-P2 | Owners of systems/products/services are identified | Assign a data processing owner to each system with documented responsibility for privacy compliance |
| ID.IM-P3 | Categories of individuals whose data are processed are inventoried | Map all data subject categories (employees, customers, patients, vendors, website visitors) |
| ID.IM-P4 | Data actions of the systems/products/services are inventoried | Document data lifecycle actions: collection, retention, logging, generation, transformation, use, disclosure, sharing, transmission, disposal |
| ID.IM-P5 | Purposes for data actions are inventoried | Document specific purposes for each data action, aligned with GDPR Art. 5(1)(b) purpose limitation |
| ID.IM-P6 | Data elements within the data actions are inventoried | Catalogue all personal data elements processed per system and per purpose |
| ID.IM-P7 | Environmental factors affecting the data processing ecosystem are understood | Assess external factors: legal/regulatory requirements, industry standards, market expectations, organisational risk tolerance |
| ID.IM-P8 | Data processing is mapped | Create and maintain data flow maps showing how personal data moves through the organisation |
The organisation's mission, objectives, stakeholders, and activities are understood and prioritised.
| Subcategory | Description | Implementation |
|---|---|---|
| ID.BE-P1 | The organisation's role in the data processing ecosystem is identified and communicated | Determine controller/processor/joint controller status for each processing activity |
| ID.BE-P2 | Priorities for organisational mission, objectives, and activities are established and communicated | Align privacy programme with business objectives; ensure privacy is a design requirement |
| ID.BE-P3 | Systems/products/services that support organisational priorities are identified and key requirements communicated | Identify which processing activities are critical to business operations and prioritise privacy investment accordingly |
The organisation understands the privacy risks to individuals and how such processing creates privacy risks to the organisation.
| Subcategory | Description | Implementation |
|---|---|---|
| ID.RA-P1 | Contextual factors related to the systems/products/services and data actions are identified | Assess context: relationship with data subjects, data subject expectations, sensitivity, volume, collection method |
| ID.RA-P2 | Data analytic inputs and outputs are identified and evaluated | For data analytics and AI, identify inputs (training data, inference data) and outputs (predictions, scores, decisions) |
| ID.RA-P3 | Potential problems for individuals that arise from data processing are identified | Identify privacy harms: loss of autonomy, discrimination, economic loss, physical harm, reputational damage, loss of trust |
| ID.RA-P4 | Problematic data actions, the likelihood that they occur, and the resulting problems for individuals are identified and assessed | Assess likelihood and severity of each problematic data action — aligned with GDPR DPIA risk assessment |
| ID.RA-P5 | Risk responses are identified and prioritised | For each identified risk, determine response: mitigate, transfer, avoid, accept |
The organisation identifies, assesses, and manages privacy risks associated with data processing by third parties.
| Subcategory | Description | Implementation |
|---|---|---|
| ID.DE-P1 | Data processing ecosystem risk management policies, processes, and procedures are identified, established, assessed, and managed | Vendor privacy management programme with due diligence, contractual requirements, and ongoing monitoring |
| ID.DE-P2 | Data processing ecosystem parties are identified, prioritised, and assessed | Map all processors, sub-processors, and third-party recipients with risk rating |
| ID.DE-P3 | Contracts with data processing ecosystem parties are established, maintained, and managed | Art. 28 DPAs with all processors; joint controller arrangements per Art. 26 |
| ID.DE-P4 | Interoperability frameworks or mechanisms are established for data processing ecosystem parties | Standard data formats, APIs, and privacy-preserving data exchange protocols |
| ID.DE-P5 | Data processing ecosystem parties are managed consistent with the organisation's risk strategy | Ongoing processor performance monitoring, audit rights exercise, sub-processor change management |
| NIST PF Subcategory | GDPR Equivalent | Implementation Overlap |
|---|---|---|
| ID.IM-P1 through P8 | Art. 30 Records of Processing Activities | RoPA fulfils the core inventory and mapping requirements |
| ID.BE-P1 | Art. 26 Joint Controllers, Art. 28 Processors | Role determination aligns directly |
| ID.RA-P1 through P5 | Art. 35 DPIA | DPIA risk assessment methodology maps to NIST risk assessment |
| ID.DE-P1 through P5 | Art. 28 Processor Requirements | Processor governance maps to ecosystem risk management |
While the NIST Privacy Framework is voluntary and not directly enforceable, organisations demonstrating NIST PF implementation show a mature privacy programme that can support GDPR accountability under Art. 5(2) and Art. 24. US state privacy laws (California CPRA, Virginia VCDPA, Colorado CPA) increasingly reference the NIST PF as a compliance resource.
© 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
SKILL.md and 4 other files (scripts, references, assets) in skills/privacy/nist-privacy-identify of mukul975/Privacy-Data-Protection-Skills.
Open the folder on GitHubat commit 9b2ef9e
Nist Privacy Identify 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 |
|---|---|---|---|---|---|---|
| Nist Privacy Identify this skillmukul975/Privacy-Data-Protection-Skills | 301 | — | ~2.3k | 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 |
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
maziyarpanahi/openmed
Checks OpenMed de-identified clinical text against the 18 HIPAA Safe Harbor identifier categories and reports gaps and residual re-identification risk.
kimlawtech/korean-privacy-terms
처리방침·이용약관 자동 생성 스킬 패키지 (v4.0). An agent skill from kimlawtech/korean-privacy-terms.
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…
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
gregmos/PII-Shield
Universal legal document processor with PII anonymization. An agent skill from gregmos/PII-Shield.
mukul975/Privacy-Data-Protection-Skills
Implements age-gating mechanisms for online services to restrict access based on user age.
mukul975/Privacy-Data-Protection-Skills
Manages AI model retention and machine unlearning requirements.
mukul975/Privacy-Data-Protection-Skills
Conducts Data Protection Impact Assessments for AI and ML systems per EDPB Guidelines 04/2025 on AI processing.
mukul975/Privacy-Data-Protection-Skills
Structures risk mitigation planning and residual risk tracking for Data Protection Impact Assessments under GDPR Article 35(7)(d).
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.
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.
Categories
Guides implementation of the NIST Privacy Framework IDENTIFY function covering ID.BE business environment, ID.DA data actions, ID.IM improvement, and ID.RA risk assessment subcategories. Nist Privacy Identify is an agent skill from mukul975/Privacy-Data-Protection-Skills.RA risk assessment subcategories.
Nist Privacy Identify fits situations like: tasks that involve Privacy and GDPR.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-privacy-identify -a claude-code`. Or copy the skill folder (skills/privacy/nist-privacy-identify in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/nist-privacy-identify in your project. Claude Code loads it when a task matches its description.
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-privacy-identify -a codex`. Or copy the skill folder (skills/privacy/nist-privacy-identify in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/nist-privacy-identify in your project. Codex loads it when a task matches its description.
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 nist-privacy-identify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nist-privacy-identify, .gemini/skills/nist-privacy-identify, .github/skills/nist-privacy-identify and .opencode/skills/nist-privacy-identify in your project.
Going by SKILL.md and its folder, Nist Privacy Identify needs Python for the scripts in its folder. Our summary lists: Python 3.
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.
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.
Nist Privacy Identify 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.
About 2.3k tokens (SKILL.md is roughly 9.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 415 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Nist Privacy Identify: 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.
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.