DC pocket-ai
(no description)
Not recommendedlow grade D
As a process C 59/100 · Has gaps — weak spots: when it triggers, inputs and preconditions
How to improve
- Add a description to the frontmatter: without it the skill never triggers.
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 Exfiltration
net-credential-useexamples.md:8Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -s -X POST -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/json" \
fixture -
low Exfiltration
net-credential-useexamples.md:16Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -s -X POST -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/json" \
fixture -
low Exfiltration
net-credential-useexamples.md:23Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -s -X POST -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/json" \
fixture -
low Exfiltration
net-credential-useexamples.md:31Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -s -X POST -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/json" \
fixture -
low Exfiltration
net-credential-useexamples.md:38Credential used in a network call (verify the destination is the intended service) (test fixture / example file)curl -s -X POST -H "Authorization: Bearer $API_KEY" -H "Content-Type: application/json" \
fixture
Files scanned: 7. 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 59/100
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 27 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1586 tokens
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +4Structure: 30 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 0.
External checks
ClawHub: suspicious
This appears to be a real Pocket AI integration, but it needs review because it gives an agent broad access to sensitive recordings while under-disclosing cloud data flow and sharing controls.
LLM: suspicious (high) · VirusTotal: suspicious · 28 May 2026