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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill assisting-with-soc2-audit-preparation88
Quality
53%
Does it follow best practices?
Impact
95%
1.00xAverage score across 9 eval scenarios
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.mdDiscovery
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 well-crafted skill description that excels across all dimensions. It provides specific concrete actions, includes an explicit 'Use this skill when...' clause with natural trigger terms, and occupies a clear niche in SOC2 compliance that distinguishes it from other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'automating tasks related to evidence gathering and documentation', 'generate reports', 'identify potential compliance gaps', 'suggest remediation steps', 'automated data collection and preliminary analysis'. | 3 / 3 |
Completeness | Clearly answers both what (automates evidence gathering, generates reports, identifies gaps, suggests remediation) AND when with explicit 'Use this skill when...' clause listing specific trigger phrases. | 3 / 3 |
Trigger Term Quality | Explicitly includes natural trigger terms users would say: 'SOC2 audit', 'compliance check', 'security controls', 'audit preparation', 'evidence gathering'. These are terms users would naturally use when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche focused on SOC2 compliance with distinct triggers like 'SOC2 audit', 'security controls', 'audit preparation'. Unlikely to conflict with general document or code skills due to the specialized compliance domain. | 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 largely descriptive rather than instructive, explaining what the skill does conceptually without providing actionable guidance. It lacks concrete plugin invocation syntax, parameter examples, expected output formats, or validation steps. The content would benefit from executable examples and specific commands rather than abstract workflow descriptions.
Suggestions
Add concrete plugin invocation syntax with actual parameters (e.g., `soc2-audit-helper --environment aws --scope security-controls`)
Include example output format or schema so Claude knows what to expect and how to interpret results
Remove 'How It Works' and 'When to Use This Skill' sections - this information is redundant with the skill description and wastes tokens
Add validation/error handling guidance: what to do if the plugin returns errors, incomplete data, or requires additional permissions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is verbose and explains concepts Claude already knows (what SOC2 is, general workflow descriptions). Sections like 'How It Works' and 'When to Use This Skill' add little actionable value and repeat information from the description. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. Examples describe what 'the skill will do' abstractly rather than showing actual plugin invocation syntax, parameters, or expected output formats. | 1 / 3 |
Workflow Clarity | Steps are vague ('invoke the plugin', 'generate a report') with no validation checkpoints, error handling, or specific sequences. No guidance on what to do if the plugin fails or returns incomplete data. | 1 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline with no references to external documentation. The 'Integration' section hints at broader context but provides no concrete links or guidance. | 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Table of Contents
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.