BC Security Best Practices
Review code with secure-by-default standards, prioritize exploitable risks, and deliver minimal-diff fixes with evidence and regression checks.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
AnalyzerSoftware developmentInfrastructureData and analyticstype and topics are labelled automatically from the skill text
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Risky intent
intent-offensive-securityremediation-patterns.md:19Offensive-security / dual-use content (legitimate for authorised testing; review intended use) (detector / deny-list definition)Why: default-deny reduces accidental privilege escalation.
detector -
low Risky intent
intent-offensive-securityseverity-model.md:8Offensive-security / dual-use content (legitimate for authorised testing; review intended use)- Remote compromise or privilege escalation is realistic.
Files scanned: 8. 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" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (Security Best Practices) differs from the folder (security-best-practices)
- 65Failures and branches. 3 branches
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 42 steps
- 100Execution cost. Instruction body is 1084 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 143: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 42 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: clean
This skill is a transparent security-review guide with optional consent-based local notes and no executable or hidden network behavior found.
LLM: benign (high) · VirusTotal: benign · 28 May 2026