CtrlK
BlogDocsLog inGet started
Tessl Logo

assisting-with-soc2-audit-preparation

This skill assists with SOC2 audit preparation by automating tasks related to evidence gathering and documentation. It leverages the soc2-audit-helper plugin to generate reports, identify potential compliance gaps, and suggest remediation steps. Use this skill when the user requests help with "SOC2 audit", "compliance check", "security controls", "audit preparation", or "evidence gathering" related to SOC2. It streamlines the initial stages of SOC2 compliance, focusing on automated data collection and preliminary analysis.

88

1.00x
Quality

53%

Does it follow best practices?

Impact

95%

1.00x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./backups/skills-migration-20251108-070147/plugins/security/soc2-audit-helper/skills/soc2-audit-helper/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

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

This is a strong skill description that clearly defines its purpose, lists concrete actions, provides explicit trigger terms, and occupies a distinct niche. It follows third-person voice throughout and balances detail with conciseness. Minor improvement could come from trimming slight redundancy between the opening and closing sentences.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'generate reports', 'identify potential compliance gaps', 'suggest remediation steps', 'automated data collection and preliminary analysis', and 'evidence gathering and documentation'.

3 / 3

Completeness

Clearly answers both 'what' (automating evidence gathering, generating reports, identifying compliance gaps, suggesting remediation) and 'when' with an explicit 'Use this skill when...' clause listing specific trigger phrases.

3 / 3

Trigger Term Quality

Includes natural keywords users would say: 'SOC2 audit', 'compliance check', 'security controls', 'audit preparation', 'evidence gathering'. These are terms a user would naturally use when seeking SOC2 help.

3 / 3

Distinctiveness Conflict Risk

SOC2 audit preparation is a clear, specific niche. The triggers are domain-specific ('SOC2 audit', 'compliance check', 'security controls') and unlikely to conflict with general document or code skills.

3 / 3

Total

12

/

12

Passed

Implementation

7%

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

This skill content is almost entirely descriptive and lacks any actionable, executable guidance. It reads like a marketing overview of a plugin rather than a skill that teaches Claude how to perform specific tasks. There are no concrete commands, no code examples, no parameter specifications, no output formats, and no validation steps—making it essentially unusable as an operational skill.

Suggestions

Add concrete, executable examples showing exactly how to invoke the soc2-audit-helper plugin, including specific commands, parameters, and expected output formats.

Remove generic explanatory sections (Overview, When to Use, Integration, Best Practices) that describe concepts Claude already knows, and replace them with actionable instructions.

Add validation checkpoints to the workflow—e.g., how to verify the plugin ran successfully, how to handle errors, and what to check in the generated report before presenting it to the user.

Include a concrete example of plugin invocation with sample input and sample output (even abbreviated) so Claude knows exactly what to expect and how to format results.

DimensionReasoningScore

Conciseness

The content is verbose and explains concepts Claude already knows (what SOC2 is, what evidence gathering means). Sections like 'How It Works', 'When to Use This Skill', and 'Integration' are padded with generic descriptions that add no actionable value. The 'Best Practices' section states obvious advice like 'review findings' and 'provide detail'.

1 / 3

Actionability

There are no concrete commands, code snippets, API calls, or executable instructions. The examples describe what the skill 'will do' in vague terms ('invoke the plugin', 'generate a report') without showing how to actually invoke the plugin, what parameters to pass, or what the output looks like. Everything is descriptive rather than instructive.

1 / 3

Workflow Clarity

The 'How It Works' section lists three abstract steps with no concrete commands, no validation checkpoints, and no error handling. The examples similarly lack any actual workflow—they just say 'invoke the plugin' and 'generate a report' without specifying how, what to verify, or what to do if something fails.

1 / 3

Progressive Disclosure

The content has some structural organization with clear section headers (Overview, How It Works, Examples, Best Practices). However, there are no references to external files, no bundle files to support deeper content, and the content is somewhat monolithic with sections that could be trimmed rather than split out.

2 / 3

Total

5

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
jeremylongshore/claude-code-plugins-plus-skills
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.