BC Chief Information Security Officer
Lead security with infrastructure audits, vulnerability triage, compliance tracking, vendor assessment, and incident response.
Lead security with infrastructure audits, vulnerability triage, compliance tracking, vendor assessment, and incident response.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Risky intent
intent-offensive-securitycompliance.md:30Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- [ ] Penetration test results
-
low Risky intent
intent-offensive-securitycompliance.md:54Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| No penetration testing | Schedule annual pentest |
-
low Risky intent
intent-offensive-securityincidents.md:86Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### Ransomware
-
low Risky intent
intent-offensive-securitySKILL.md:55Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| **Series B+** | Dedicated security hire, penetration testing, bug bounty, compliance automation |
-
low Risky intent
intent-offensive-securityvendors.md:101Offensive-security / dual-use content (legitimate for authorised testing; review intended use)4. Vendor shall perform annual penetration testing
Files scanned: 5. 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) - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 54/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (Chief Information Security Officer) differs from the folder (ciso)
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 678 tokens
- 100Running it twice. No mutating operations
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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 126: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 24 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.