CD yaps-image-generate
Create an image from a written prompt with Yaps. Save the result or make a sticker. New users: install Yaps and sign in.
Create an image from a written prompt with Yaps.
As a process D 40/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Concealment
en-hide-from-userreferences/runtime.md:12Instruction to hide actions from the user (negated — the text forbids it)offer the Yaps app workflow. Do not silently install it.
negated
Files scanned: 6. 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")
Process rating: all ten parameters 40/100
- 0Result and completion. Does not say what the result is
- 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
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 75Steps. 3 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 426 tokens
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
- +4No input/output examples
- +2Single-language instructions
- +3Description length 120: enough signal without eating the budget
- +4Structure: 3 headings
- +3Step-by-step instructions: 3 items
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.
External checks
ClawHub: suspicious
The skill is advertised for Yaps image generation, but its bundled runtime can also act as a broad Yaps CLI wrapper and exposes media transcription workflows.
LLM: suspicious (high) · 25 Sept 2026