C15t
c15t/c15t
Work with c15t consent management docs, APIs, and integrations for Next.js, React, and JavaScript.
Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies.
Install Nist Pf Communicate
$ npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-communicate -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-communicate --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-pf-communicate .claude/skills/nist-pf-communicate && 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-pf-communicate" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-communicate into .claude/skills/nist-pf-communicate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-communicate", 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-pf-communicateType 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-pf-communicate -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-communicate --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-pf-communicate .agents/skills/nist-pf-communicate && 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-pf-communicate" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-communicate into .agents/skills/nist-pf-communicate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-communicate", 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-pf-communicate -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-communicate --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-pf-communicate .cursor/skills/nist-pf-communicate && 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-pf-communicate" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-communicate into .cursor/skills/nist-pf-communicate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-communicate", 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-pf-communicate--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-pf-communicate -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Privacy-Data-Protection-Skills nist-pf-communicate --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-pf-communicate .gemini/skills/nist-pf-communicate && 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-pf-communicate" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-communicate into .gemini/skills/nist-pf-communicate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-communicate", 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-pf-communicateInstalls 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-pf-communicate -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-pf-communicate .github/skills/nist-pf-communicate && 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-pf-communicate" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-communicate into .github/skills/nist-pf-communicate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-communicate", 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-pf-communicate -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-pf-communicate --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-pf-communicate .opencode/skills/nist-pf-communicate && 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-pf-communicate" agent skill from https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/skills/privacy/nist-pf-communicate into .opencode/skills/nist-pf-communicate/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nist-pf-communicate", 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
nist-pf-communicate- GitHub stars
- 301
- Token cost
- ~2.3k tokens
- SKILL.md length
- 836 words
- Files
- 5 (incl. scripts, references, assets)
- Skills in repo
- 280
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies.
- Works in 7 steps: How aware are you of our privacy… → How easy is it to find information about… → How confident are you that we protect… → …
- Tasks that involve Privacy and GDPR
- SKILL.md covers Overview, COMMUNICATE Function…, Transparency Framework and Privacy Notice Content…, plus 4 more sections
- Runs Python scripts from its folder
What it does
Nist Pf Communicate is an agent skill from mukul975/Privacy-Data-Protection-Skills. Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies. Provides transparency mechanisms, stakeholder engagement frameworks, privacy notice templates, and communication workflow guidance.
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.
When your agent uses it
- Tasks that involve Privacy and GDPR
Example prompts
- “/nist-pf-communicate”
Requirements
- Python 3
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- How aware are you of our privacy practices? (1-5 scale)
- How easy is it to find information about how we use your data? (1-5 scale)
- How confident are you that we protect your personal data? (1-5 scale)
- Have you exercised any privacy rights in the past 12 months? (Yes/No, which ones)
- How satisfied were you with the response? (1-5 scale, if applicable)
- What privacy improvements would you like to see? (Open text)
- How likely are you to recommend us based on our privacy practices? (0-10 NPS)
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
Nist Pf Communicate loads about 2.3k tokens when it runs, and up to ~3.1k if it reads all its reference files. Until then it costs about 69 tokens; SKILL.md has 836 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). 836 words, ~2,313 tokens.
Download SKILL.mdSave it as
.claude/skills/nist-pf-communicate/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- nist-pf-communicate
- description
- Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies. Provides transparency mechanisms, stakeholder engagement frameworks, privacy notice templates, and communication workflow guidance.
- license
- Apache-2.0
- metadata.author
- mukul975
- metadata.version
- 1.0
- metadata.domain
- privacy
- metadata.subdomain
- privacy-engineering
- metadata.tags
- nist-privacy-framework, communicate-function, privacy-transparency, stakeholder-engagement, privacy-notices
NIST Privacy Framework — COMMUNICATE Function
Overview
The COMMUNICATE function develops and implements appropriate activities to enable organizations and individuals to have a reliable understanding and engage in a dialogue about how data are processed and associated privacy risks. This function is essential for building trust and ensuring transparency with data subjects, regulators, and business partners.
COMMUNICATE Function Subcategories
CM.AW — Awareness
Raising awareness of data processing practices and privacy risks among stakeholders.
| Subcategory | Description | Implementation Guidance |
|---|---|---|
| CM.AW-P1 | Mechanisms (e.g., notices, internal policies) for communicating data processing purposes, practices, and associated privacy risks are established and in service | Publish layered privacy notices. Maintain internal data processing documentation. Establish communication channels for privacy inquiries. |
| CM.AW-P2 | Mechanisms for obtaining feedback from individuals about data processing and associated privacy risks are established and in service | Deploy feedback forms on privacy pages. Monitor privacy-related inquiries through support channels. Conduct periodic privacy perception surveys. |
| CM.AW-P3 | System/product/service design enables data processing visibility | Implement privacy dashboards for data subjects. Provide real-time data processing status. Enable granular consent visibility. |
| CM.AW-P4 | Records of data disclosures and sharing are maintained and can be accessed for review or transmission | Maintain disclosure registers. Enable data subjects to view sharing history. Automate disclosure logging. |
| CM.AW-P5 | Data corrections or deletions can be communicated to individuals or organizations that have received the data | Implement downstream notification workflows. Track data recipients for correction propagation. Automate deletion verification across partners. |
| CM.AW-P6 | Data provenance and lineage are maintained and can be accessed for review or transmission | Document data origins and transformation history. Provide lineage visualization. Enable audit trail access for authorized parties. |
| CM.AW-P7 | Impacted individuals and organizations are notified about a privacy breach or event | Develop breach notification templates. Establish notification timelines per jurisdiction. Maintain contact information for notification delivery. |
| CM.AW-P8 | Individuals are provided with mitigation mechanisms for observed privacy risks | Offer identity protection services post-breach. Provide self-service privacy controls. Communicate available remediation options. |
CM.PO — Communication Policies
Policies governing how privacy-related information is communicated.
| Subcategory | Description | Implementation Guidance |
|---|---|---|
| CM.PO-P1 | Transparency policies, processes, and procedures for communicating data processing purposes, practices, associated privacy risks, and options for enabling data subjects' data processing preferences are established and in service | Develop layered transparency framework. Define communication standards for each audience. |
| CM.PO-P2 | Roles and responsibilities for communicating privacy-related information are established | Assign communications ownership. Define approval workflows for external privacy communications. |
Transparency Framework
Layered Privacy Notice Architecture
Layer 1: Short Notice (Banner/Summary)
├── Who we are
├── What data we collect
├── Key purposes
├── Core rights
└── Link to full notice
Layer 2: Full Privacy Notice
├── Detailed purposes and legal bases
├── Data categories and sources
├── Recipients and transfers
├── Retention periods
├── Complete rights information
├── Contact information
└── Links to supplementary notices
Layer 3: Supplementary Notices
├── Cookie Policy
├── Children's Privacy Notice
├── Employee Privacy Notice
├── Specific Service Notices
└── Jurisdiction-Specific Addenda
Layer 4: Just-in-Time Notices
├── Collection-point notifications
├── Consent requests with context
├── Purpose-specific explanations
└── Processing change notificationsCommunication Channel Matrix
| Audience | Channel | Frequency | Content Type | Owner |
|---|---|---|---|---|
| Data subjects (general) | Website privacy center | Continuous | Notices, policies, FAQs | Privacy Team |
| Data subjects (customers) | Email, in-app notifications | Event-driven | Consent changes, updates | Marketing + Privacy |
| Data subjects (employees) | Intranet, HR portal | Semi-annual + event | Employee privacy info | HR + Privacy |
| Regulators | Formal correspondence | As required | Compliance reports, notifications | Legal + DPO |
| Business partners | Contract addenda, portal | Annual + event | Processing terms, audit rights | Legal + Procurement |
| Board/executives | Dashboards, presentations | Quarterly | Risk reports, KPIs | CPO |
| Internal teams | Confluence, training | Monthly | Guidelines, best practices | Privacy Champions |
Privacy Notice Content Requirements
Show full SKILL.md (352 more words)Show less
Mandatory Elements by Regulation
| Element | GDPR Art. 13/14 | CCPA/CPRA | LGPD | PIPEDA |
|---|---|---|---|---|
| Controller identity | Required | Required | Required | Required |
| DPO contact | Required | N/A | Required (DPO equivalent) | N/A |
| Processing purposes | Required | Required | Required | Required |
| Legal basis | Required | N/A | Required | N/A |
| Data categories | Required | Required | Required | Required |
| Recipients | Required | Required | Required | Required |
| International transfers | Required | N/A | Required | Required |
| Retention periods | Required | Disclosed on request | Required | Required |
| Data subject rights | Required | Required | Required | Required |
| Right to complain | Required | N/A | Required | Required |
| Automated decision-making | Required | CPRA: Required | Required | N/A |
| Data source (indirect collection) | Required | Required | Required | Required |
| Sale/sharing opt-out | N/A | Required | N/A | N/A |
| Financial incentive terms | N/A | Required | N/A | N/A |
Stakeholder Engagement Workflows
Data Subject Inquiry Handling
Inquiry Received
|
v
Classify Inquiry Type
├── General Privacy Question → FAQ/Knowledge Base → Respond within 5 business days
├── Data Subject Request → Route to DSR Workflow → Respond within regulatory deadline
├── Complaint → Escalate to DPO → Investigate → Respond within 15 business days
├── Breach Inquiry → Route to Incident Team → Coordinate response
└── Consent Change → Process immediately → Confirm within 24 hoursPrivacy Communication Approval Workflow
| Communication Type | Drafting | Review | Approval | Distribution |
|---|---|---|---|---|
| Privacy policy update | Privacy Team | Legal | CPO + General Counsel | Web team |
| Breach notification | Incident Lead | Legal + DPO | CEO + General Counsel | Communications |
| Regulatory response | DPO | Legal | General Counsel | DPO |
| Marketing consent request | Marketing | Privacy Team | CPO | Marketing |
| Internal policy update | Privacy Team | Stakeholders | CPO | Internal comms |
Feedback Mechanisms
Privacy Perception Survey Template (Annual)
- How aware are you of our privacy practices? (1-5 scale)
- How easy is it to find information about how we use your data? (1-5 scale)
- How confident are you that we protect your personal data? (1-5 scale)
- Have you exercised any privacy rights in the past 12 months? (Yes/No, which ones)
- How satisfied were you with the response? (1-5 scale, if applicable)
- What privacy improvements would you like to see? (Open text)
- How likely are you to recommend us based on our privacy practices? (0-10 NPS)
Control Mapping
| NIST PF COMMUNICATE | ISO 27701 | GDPR Article | APEC CBPR |
|---|---|---|---|
| CM.AW-P1 | A.7.3.2 | Art. 12, 13, 14 | Principle 5 |
| CM.AW-P2 | A.7.3.8 | Art. 77 | Principle 9 |
| CM.AW-P3 | A.7.2.5 | Art. 12(1) | Principle 5 |
| CM.AW-P4 | A.7.5.3 | Art. 19 | Principle 7 |
| CM.AW-P7 | A.7.3.9 | Art. 34 | Principle 8 |
| CM.PO-P1 | A.7.3.2 | Art. 12 | Principle 5 |
| CM.PO-P2 | 5.3 | Art. 37-39 | Principle 9 |
References
- NIST Privacy Framework Version 1.0 (January 16, 2020)
- Article 29 Working Party WP260 — Guidelines on Transparency
- EDPB Guidelines 04/2022 on Calculation of Administrative Fines
- ISO/IEC 29100:2011 — Privacy Framework (Privacy Principles)
© 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/nist-pf-communicate 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
Nist Pf Communicate 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 Pf Communicate 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 |
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 Nist Pf Communicate
What does Nist Pf Communicate do?
Implement the NIST Privacy Framework COMMUNICATE function covering CM.AW awareness raising and CM.PO communication policies. Nist Pf Communicate is an agent skill from mukul975/Privacy-Data-Protection-Skills.PO communication policies.
When should I use Nist Pf Communicate?
Nist Pf Communicate fits situations like: tasks that involve Privacy and GDPR.
How do I install Nist Pf Communicate in Claude Code?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-communicate -a claude-code`. Or copy the skill folder (skills/privacy/nist-pf-communicate in mukul975/Privacy-Data-Protection-Skills) into .claude/skills/nist-pf-communicate in your project. Claude Code loads it when a task matches its description.
How do I install Nist Pf Communicate in Codex?
Run `npx skills add mukul975/Privacy-Data-Protection-Skills --skill nist-pf-communicate -a codex`. Or copy the skill folder (skills/privacy/nist-pf-communicate in mukul975/Privacy-Data-Protection-Skills) into .agents/skills/nist-pf-communicate in your project. Codex loads it when a task matches its description.
Can I use Nist Pf Communicate 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 nist-pf-communicate -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-pf-communicate, .gemini/skills/nist-pf-communicate, .github/skills/nist-pf-communicate and .opencode/skills/nist-pf-communicate in your project.
What does Nist Pf Communicate need to run?
Going by SKILL.md and its folder, Nist Pf Communicate needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Nist Pf Communicate 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 Nist Pf Communicate 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 Nist Pf Communicate use?
Nist Pf Communicate 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 Nist Pf Communicate use?
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 785 tokens, read only when the agent opens those files.
What are the alternatives to Nist Pf Communicate?
Skills that share tags, products or a category with Nist Pf Communicate: 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 Nist Pf Communicate?
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.