Agent skill · Security

compliance-readiness

/cs:compliance-readiness <program> — Multi-framework compliance officer 6-question forcing interrogation of any compliance program. Use before starting a new framework, planning the annual audit calendar, or preparing for certification stage 1.

Alireza Rezvani23,369★ · +428/wk · 1 repos on radarProfile →
claude-codecodexcursorMIT
Install
npx skills add alirezarezvani/claude-skills --skill compliance-readiness --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Path: compliance-os/skills/compliance-readiness/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 23,791 · +422 this week
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# /cs:compliance-readiness — Compliance Officer Forcing Questions **Command:** `/cs:compliance-readiness <program>` The multi-framework compliance officer pressure-tests any compliance program. Six questions before any new-framework commitment, audit cycle planning, or certification readiness sign-off. ## When to Run - Before adopting a new compliance framework - Before annual audit calendar finalization - Before certification stage 1 readiness sign-off - Before management review (Clause 9.3 across frameworks) - When evidence-collection effort has grown 50%+ year-over-year (a smell) - When an audit produced > 15% critical findings ## The Six Compliance Officer Questions ### 1. Have you named every applicable framework? **No framework selector run, no defensible scope.** - Run `framework_selector.py` with company profile - Forgetting a framework means rebuilding the audit program later - Pay attention to industry-specific overlays (financial: NYDFS, FINMA; healthcare: HIPAA, ISO 13485; AI: ISO 42001 + EU AI Act) ### 2. Where do the frameworks overlap, and what's the reuse leverage? **Single evidence -> N controls = the cornerstone of multi-framework efficiency.** - Run `cross_framew

What's inside
Steps it walks through
  1. When to Run
  2. The Six Compliance Officer Questions
  3. 1. Have you named every applicable framework?
  4. 2. Where do the frameworks overlap, and what's the reuse leverage?
  5. 3. Who owns each artefact, and what's the reuse-leverage score?
  6. 4. What's the audit calendar, and is auditor independence respected?
  7. 5. What does a mock audit produce, and is the severity distribution healthy?
  8. 6. What's the management review cadence across frameworks?
  9. Workflow
  10. Output Format
  11. Routing
  12. Related
Commands it runs
python ../../skills/compliance-os/scripts/framework_selector.py profile.json
python ../../skills/compliance-os/scripts/cross_framework_mapper.py program.json
python ../../skills/compliance-os/scripts/evidence_pool_generator.py program.json
python ../../skills/compliance-os/scripts/audit_simulator.py scope.json
More from claude-skills
All skills →
About this skill
What does the compliance-readiness skill do?

/cs:compliance-readiness <program> — Multi-framework compliance officer 6-question forcing interrogation of any compliance program. Use before starting a new framework, planning the annual audit calendar, or preparing for certification stage 1.

How do I install it?

Run `npx skills add alirezarezvani/claude-skills --skill compliance-readiness --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going