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.
Coordinate a PCI DSS penetration-testing and CDE-scoping readiness assessment across methodology, scope, segmentation, execution evidence, remediation, and retesting.
Install Assess Pci Dss Readiness
$ npx skills add cyberful/cyberful --skill assess-pci-dss-readiness -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cyberful/cyberful assess-pci-dss-readiness --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/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/assess-pci-dss-readiness .claude/skills/assess-pci-dss-readiness && 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 "assess-pci-dss-readiness" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readiness into .claude/skills/assess-pci-dss-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-pci-dss-readiness", 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/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readinessType 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 cyberful/cyberful --skill assess-pci-dss-readiness -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cyberful/cyberful assess-pci-dss-readiness --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .agents/skills && cp -r skills-src/cyberful/builtin/skills/assess-pci-dss-readiness .agents/skills/assess-pci-dss-readiness && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "assess-pci-dss-readiness" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readiness into .agents/skills/assess-pci-dss-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-pci-dss-readiness", 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 cyberful/cyberful --skill assess-pci-dss-readiness -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cyberful/cyberful assess-pci-dss-readiness --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/cyberful/builtin/skills/assess-pci-dss-readiness .cursor/skills/assess-pci-dss-readiness && 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 "assess-pci-dss-readiness" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readiness into .cursor/skills/assess-pci-dss-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-pci-dss-readiness", 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/cyberful/cyberful.git --path cyberful/builtin/skills/assess-pci-dss-readiness--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 cyberful/cyberful --skill assess-pci-dss-readiness -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cyberful/cyberful assess-pci-dss-readiness --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/cyberful/builtin/skills/assess-pci-dss-readiness .gemini/skills/assess-pci-dss-readiness && 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 "assess-pci-dss-readiness" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readiness into .gemini/skills/assess-pci-dss-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-pci-dss-readiness", 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 cyberful/cyberful assess-pci-dss-readinessInstalls 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 cyberful/cyberful --skill assess-pci-dss-readiness -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .github/skills && cp -r skills-src/cyberful/builtin/skills/assess-pci-dss-readiness .github/skills/assess-pci-dss-readiness && 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 "assess-pci-dss-readiness" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readiness into .github/skills/assess-pci-dss-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-pci-dss-readiness", 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 cyberful/cyberful --skill assess-pci-dss-readiness -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cyberful/cyberful assess-pci-dss-readiness --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/cyberful/builtin/skills/assess-pci-dss-readiness .opencode/skills/assess-pci-dss-readiness && 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 "assess-pci-dss-readiness" agent skill from https://github.com/cyberful/cyberful/tree/main/cyberful/builtin/skills/assess-pci-dss-readiness into .opencode/skills/assess-pci-dss-readiness/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "assess-pci-dss-readiness", 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
assess-pci-dss-readiness- GitHub stars
- 135
- Token cost
- ~895 tokens
- SKILL.md length
- 303 words
- Files
- 5 (incl. references, assets)
- Skills in repo
- 85
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Coordinate a PCI DSS penetration-testing and CDE-scoping readiness assessment across methodology, scope, segmentation, execution evidence, remediation, and retesting.
- Requirement 11.4 readiness
- SKILL.md covers Establish the assessment…, Route to specialist evidence, Maintain the readiness register and Authoritative anchors
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Do not use it as a full PCI DSS compliance assessment
What it does
Assess Pci Dss Readiness is an agent skill from cyberful/cyberful. Coordinate a PCI DSS penetration-testing and CDE-scoping readiness assessment across methodology, scope, segmentation, execution evidence, remediation, and retesting. Use for Requirement 11.4 readiness; do not use it as a full PCI DSS compliance assessment or attestation.
Its SKILL.md is about 900 tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files and assets (for example `agents/openai.yaml`, `assets/pci-readiness-register.schema.json` and `assets/pci-readiness-register.template.json`).
It sits in Legal & Compliance, covering Healthcare and finance regulation and Penetration testing. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.
When your agent uses it
- Requirement 11.4 readiness
- Do not use it as a full PCI DSS compliance assessment
Example prompts
- “/assess-pci-dss-readiness”
What it can do on your machine
Read from SKILL.md and the folder at commit ec598a6. 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.
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):
docs-prv.pcisecuritystandards.orgpcisecuritystandards.org
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
Assess Pci Dss Readiness loads about 895 tokens when it runs, and up to ~1.4k if it reads all its reference files. Until then it costs about 74 tokens; SKILL.md has 303 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); files beside SKILL.md are not scanned.
SKILL.md
The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 303 words, ~895 tokens.
Download SKILL.mdSave it as
.claude/skills/assess-pci-dss-readiness/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- assess-pci-dss-readiness
- description
- Coordinate a PCI DSS penetration-testing and CDE-scoping readiness assessment across methodology, scope, segmentation, execution evidence, remediation, and retesting. Use for Requirement 11.4 readiness; do not use it as a full PCI DSS compliance assessment or attestation.
- metadata.domain
- payment-security
- metadata.subdomain
- pci-dss-readiness
- metadata.triggers
- assess pci dss readiness, pci dss penetration testing readiness, pci dss 11.4 gap assessment, cde scope readiness review, pci segmentation evidence readiness…
- metadata.tags
- pci-dss, readiness, requirement-11.4, cde, gap-assessment, evidence
Assess PCI DSS Readiness
Coordinate readiness for PCI DSS CDE scoping and penetration-testing obligations. This package is a router and integration layer for Requirements 11.4 and 12.5.2; it is not a complete assessment of all PCI DSS requirements, a Report on Compliance, a Self-Assessment Questionnaire, an Attestation of Compliance, or a certification decision.
Establish the assessment boundary
Read references/readiness-routing.md. Confirm the PCI DSS version, entity type, selected validation process, assessor or compliance-accepting entity, assessment period, services, third parties, and whether segmentation reduces scope. If the request requires a full PCI DSS assessment, retain the broader requirement inventory as an external dependency and restrict this skill to its supported scope.
Route to specialist evidence
- Use
trace-cardholder-data-environmentto reconstruct payment flows, CDE components, connected and security-impacting systems, third-party paths, critical systems, and scope gaps. - Use
plan-pci-dss-penetration-testto define the methodology, internal and external coverage, application and network layers, tester qualifications and independence, significant-change triggers, rules of engagement, retention, remediation, and retest criteria. - Use
test-cardholder-data-segmentationwhen any segmentation or isolation control supports a scope-reduction claim. - Use
audit-pci-dss-penetration-test-evidenceto normalize the resulting evidence and identify unsupported or missing requirements without deciding compliance.
Do not repeat specialist procedures in the readiness layer. Preserve their artifact identities and reconcile conflicts, applicability, ownership, and dates.
Maintain the readiness register
Populate assets/pci-readiness-register.template.json under assets/pci-readiness-register.schema.json. Record each applicable requirement, evidence, status, owner, next action, and dependency. Use not-applicable only with an entity- and environment-specific rationale; a missing artifact is a gap, not non-applicability.
Separate:
- readiness of the entity's methodology and evidence;
- technical results from authorized testing;
- assessor validation and formal reporting;
- residual work outside Requirements 11.4 and 12.5.2.
Conclude with supported readiness, open gaps, blocked evidence, and the exact next discriminator. Never state that the entity is PCI DSS compliant.
Authoritative anchors
- PCI DSS v4.0.1: https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0_1.pdf
- PCI SSC PCI DSS overview: https://www.pcisecuritystandards.org/standards/pci-dss/
© cyberful, AGPL-3.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 (references, assets) in cyberful/builtin/skills/assess-pci-dss-readiness of cyberful/cyberful.
- SKILL.md
- agents/openai.yaml
- assets/pci-readiness-register.schema.json
- assets/pci-readiness-register.template.json
- references/readiness-routing.md
Open the folder on GitHubat commit ec598a6
Compare with similar skills
Assess Pci Dss Readiness 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 |
|---|---|---|---|---|---|---|
| Assess Pci Dss Readiness this skillcyberful/cyberful | 135 | — | ~895 | Automated safety check: Pass | AGPL-3.0 | |
| HIPAA Safe Harbor Coverage Auditmaziyarpanahi/openmed | 5.5k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| HIPAA Pre-Deployment Compliance Checkmaziyarpanahi/openmed | 5.5k | — | ~2k | Automated safety check: Pass | Apache-2.0 | |
| Hipaa ComplianceSushegaad/Claude-Skills-Governance-Risk-and-Compliance | 946 | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| ISO Standards Readiness EvidenceK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~4.6k | Automated safety check: Notes | MIT | |
| Fda Consultant Specialistdavila7/claude-code-templates | 33k | 1 repos | ~2.7k | Automated safety check: Pass | MIT |
Similar skills
HIPAA Pre-Deployment Compliance Check
maziyarpanahi/openmed
Walks a data pipeline against the HIPAA Privacy and Security Rule checklist and produces a gap report before it processes patient data.
Hipaa Compliance
Sushegaad/Claude-Skills-Governance-Risk-and-Compliance
Expert HIPAA compliance assistant for healthcare and software contexts.
ISO Standards Readiness Evidence
K-Dense-AI/scientific-agent-skills
Organizes scope, controlled documents, risk files and traceability into draft evidence for human review against ISO 13485, 14971, 17025 and 15189.
Fda Consultant Specialist
davila7/claude-code-templates
Senior FDA consultant and specialist for medical device companies including HIPAA compliance and requirement management.
Grc Knowledge
mlunato47/claude-grc-plugin
Senior GRC analyst expertise across 18 compliance frameworks — NIST 800-53, FedRAMP (Rev5 + 20x/CR26, KSIs, VDR/VER, Certification Classes A–D), DoD/DoW Impact Levels (IL2–IL6, DISA Cloud SRG), ITAR…
More from cyberful/cyberful
All 85 skills in this repoAudit Infrastructure As Code
cyberful/cyberful
Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.
Audit Kubernetes Policy Enforcement
cyberful/cyberful
Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.
Audit Pci Dss Penetration Test Evidence
cyberful/cyberful
Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.
Operate Content Discovery
cyberful/cyberful
Design and interpret advanced content discovery with ffuf and complementary web fuzzers.
Operate Network Recon
cyberful/cyberful
Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.
Operate Sast Toolchain
cyberful/cyberful
Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.
Related
Categories
Questions about Assess Pci Dss Readiness
What does Assess Pci Dss Readiness do?
Coordinate a PCI DSS penetration-testing and CDE-scoping readiness assessment across methodology, scope, segmentation, execution evidence, remediation, and retesting. Assess Pci Dss Readiness is an agent skill from cyberful/cyberful. Coordinate a PCI DSS penetration-testing and CDE-scoping readiness assessment across methodology, scope, segmentation, execution evidence, remediation, and retesting.
When should I use Assess Pci Dss Readiness?
Assess Pci Dss Readiness fits situations like: requirement 11.4 readiness; do not use it as a full PCI DSS compliance assessment.
How do I install Assess Pci Dss Readiness in Claude Code?
Run `npx skills add cyberful/cyberful --skill assess-pci-dss-readiness -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/assess-pci-dss-readiness in cyberful/cyberful) into .claude/skills/assess-pci-dss-readiness in your project. Claude Code loads it when a task matches its description.
How do I install Assess Pci Dss Readiness in Codex?
Run `npx skills add cyberful/cyberful --skill assess-pci-dss-readiness -a codex`. Or copy the skill folder (cyberful/builtin/skills/assess-pci-dss-readiness in cyberful/cyberful) into .agents/skills/assess-pci-dss-readiness in your project. Codex loads it when a task matches its description.
Can I use Assess Pci Dss Readiness 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 cyberful/cyberful --skill assess-pci-dss-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/assess-pci-dss-readiness, .gemini/skills/assess-pci-dss-readiness, .github/skills/assess-pci-dss-readiness and .opencode/skills/assess-pci-dss-readiness in your project.
What does Assess Pci Dss Readiness need to run?
SKILL.md names no scripts, command-line tools or credentials: Assess Pci Dss Readiness is instructions for the agent only.
Does Assess Pci Dss Readiness access the network?
SKILL.md names 2 domains. As links in the text: docs-prv.pcisecuritystandards.org and pcisecuritystandards.org. This is read from the text; nothing was executed.
Is Assess Pci Dss Readiness 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 Assess Pci Dss Readiness use?
Assess Pci Dss Readiness is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Assess Pci Dss Readiness use?
About 895 tokens (SKILL.md is roughly 3.6k 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 459 tokens, read only when the agent opens those files.
What are the alternatives to Assess Pci Dss Readiness?
Skills that share tags, products or a category with Assess Pci Dss Readiness: HIPAA Safe Harbor Coverage Audit (maziyarpanahi/openmed, 5.5k stars), HIPAA Pre-Deployment Compliance Check (maziyarpanahi/openmed, 5.5k stars), Hipaa Compliance (Sushegaad/Claude-Skills-Governance-Risk-and-Compliance, 946 stars) and ISO Standards Readiness Evidence (K-Dense-AI/scientific-agent-skills, 48k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Assess Pci Dss Readiness?
cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.
Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.