DC nano-banana-openrouter
(no description)
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain someone else's key or token. If it is live, your agent will call third-party services under a stranger's identity; if it was revoked, the skill's scripts simply fail. Such a key often arrives with the author's whole workspace, personal data included.
The key is visible to everyone who downloaded the skill and has likely been copied by catalog-scanning bots already. Revoke it now, check bills and access logs, then reissue.
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Secrets in code
secret-openrouter-keytest-gen.mjs:3OpenRouter API key (test fixture / example file; quoted — discussed, not commanded)const apiKey = "sk-o…cb3";
fixturequoted -
low Secrets in code
secret-high-entropy-tokenoutput.json:3High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"id": "gen-…XW0",
quoted -
low Secrets in code
secret-high-entropy-tokenoutput.json:24High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"url": "data:image/png;base64,iVBO…gfh/QaDg…u9p+ULkapDENgzpj+Kl5
detector -
low Secrets in code
secret-high-entropy-tokenpackage-lock.json:127High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…wQp+7C4n…9JQ==",
detector -
low Secrets in code
secret-labelled-tokentest-gen.mjs:3Labelled token / key literal (vendor format unknown — verify it is not a live credential) (test fixture / example file)const apiKey = "sk-o…cb3";
fixture -
low Secrets in code
secret-password-literaltest-gen.mjs:3Hard-coded password / key literal (may be an example) (test fixture / example file)const apiKey = "sk-o…cb3";
fixture
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
frontmatterSKILL.md: no YAML frontmatter block found - error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 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
- 100Tools and files. No external tools needed
- 100Steps. 7 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 280 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 7 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.