CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

soc2

Expert SOC 2 compliance assistant covering all five Trust Services Criteria (Security/CC, Availability/A, Confidentiality/C, Processing Integrity/PI, Privacy/P). Use this skill whenever a user mentions SOC 2, Trust Services Criteria, SOC 2 Type 1 or Type 2, audit readiness, compliance gaps, control documentation, evidence collection, vendor risk questionnaires, or anything related to AICPA service organization controls. Trigger even for adjacent topics like "we need to get audited", "a customer asked for our security report", "writing an information security policy", or "preparing for an audit". Covers gap analysis, policy writing, control documentation, audit evidence preparation, and vendor risk reviews for organizations at any maturity level — from first-time startups to seasoned compliance teams.

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured advisory skill: the body functions as a genuine overview with an effective task router, copy-paste templates, and clean one-level-deep progressive disclosure verified against the actual bundle. The main improvement areas are trimming reference-file duplication out of SKILL.md and adding worked examples plus explicit evidence-verification checkpoints in the gap-analysis workflow.

Suggestions

Trim the 13-row Core Policy Set table and the audit-evidence folder tree down to summaries (counts/categories), pointing to references/policies.md and references/evidence.md for the full lists, to cut duplicated tokens from the always-loaded body.

Add one worked example in Control Documentation — a filled-in control statement (e.g., a completed CC6.1 MFA control) — so the template's expected output quality is unambiguous.

In Gap Analysis Step 2, add an explicit checkpoint such as 'Do not mark 🟢 Met unless you can name the concrete evidence artifact that proves it' to close the validation gap in the workflow.

DimensionReasoningScore

Conciseness

The body is efficient — task router, quick-reference tables, and fill-in templates earn their tokens — but the 13-row policy table and evidence folder tree restate detail that lives in references/policies.md and references/evidence.md, and the 'You are an expert SOC 2 compliance advisor' preamble is padding. Fits 'efficient with minor instances that could be trimmed' rather than 'every token earns its place'.

4 / 5

Actionability

Concrete, fill-in-ready guidance throughout: the remediation plan block (Control Area / Gap / Remediation / Owner / Target Date / Evidence Needed), the control statement format, RAG status definitions, and the vendor risk tier table. It falls short of fully executable only in lacking a worked example of a completed control statement or remediation entry.

4 / 5

Workflow Clarity

Gap analysis is a clearly sequenced Step 1→4 (scope confirmation → RAG self-assessment → common gaps → remediation plan) with a scoping checkpoint ('Before assessing, confirm: …'). Minor validation gaps remain — e.g., no explicit instruction to verify evidence actually exists before rating a criterion 🟢 Met — keeping it below the explicit-validation anchor 5.

4 / 5

Progressive Disclosure

Clear overview with a task router signaling the correct reference per task, per-section pointers ('Read references/policies.md for full templates'), a consolidated Reference Files section, and — verified on disk — all four referenced files exist with no nested references, giving well-signaled one-level-deep navigation.

5 / 5

Total

17

/

20

Passed

Description

96%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 excellent description: it explicitly states what the skill does and when to use it, with comprehensive, naturally phrased trigger terms and concrete capability coverage. The only weakness is slight over-extension via broad adjacent triggers (e.g., general information-security-policy requests) and minor length padding ("for organizations at any maturity level — from first-time startups to seasoned compliance teams").

DimensionReasoningScore

Specificity

The description lists five concrete actions — "gap analysis, policy writing, control documentation, audit evidence preparation, and vendor risk reviews" — plus the full domain scope (all five Trust Services Criteria), matching the comprehensive-coverage anchor rather than the 'minor gaps' level below.

5 / 5

Completeness

Both 'what' ("Expert SOC 2 compliance assistant covering all five Trust Services Criteria… Covers gap analysis, policy writing…") and 'when' ("Use this skill whenever a user mentions…" plus explicit adjacent-topic triggers) are clearly and explicitly stated, exceeding the anchor-4 level where 'when' could be more specific.

5 / 5

Trigger Term Quality

It covers the formal keywords ("SOC 2", "Trust Services Criteria", "Type 1 or Type 2", "audit readiness", "vendor risk questionnaires") AND natural user phrasings ("we need to get audited", "a customer asked for our security report", "preparing for an audit"), giving comprehensive natural-term coverage.

5 / 5

Distinctiveness Conflict Risk

SOC 2 compliance is a clear niche with distinct triggers, but the deliberately broad adjacent triggers — "writing an information security policy", "a customer asked for our security report" — create minor overlap risk with generic security-policy or ISO 27001-type skills, placing it just below the minimal-conflict anchor 5.

4 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Sushegaad/Claude-Skills-Governance-Risk-and-Compliance

Path

plugins/soc2/skills/soc2/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.