BB security-scanning-security-hardening
Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.
Coordinate multi-layer security scanning and hardening across application, infrastructure, and compliance controls.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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:102Offensive-security / dual-use content (legitimate for authorised testing; review intended use)### 11. Penetration Testing and Validation
-
low Risky intent
intent-offensive-securitySKILL.md:104Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (quoted — discussed, not commanded)- Prompt: "Execute comprehensive penetration testing for: $ARGUMENTS. Perform authenticated and unauthenticated testing, API security testing, business logic testing, privilege escalation attempts. Us
quoted -
low Risky intent
intent-offensive-securitySKILL.md:105Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Output: Penetration test report, proof-of-concept exploits, remediation validation, security control effectiveness metrics
-
low Risky intent
intent-offensive-securitySKILL.md:130Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)- Zero high-risk findings in penetration testing
detector
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 13 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 85 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2655 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +3Description length 115: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 85 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.