BD agentscale
Deploy web apps and APIs to a public URL with a single command.
As a process D 43/100 · Unfinished process — 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.
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 Secrets in code
secret-high-entropy-tokenpackage-lock.json:26High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…7pY+zoMV…h0x/Ptw8…8dg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:43High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…b00+Gxjx…zRc/oZwU…hzA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:111High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha512-vHk/hA7/1Ack…wbo+jaSh…Gtl+A5zq…HFg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:145High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…Dsc+j03S…0oA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:434High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NS8+tHW7…WOF+PEzk…X4Q==",
detector
Files scanned: 12. 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") - note
frontmatter-keyunknown frontmatter key "required_tools"
Process rating: all ten parameters 43/100
- 0Result and completion. Does not say what the result is
- 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
- 30Running it twice. 7 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 17 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 491 tokens
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 63: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 11 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: clean
This is a coherent deployment tool, but using it will upload your project and use a locally stored API key.
LLM: benign (high) · VirusTotal: suspicious · 27 May 2026