CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

64

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./compliance-os/skills/compliance-readiness/SKILL.md
SKILL.md
Quality
Evals
Security

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 dense with actionable, threshold-driven guidance, concrete script commands, and a complete output format, all organized into clean sections with no filler. Its gaps are validation depth (no failure/retry handling in the workflow) and reliance on external paths whose existence the reader cannot verify from this skill.

Suggestions

Add an explicit validation step to the workflow, e.g. 'if the mock-audit distribution is unhealthy, re-scope the audit and re-run audit_simulator.py' to close the fix-and-retry loop.

Document the expected shape of the input files (profile.json, program.json, scope.json) or point to where those formats are defined, since the commands are otherwise not runnable as written.

Make script references resolvable (bundle the scripts or reference them relative to the skill root) rather than via layout-dependent ../../skills/ paths.

DimensionReasoningScore

Conciseness

The body is lean — each question pairs a one-line smell with concrete thresholds ("HIGH-leverage artefacts (≥ 5 mappings)", "≥ 40% observation, ≤ 15% critical") and no space is spent explaining compliance basics. The only trimmable redundancy is the opening paragraph restating the frontmatter description almost verbatim, which keeps it below the 'every token earns its place' anchor.

4 / 5

Actionability

Commands are executable with arguments ("python ../../skills/compliance-os/scripts/framework_selector.py profile.json") and the output template is fully specified, but the input files (profile.json, program.json, scope.json) have no documented format and the script paths assume a fixed repository layout — concrete guidance with minor gaps.

4 / 5

Workflow Clarity

The numbered 4-step workflow is clearly sequenced, and the mock-audit severity distribution check plus the READY/STAGE-2/NOT-READY verdict function as checkpoints. It stops short of the top anchor because there is no explicit fix-and-retry loop or guidance for what to do when a script fails or a check comes back unhealthy.

4 / 5

Progressive Disclosure

A single well-sectioned file (~130 lines) with clearly signaled one-level-deep links (Routing, Related, agent and sibling-skill references) — good structure with minor gaps: the referenced script and skill paths (../../skills/compliance-os/...) live outside this bundle, so no local reference material backs them.

4 / 5

Total

16

/

20

Passed

Description

78%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 clearly and explicitly covers both what the skill does and when to use it, with natural trigger phrases and a distinct multi-framework niche. Its only weakness is specificity: it describes the interrogation format without naming the concrete operations the skill actually performs.

Suggestions

Name the concrete operations in the description, e.g. 'Selects applicable frameworks, maps control overlaps, consolidates the evidence pool, and runs a mock audit across a compliance program' instead of only '6-question forcing interrogation'.

Add common trigger synonyms users would naturally say, such as 'audit readiness', 'ISO/SOC 2 certification prep', or 'compliance program review', to broaden keyword coverage.

Disambiguate from sibling single-framework skills by signaling scope, e.g. 'use this before any framework-specific command like /cs:aims-audit'.

DimensionReasoningScore

Specificity

"6-question forcing interrogation of any compliance program" names the domain and one concrete action-shape but never enumerates the actual operations (framework selection, overlap mapping, mock audit), matching the 'names domain and 1-2 concrete actions, not comprehensive' anchor rather than the 'lists several specific actions' anchor.

3 / 5

Completeness

It explicitly answers both what ("Multi-framework compliance officer 6-question forcing interrogation of any compliance program") and when ("Use before starting a new framework, planning the annual audit calendar, or preparing for certification stage 1") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"starting a new framework", "planning the annual audit calendar", and "preparing for certification stage 1" are natural trigger phrases, but common variations users would say (audit prep, readiness review, specific framework names like ISO or SOC 2) are missing, so it falls just short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The "multi-framework" framing carves a clear niche with distinct triggers, but the skill sits in a family of closely related compliance commands (single-framework audit and readiness skills), creating minor overlap risk with those siblings rather than minimal conflict risk.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

alirezarezvani/claude-skills

Path

compliance-os/skills/compliance-readiness/SKILL.md

Revision

19392f7

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill