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.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and actionable, with concrete scripts, thresholds, a numbered workflow, and a verdict-gated output template. Weakest on explicit validation feedback loops and on progressive disclosure (no own bundle files, some redundancy across sections).

Suggestions

Add an explicit validate→fix→retry loop in the Workflow section (e.g., re-run audit_simulator.py after addressing critical findings before issuing the verdict) to raise workflow clarity.

De-duplicate the script invocations between the Six Questions and the Workflow section so each script appears once with its full invocation syntax.

Confirm the ../../skills/compliance-os/scripts/ paths resolve from this skill's location, or note the dependency explicitly, since no local scripts/ bundle exists.

Dimension	Reasoning	Score
Conciseness	Mostly lean and efficient — punchy bolded principles plus concrete bullets, with specific thresholds rather than concept explanation. Not a 5 because the Workflow section repeats script invocations already named in the Six Questions, and a few rationale lines could be trimmed.	4 / 5
Actionability	Provides concrete script names, full bash invocations with arguments, and numeric thresholds (≥40% observation, ≤15% critical, ≥5 mappings). Not a 5 because the Six Questions reference scripts by informal phrasing ("Run framework_selector.py with company profile") and the invoked scripts live in an external path that is not part of this skill's bundle.	4 / 5
Workflow Clarity	Six numbered questions plus a four-step numbered Workflow give a clear sequence, and the healthy-distribution check plus READY/STAGE-2-CANDIDATE/NOT-READY verdict act as checkpoints. Not a 5 because there is no explicit validate→fix→retry feedback loop between workflow steps.	4 / 5
Progressive Disclosure	Well-organized into clear sections (When to Run, Six Questions, Workflow, Output Format, Routing, Related) with one-level-deep references to related skills and agents. Not a 5 because the skill has no bundle files of its own and is over 50 lines, so the simple-skill exception does not fully apply.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong: it states a specific action, gives explicit "Use before…" trigger guidance with concrete compliance scenarios, and occupies a distinct niche. Minor room to add synonyms/shorthand for trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and a concrete mechanism — "6-question forcing interrogation of any compliance program" — giving a specific action rather than vague language. Not a 5 because it describes essentially one action rather than a comprehensive list of concrete actions.	4 / 5
Completeness	Explicitly answers both what ("Multi-framework compliance officer 6-question forcing interrogation") and when ("Use before starting a new framework, planning the annual audit calendar, or preparing for certification stage 1") with concrete trigger phrases. Voice is third person; no first/second-person penalty.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users in compliance would say — "starting a new framework", "annual audit calendar", "certification stage 1". Not a 5 because common synonyms and shorthand variants are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (multi-framework compliance readiness) with distinct triggers unlikely to fire for unrelated skills, minimizing conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: alirezarezvani/claude-skills
Path: compliance-os/skills/compliance-readiness/SKILL.md
Commit: 19392f7

Reviewed: ~10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.