AC heimdall
Author and run evidence-backed browser and API test plans with honest blocked and non-run semantics. Use when an agent needs to exercise a live web app or API through Playwright/CDP, an isolated Docker browser, or a human-controlled logged-in browser lane.
Author and run evidence-backed browser and API test plans with honest blocked and non-run semantics.
As a process C 62/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:50High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…RNq/mC+16R1…A0M+/s6ny…wFA==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:123High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…S4F+im88…HRE/cYlx…2oE/ufM0p61IKng==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:174High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…rdY+ziCYCPMmtZjjIwOmXFjmyzEHn+UUxk5of+SYsj…5hY/rOAw==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:259High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…NmN+loZK…eAz+famM…vZz+zT1jlh/keC3Rj/lg==",
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:573High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…kni+7p+2IAE…qay/36uRV/bFkg…gzy+Q==",
detector
Files scanned: 45. 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 62/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Inputs and preconditions. Does not say what the process needs to start
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. No external tools needed
- 100Steps. 4 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 772 tokens
- 100Running it twice. No mutating operations
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
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +3Description length 256: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 4 items
- +4Has examples (4 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 83.