AC image-outpainting
Extend an image beyond its original borders — uncrop, change aspect ratio, fill in what the camera didn't capture — built into Genspark, no API key and no external account. Turn a 1:1 portrait into a 16:9 banner, reveal a subject's full body, or widen a product shot, with the original subject and framing preserved. Runs on the Genspark sandbox via `gsk image_generation --model nano-banana-2`. Triggers on "extend image canvas", "outpaint this photo", "expand image scene", "widen image background", "uncrop", "change aspect ratio of an image", or any explicit ask to extend or expand an image past its edges.
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
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 · 0
✓ No critical or high findings
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 5 mutating operations with no state check
- 55Failures and branches. 1 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 27 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1749 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 611: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 27 items
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.