AB yummy-shared
Use when operating yummycli for the first time, checking Gemini credential status, handling yummycli JSON command output, or applying shared CLI safety rules before image generation or editing.
As a process B 66/100 · Nearly there — weak spots: when it triggers, inputs and preconditions, running it twice
IntegrationInfrastructureWriting and documentstype and topics are labelled automatically from the skill text
How to improve
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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 · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 193 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - note
frontmatter-keyunknown frontmatter key "always" - note
frontmatter-keyunknown frontmatter key "install"
Process rating: all ten parameters 66/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 60Consistency. The Hermes dialect needs category and tags
- 100Tools and files. No external tools needed
- 100Steps. 5 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 316 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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 193: enough signal without eating the budget
- +4Structure: 4 headings
- +3Step-by-step instructions: 5 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.
External checks
ClawHub: suspicious
This skill is mostly a coherent yummycli/Gemini helper, but it documents an unsafe way to pass a live Gemini API key on the command line.
LLM: suspicious (medium) · VirusTotal: · 29 May 2026