Agent skill

Configuring Privacy Policies

by maziyarpanahi in maziyarpanahi/openmed

Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators.

Apache-2.0Auto-check passedLegal & Compliance

Install Configuring Privacy Policies

skills CLI

$ npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a claude-code

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

GitHub CLI

$ gh skill install maziyarpanahi/openmed configuring-privacy-policies --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/configuring-privacy-policies .claude/skills/configuring-privacy-policies && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "configuring-privacy-policies" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies into .claude/skills/configuring-privacy-policies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuring-privacy-policies", 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

$skill-installer install https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies

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

skills CLI

$ npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed configuring-privacy-policies --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/configuring-privacy-policies .agents/skills/configuring-privacy-policies && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "configuring-privacy-policies" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies into .agents/skills/configuring-privacy-policies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuring-privacy-policies", 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.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed configuring-privacy-policies --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/configuring-privacy-policies .cursor/skills/configuring-privacy-policies && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "configuring-privacy-policies" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies into .cursor/skills/configuring-privacy-policies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuring-privacy-policies", 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

$ gemini skills install https://github.com/maziyarpanahi/openmed.git --path skills/configuring-privacy-policies

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed configuring-privacy-policies --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/configuring-privacy-policies .gemini/skills/configuring-privacy-policies && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "configuring-privacy-policies" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies into .gemini/skills/configuring-privacy-policies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuring-privacy-policies", 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.

GitHub CLI

$ gh skill install maziyarpanahi/openmed configuring-privacy-policies

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

skills CLI

$ npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/configuring-privacy-policies .github/skills/configuring-privacy-policies && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "configuring-privacy-policies" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies into .github/skills/configuring-privacy-policies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuring-privacy-policies", 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.

skills CLI

$ npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install maziyarpanahi/openmed configuring-privacy-policies --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/maziyarpanahi/openmed.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/configuring-privacy-policies .opencode/skills/configuring-privacy-policies && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "configuring-privacy-policies" agent skill from https://github.com/maziyarpanahi/openmed/tree/master/skills/configuring-privacy-policies into .opencode/skills/configuring-privacy-policies/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configuring-privacy-policies", 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: configuring-privacy-policies
GitHub stars: 5.5k
Token cost: ~2.1k tokens
SKILL.md length: 638 words
Files: 1
Skills in repo: 74
Repo updated: Oct 11, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators.

The user asks which policy fits HIPAA Safe Harbor vs Expert Determination vs GDPR vs PIPEDA vs a research limited dataset vs strict no-leak
SKILL.md covers When to use this skill, Quick start, The seven bundled profiles and Choosing: map regulation →…, plus 4 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
Wants to pass policy= to deidentify()

What it does

Configuring Privacy Policies is an agent skill from maziyarpanahi/openmed. Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators. Use when the user asks which policy fits HIPAA Safe Harbor vs Expert Determination vs GDPR vs PIPEDA vs a research limited dataset vs strict no-leak, wants to pass policy= to deidentify(), needs to keep quasi-identifiers for research, or must register a custom MRN/name/address surrogate provider. Covers the profile-to-use-case map, AnonymizerConfig/Anonymizer for fine control, and…

Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Legal & Compliance, covering Privacy and GDPR and Healthcare and finance regulation. The repository describes itself as: Local-first healthcare AI: clinical NER and HIPAA PII de-identification on hardware you control. 2,200+ medical models, 35 model-backed PII languages, and Python, MLX, Android… The licence is Apache-2.0.

When your agent uses it

The user asks which policy fits HIPAA Safe Harbor vs Expert Determination vs GDPR vs PIPEDA vs a research limited dataset vs strict no-leak
Wants to pass policy= to deidentify()
Needs to keep quasi-identifiers for research
Must register a custom MRN/name/address surrogate provider

Example prompts

“/configuring-privacy-policies”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 34d7b8c. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
- hhs.gov
- priv.gc.ca
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

Configuring Privacy Policies loads about 2.1k tokens when it runs. Until then it costs about 171 tokens; SKILL.md has 638 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~171
When it runs · the whole SKILL.md, loaded when a task matches: ~2.1k

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); files beside SKILL.md are not scanned.

SKILL.md

The full file from maziyarpanahi/openmed at commit 34d7b8c, republished under its Apache-2.0 licence (© maziyarpanahi). 638 words, ~2,126 tokens.

Download SKILL.mdSave it as .claude/skills/configuring-privacy-policies/SKILL.md (or your agent's skills folder).

name: configuring-privacy-policies
description: Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators. Use when the user asks which policy fits HIPAA Safe Harbor vs Expert Determination vs GDPR vs PIPEDA vs a research limited dataset vs strict no-leak, wants to pass policy= to deidentify(), needs to keep quasi-identifiers for research, or must register a custom MRN/name/address surrogate provider. Covers the profile-to-use-case map, AnonymizerConfig/Anonymizer for fine control, and register_clinical_provider / register_label_generator. Pairs with OpenMed deidentifying-clinical-text and generating-synthetic-surrogates.
license: Apache-2.0
metadata.project: OpenMed
metadata.category: de-identification
metadata.pairs: adjacent
metadata.version: 1.0

Configuring privacy policies

A policy profile is a named bundle of de-identification decisions: which action (mask/redact/replace/keep) applies to each label, how aggressively detectors arbitrate, whether the mandatory safety sweep runs, and whether a reversible mapping is produced. OpenMed ships seven profiles. Pass one by name to deidentify(policy=...) and you get a compliance-aligned default without hand-wiring 50+ per-label actions. Everything runs on-device.

When to use this skill

Use it to pick the right policy= for a regulatory context, to understand what a profile actually changes, or to go beyond the bundle — keeping quasi- identifiers for research, or registering a custom surrogate generator (e.g. your own MRN format).

Quick start

python

import openmed

note = "Jane Roe, DOB 1979-04-11, lives in Cambridge MA 02139. SSN 123-45-6789."

# HIPAA Safe Harbor: mask every identifier class.
safe = openmed.deidentify(note, policy="hipaa_safe_harbor")

# GDPR pseudonymization: replace with fakes AND keep a reversible mapping.
gdpr = openmed.deidentify(note, policy="gdpr_pseudonymization")
mapping = gdpr.mapping          # present because the profile sets keep_mapping=True

# Research limited dataset: mask direct identifiers, KEEP quasi-identifiers
# (dates, age, ZIP, geography) so the data stays analytically useful.
lds = openmed.deidentify(note, policy="research_limited_dataset")

The seven bundled profiles

Each profile lives in openmed/core/policies/<name>.json. Summary of what each actually configures:

Profile	Default action	Quasi-identifiers	Mapping	Safety sweep	Use case
`hipaa_safe_harbor`	mask all	masked	none	mandatory	HIPAA §164.514(b)(2) Safe Harbor — strip all 18 identifier classes
`hipaa_expert_review_assist`	redact	redacted; clinical concepts kept	none	optional	Assist Expert Determination (§164.514(b)(1)); keeps microbiology/clinical terms for a statistician to assess residual risk
`gdpr_pseudonymization`	replace	replaced; clinical kept	kept + reversible	mandatory	GDPR Art. 4(5) pseudonymization — reversible under controlled key
`canada_pipeda`	replace (IDs masked)	replaced	kept + reversible	mandatory	PIPEDA-aligned; like GDPR but masks ID_NUM/SSN outright
`research_limited_dataset`	mask direct ids	keeps dates, age, ZIP, geography, org, job	none	mandatory	HIPAA Limited Data Set (§164.514(e)) — usable for research with a DUA
`clinical_minimal_redaction`	mask direct ids	keeps quasi-identifiers	none	optional	Internal clinical use where readability matters; lighter cascade
`strict_no_leak`	mask everything	masked; even clinical concepts masked	none	mandatory	Maximum-recall, union arbitration, all cascade tiers — zero-leakage posture

Key dimensions to reason about:

default_action — mask ([NAME]), redact, replace (fake value), or keep. Set per label in the profile's actions map.
policy_label_actions — coarse action by class: DIRECT_IDENTIFIER / QUASI_IDENTIFIER / CLINICAL_CONCEPT. Research and minimal-redaction profiles keep quasi-identifiers; strict-no-leak masks even clinical concepts.
keep_mapping / reversible_id — only GDPR and PIPEDA produce a reversible mapping. Treat that mapping as PHI.
safety_sweep_mandatory — deterministic structured-ID sweep (SSN, MRN- like, emails) that runs regardless of model confidence. Off only for the two "minimal/assist" profiles.
arbitration_mode / forced_cascade_tiers — strict_no_leak uses high_recall_union across tiers R0–R3 (most aggressive); minimal redaction uses only R0–R1.

Choosing: map regulation → profile

Publish or share data with no DUA, US → hipaa_safe_harbor.
Statistician will certify low risk (keep clinical signal) → hipaa_expert_review_assist, then human Expert Determination.
EU subjects, need reversibility under a key → gdpr_pseudonymization.
Canadian subjects → canada_pipeda.
Research cohort needing dates/age/geography → research_limited_dataset (requires a Data Use Agreement).
Internal clinical workflow, readability first → clinical_minimal_redaction.
Adversarial / zero-tolerance leakage → strict_no_leak.

Show full SKILL.md (231 more words)Show less

Customizing beyond the bundle

When a profile is close but not exact, drive the engine directly with Anonymizer / AnonymizerConfig, or register custom generators.

python

from openmed import (
    Anonymizer, AnonymizerConfig,
    register_label_generator, register_clinical_provider,
)

# 1) Per-instance config (language, locale, deterministic surrogates):
anon = Anonymizer(AnonymizerConfig(lang="en", consistent=True, seed=7))
fake_name = anon.surrogate("John Doe", "PERSON")     # type-matched surrogate

# 2) Override the surrogate for one canonical label (e.g. your MRN format).
#    Generators take (faker, original, *, locale) and return a string.
def hospital_mrn(faker, original, *, locale):
    return f"H{faker.numerify('#######')}"

register_label_generator("ID_NUM", hospital_mrn)     # global, all new Anonymizers

# 3) Add a custom Faker provider (e.g. proprietary identifier formats).
register_clinical_provider(MyClinicalProvider)        # a faker BaseProvider class

Use register_label_generator(canonical_label, fn) to swap one label's surrogate; use register_clinical_provider(provider) to add whole Faker providers. For per-call scoping, pass providers via AnonymizerConfig.custom_providers instead of the global registry. Validate custom labels against openmed.CANONICAL_LABELS.

Hand-off to / from OpenMed

Apply a policy: openmed.deidentify(text, policy="<name>") — see deidentifying-clinical-text.
Surrogate strategy: generating-synthetic-surrogates for method="replace" with consistent/seed/locale and custom providers.
Verify coverage: auditing-deidentification-runs (audit=True) and auditing-safe-harbor-checklist (18 identifier categories).
Other surfaces: MCP openmed_deidentify and REST POST /pii/deidentify accept the same policy argument.

Edge cases & gotchas

Profiles are configuration, not a guarantee. A profile that keeps quasi- identifiers (research/minimal) does not meet Safe Harbor — pair it with a Data Use Agreement or Expert Determination.
Reversible profiles produce a re-identifying mapping. GDPR/PIPEDA mappings are as sensitive as the raw PHI; store them encrypted and separately.
register_label_generator is global and persists for the process. It mutates a shared registry; prefer AnonymizerConfig.custom_providers for isolated, per-run behavior.
Surrogates must not collide with real values. Keep generated identifiers out of the real ID space; see generating-synthetic-surrogates.
Permissive licensing only. Do not bundle UMLS/SNOMED/CPT/MIMIC/i2b2/n2c2 into custom providers; call restricted terminologies out-of-process.

Standards & references

HIPAA de-identification, 45 CFR 164.514(b): https://www.hhs.gov/hipaa/for-professionals/privacy/special-topics/de-identification/index.html
HIPAA Limited Data Set, 45 CFR 164.514(e).
GDPR pseudonymization, Regulation (EU) 2016/679 Art. 4(5) & Art. 25.
PIPEDA (Canada): https://www.priv.gc.ca/en/privacy-topics/privacy-laws-in-canada/the-personal-information-protection-and-electronic-documents-act-pipeda/
OpenMed source: openmed/core/policies/*.json, openmed/core/anonymizer/.

Files

Just SKILL.md in skills/configuring-privacy-policies of maziyarpanahi/openmed.

Open the folder on GitHubat commit 34d7b8c

Compare with similar skills

Configuring Privacy Policies 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.

Configuring Privacy Policies compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Configuring Privacy Policies this skillmaziyarpanahi/openmed	5.5k	—	~2.1k	Automated safety check: Pass	Apache-2.0	today
Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance	946	1 repos	~2.3k	Automated safety check: Pass	MIT	yesterday
Audit Reportharness/harness-skills	115	—	~1.3k	Automated safety check: Pass	Apache-2.0	4 days ago
Anne WojcickiK-Dense-AI/mimeographs	129	—	~1.5k	Automated safety check: Pass	MIT	1 mo ago
Dpa Checklist ReviewLegalQuants/lq-ai	150	—	~3.7k	Automated safety check: Pass	Apache-2.0	today
Healthcare Phi Complianceaffaan-m/ECC	277k	1 repos	~1.4k	Automated safety check: Pass	MIT	today

Similar skills

Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
946 GitHub starsUsed in 1 repo~2.3k tokens
Legal & ComplianceAuto-check passed
Audit Report
harness/harness-skills
Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.
115 GitHub stars~1.3k tokensUpdated 4 days ago
Legal & ComplianceAuto-check passed
Anne Wojcicki
K-Dense-AI/mimeographs
Applies the strategic frameworks and mental models of Anne Wojcicki, co-founder and CEO of 23andMe.
129 GitHub stars~1.5k tokensUpdated 1 mo ago
Legal & ComplianceAuto-check passed
Dpa Checklist Review
LegalQuants/lq-ai
A skill your agent uses when the user provides a Data Processing Agreement, Data Processing Addendum, or HIPAA Business Associate Agreement and asks whether it contains the terms required under the…
150 GitHub stars~3.7k tokensUpdated today
Legal & ComplianceAuto-check passed
Healthcare Phi Compliance
affaan-m/ECC
Protected Health Information (PHI) and PII compliance patterns for healthcare applications: data classification, row-level access control, tamper-proof audit trails, schema tagging, and common leak…
277k GitHub starsUsed in 1 repo~1.4k tokens
Legal & ComplianceAuto-check passed
Security Compliance
sangrokjung/claude-forge
Guides security professionals in implementing defense-in-depth security architectures, achieving compliance with industry frameworks (SOC2, ISO27001, GDPR, HIPAA), conducting threat modeling and…
852 GitHub starsUsed in 2 repos~7.2k tokens
Legal & ComplianceAuto-check passed

Questions about Configuring Privacy Policies

What does Configuring Privacy Policies do?

Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators. Configuring Privacy Policies is an agent skill from maziyarpanahi/openmed. Select and customize OpenMed's seven bundled privacy policy profiles for de-identification, and build custom surrogate generators.

When should I use Configuring Privacy Policies?

Configuring Privacy Policies fits situations like: the user asks which policy fits HIPAA Safe Harbor vs Expert Determination vs GDPR vs PIPEDA vs a research limited dataset vs strict no-leak; wants to pass policy= to deidentify(); needs to keep quasi-identifiers for research; must register a custom MRN/name/address surrogate provider.

How do I install Configuring Privacy Policies in Claude Code?

Run `npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a claude-code`. Or copy the skill folder (skills/configuring-privacy-policies in maziyarpanahi/openmed) into .claude/skills/configuring-privacy-policies in your project. Claude Code loads it when a task matches its description.

How do I install Configuring Privacy Policies in Codex?

Run `npx skills add maziyarpanahi/openmed --skill configuring-privacy-policies -a codex`. Or copy the skill folder (skills/configuring-privacy-policies in maziyarpanahi/openmed) into .agents/skills/configuring-privacy-policies in your project. Codex loads it when a task matches its description.

Can I use Configuring Privacy Policies 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 maziyarpanahi/openmed --skill configuring-privacy-policies -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configuring-privacy-policies, .gemini/skills/configuring-privacy-policies, .github/skills/configuring-privacy-policies and .opencode/skills/configuring-privacy-policies in your project.

What does Configuring Privacy Policies need to run?

SKILL.md names no scripts, command-line tools or credentials: Configuring Privacy Policies is instructions for the agent only. Our summary lists: Python 3.

Does Configuring Privacy Policies access the network?

SKILL.md names 2 domains. As links in the text: hhs.gov and priv.gc.ca. This is read from the text; nothing was executed.

Is Configuring Privacy Policies 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. Review the folder before installing.

What licence does Configuring Privacy Policies use?

Configuring Privacy Policies 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 Configuring Privacy Policies use?

About 2.1k tokens (SKILL.md is roughly 8.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Configuring Privacy Policies?

Skills that share tags, products or a category with Configuring Privacy Policies: Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars), Audit Report (harness/harness-skills, 115 stars), Anne Wojcicki (K-Dense-AI/mimeographs, 129 stars) and Dpa Checklist Review (LegalQuants/lq-ai, 150 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Configuring Privacy Policies?

maziyarpanahi (a GitHub user) maintains it in maziyarpanahi/openmed, which has 5,506 GitHub stars. The repository holds 74 skills in this directory. The repository was last updated on October 11, 2026.

Source: maziyarpanahi/openmed on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Configuring Privacy Policies

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Configuring privacy policies

When to use this skill

Quick start

The seven bundled profiles

Choosing: map regulation → profile

Customizing beyond the bundle

Hand-off to / from OpenMed

Edge cases & gotchas

Standards & references

Files

Compare with similar skills

Similar skills

More from maziyarpanahi/openmed

Related

Questions about Configuring Privacy Policies