AC poyo-seedream-5-pro
Seedream 5.0 Pro image generation and editing on PoYo / poyo.ai via `https://api.poyo.ai/api/generate/submit`; use for `seedream-5.0-pro`, `seedream-5.0-pro-edit`, text-to-image, reference-image editing, 1K or 2K output, aspect-ratio control, and multi-image output.
Seedream 5.0 Pro image generation and editing on PoYo / poyo.ai via https://api.poyo.ai/api/generate/submit; use for seedream-5.0-pro, seedream-5.0-pro-edit…
As a process C 52/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches
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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
net-credential-usereferences/api.md:12Credential used in a network call (verify the destination is the intended service) (the skill's own vendor host; quoted — discussed, not commanded)Send `Authorization: Bearer $POYO_API_KEY` and `Content-Type: application/json`. Create or manage a key at <https://poyo.ai/dashboard/api-key>.
vendor-hostquoted
Files scanned: 4. 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 52/100
- 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. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) 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 695 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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 266: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 27 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 90.