CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

control-audit

Control-level audit readiness for SOC 2, ISO/IEC 27001:2022 and NIST SP 800-53 Rev. 5 / FedRAMP. Scope the audit (criteria or baseline, systems, period, Type 1 vs Type 2), build the control inventory, write an evidence request per control (artifact, owner, sample, test method), test what the repo and configs show (CC8.1 / A.8.32 / CM-3 change management via branch protection), hand technical checks to the owning skill, and record control gaps in the shared findings format with a control matrix. Use when the user mentions 'SOC 2,' 'SOC 2 Type 2,' 'Trust Services Criteria,' 'ISO 27001,' 'ISMS,' 'Statement of Applicability,' 'Annex A controls,' 'NIST 800-53,' 'FedRAMP,' 'FedRAMP 20x,' 'SSP,' 'POA&M,' 'control matrix,' 'evidence request list,' 'PBC list,' 'audit readiness,' 'control testing,' or is getting ready for an external auditor or assessor.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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.

A strong, mature skill body: fully executable commands and templates, a gated five-step workflow with real validation loops, and clean one-level-deep reference structure verified against the actual bundle. The only weakness is token budget — roughly 290 lines with a trimmable standards bibliography and occasional non-operational prose.

Suggestions

Move the closing standards bibliography (AICPA guide, COSO framework, ISO/IEC 27002, FedRAMP Consolidated Rules citations) into the per-framework reference files, keeping only the framework-to-reference mapping table in SKILL.md.

Trim non-operational flavor sentences (e.g., "Most readiness work that goes wrong went wrong here") and merge the two handoff tables' surrounding prose to cut the body closer to a lean overview.

Consider moving the full report markdown template into a reference file, keeping inline only the section list and the rule that the JSON drives the prose.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely skill-specific knowledge (sample-size tables, test-method hierarchy, fingerprint grammar, evidence-handling rules) rather than concepts Claude already knows, but there is trimmable material: the closing standards bibliography (COSO, AICPA guide, ISO/IEC citations) largely duplicates content carried by the reference files, and a few flavor sentences ("Most readiness work that goes wrong went wrong here") are not operational. This sits at efficient-with-minor-trimming rather than every-token-earns-its-place.

4 / 5

Actionability

Guidance is copy-paste executable throughout: exact read-only commands with portable fallbacks ("gh api repos/<owner>/<repo>/branches/main/protection", "rg -n \"required_approving_review_count\\|enforce_admins\" -g '*.tf'"; portable grep variant), concrete pass conditions ("approver ≠ author, approval before merge, CI green at merge"), worked fingerprint examples, field-by-field tables, a validation command, and a complete renderable report template.

5 / 5

Workflow Clarity

The five steps are clearly sequenced with explicit gates and feedback loops: "Write scope.md before anything else," "run the refutation pass in references/verification.md before anything is confirmed," "Validate it and fix every error" on findings.json, and re-run matching by fingerprint with rules for stale rejected records — matching the top anchor's validation-plus-error-recovery pattern.

5 / 5

Progressive Disclosure

SKILL.md stays at the overview/workflow level while framework detail is split into one-level-deep, clearly linked references (references/soc2.md, references/iso27001.md, references/nist-800-53.md) plus shared format files and scripts (findings-format.md, verification.md, severity-calibration.md, validate-findings.mjs, to-sarif.mjs) — all of which exist in the bundle, with none nested deeper than one level.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An exemplary description: concrete third-person action list, explicit and comprehensive 'Use when' triggers covering both formal and colloquial phrasings, and a clearly bounded niche that separates it from adjacent audit skills. Density is high but every clause is informative rather than padded.

DimensionReasoningScore

Specificity

The description lists six concrete actions with specifics — "Scope the audit (criteria or baseline, systems, period, Type 1 vs Type 2), build the control inventory, write an evidence request per control (artifact, owner, sample, test method), test what the repo and configs show (CC8.1 / A.8.32 / CM-3 change management via branch protection), hand technical checks to the owning skill, and record control gaps" — covering the full lifecycle from scoping to recording, which matches the comprehensive-coverage anchor rather than the several-actions-with-minor-gaps anchor.

5 / 5

Completeness

It explicitly answers both questions: the what is the enumerated action set, and the when is an explicit "Use when the user mentions..." clause with concrete trigger phrases, exactly matching the top anchor. A weaker 'when' would cap it at 4, but here the trigger guidance is fully explicit.

5 / 5

Trigger Term Quality

The trigger list spans formal names and practitioner shorthand a user would naturally say: "'SOC 2,' 'SOC 2 Type 2,' 'Trust Services Criteria,' 'ISO 27001,' 'ISMS,' 'Statement of Applicability,' 'NIST 800-53,' 'FedRAMP,' 'FedRAMP 20x,' 'SSP,' 'POA&M,' 'control matrix,' 'PBC list,' 'audit readiness,' 'control testing,'" plus the plain-language "getting ready for an external auditor or assessor."

5 / 5

Distinctiveness Conflict Risk

The niche is precise — control-level readiness for SOC 2 / ISO 27001:2022 / NIST 800-53 / FedRAMP — and the triggers are framework-specific terms that don't overlap with sibling skills' territory (PCI, HIPAA, CSF tiers), giving minimal conflict risk.

5 / 5

Total

20

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

briiirussell/cybersecurity-skills

Path

skills/control-audit/SKILL.md

Reviewed

Table of Contents

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.