BD SOC 2 Compliance Accelerator
Your agent for achieving and maintaining SOC 2 Type I and Type II compliance — from readiness assessment through audit completion.
Your agent for achieving and maintaining SOC 2 Type I and Type II compliance — from readiness assessment through audit completion.
As a process D 48/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Risky intent
intent-offensive-securitySKILL.md:95Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)8. **Vulnerability Management**: Regular scanning, patch cadence (critical <72hrs), penetration testing
detector
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 48/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 7 mutating operations with no state check
- 40Consistency. Frontmatter name (SOC 2 Compliance Accelerator) differs from the folder (afrexai-soc2-compliance)
- 100Tools and files. No external tools needed
- 100Steps. 65 steps
- 100Execution cost. Instruction body is 2599 tokens
- 100Progress reporting. Reports progress
- low 13 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 130: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 65 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.