BC sovereign-test-generator
Analyzes codebases and generates comprehensive test suites. Unit tests, integration tests, edge cases, mocking strategies. Supports JavaScript/TypeScript (Jest, Vitest), Python (pytest), Go, and Rust.
As a process C 64/100 · Has gaps — weak spots: when it triggers, execution cost, running it twice
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
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-password-literalSKILL.md:271Hard-coded password / key literal (may be an example)password: 'secureP@ss123',
-
low Secrets in code
secret-password-literalSKILL.md:440Hard-coded password / key literal (may be an example)password="secureP@ss123",
-
low Secrets in code
secret-password-literalSKILL.md:455Hard-coded password / key literal (may be an example)password="secureP@ss123",
-
low Secrets in code
secret-password-literalSKILL.md:467Hard-coded password / key literal (may be an example)password="secureP@ss123",
-
low Secrets in code
secret-password-literalSKILL.md:494Hard-coded password / key literal (may be an example)password="secureP@ss123",
Files scanned: 4. 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") - warning
body-longSKILL.md body ≈ 10790 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 64/100
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 13 mutating operations with no state check
- 40Execution cost. Instruction body is 10790 tokens: crowds the task out of the window
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 94 steps, 1 vague phrases
- 100Failures and branches. 5 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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)
- +1No license
- +2Single-language instructions
- +3Description length 200: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 94 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: clean
This is an instruction-only testing skill that coherently helps an agent analyze code and generate test suites, with no evidence of hidden execution or data exfiltration.
LLM: benign (high) · VirusTotal: benign · 28 May 2026