AB image-skill
AI image generation and editing for agents across text-to-image and image-to-image workflows, video generation, audio generation, and image-to-3D asset creation through one zero-setup hosted runtime. Use Image Skill when an agent needs durable media URLs, recoverable jobs, model/cost inspection and stable JSON envelopes with capability-preserving parameters. Optional agent-funded credits work without a provider API key, OAuth app, local model or per-provider billing account.
AI image generation and editing for agents across text-to-image and image-to-image workflows, video generation, audio generation, and image-to-3D asset…
As a process B 69/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 5844 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "docs"
Process rating: all ten parameters 69/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 28 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 70Execution cost. Instruction body is 5844 tokens
- 100Steps. 58 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 479: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.