BC Compliance & Audit Readiness Engine
Your AI compliance officer. Guides startups and scale-ups through SOC 2, ISO 27001, GDPR, HIPAA, and PCI DSS — from zero to audit-ready. No consultants needed.
Your AI compliance officer.
As a process C 54/100 · Has gaps — 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.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
For the model run — optional
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
low Risky intent
intent-offensive-securitySKILL.md:115Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Penetration testing (annual minimum)
-
low Risky intent
intent-offensive-securitySKILL.md:559Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Schedule penetration test (results needed before audit)
-
low Risky intent
intent-offensive-securitySKILL.md:602Offensive-security / dual-use content (legitimate for authorised testing; review intended use)pent…pdf
-
low Risky intent
intent-offensive-securitySKILL.md:678Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Annual** | Full risk assessment, penetration test, policy review cycle, SOC 2/ISO audit, security awareness training, management review |
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") - warning
body-longSKILL.md body ≈ 7926 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 54/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 10 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (Compliance & Audit Readiness Engine) differs from the folder (afrexai-compliance-engine)
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 7926 tokens
- 85Steps. 248 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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 159: enough signal without eating the budget
- +4Structure: 68 headings
- +3Step-by-step instructions: 248 items
- +4Has examples (8 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.