BC li-base-scan
Linux base security scanner integrating multiple tools - nmap, lynis, nikto, sqlmap, trivy. SINGLE HOST ONLY. Features secure temp files, progress bar, scan history, report export. Comprehensive security baseline scanning with hardened implementation.
As a process C 62/100 · Has gaps — weak spots: when it triggers, inputs and preconditions
IntegrationInfrastructureData and analyticstype and topics are labelled automatically from the skill text
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:240Pipe-to-shell installer from a well-known host (still executes remote code) (documentation of a security skill)curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh
security skill -
low Dangerous commands
cmd-pipe-to-shell-known-hostSKILL.md:481Pipe-to-shell installer from a well-known host (still executes remote code) (documentation of a security skill)curl -sfL https://raw.githubusercontent.com/aquasecurity/trivy/main/contrib/install.sh | sh
security skill
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 62/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 84 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2734 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (8 tags): a typed call is more reliable
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)
- -2localhost URLs: will not work for another user
- -219 emoji in the instructions: noise for the model
- -32 of 4 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +3Description length 251: enough signal without eating the budget
- +4Structure: 80 headings
- +3Step-by-step instructions: 84 items
- +3Output format is stated explicitly
- +4Has examples (48 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.
External checks
ClawHub: suspicious
This appears to be a real security scanner, but some modes under-disclose local whole-filesystem secret scanning and stealth scan behavior.
LLM: suspicious (high) · VirusTotal: · 29 May 2026