AC gpt-image-2-runcomfy
GPT Image 2 on RunComfy. GPT Image 2 (OpenAI ChatGPT Images 2.0) is the strongest text-rendering image model available — embedded text, logos, signage, multilingual typography, and high-fidelity layout. This skill calls GPT Image 2 through the RunComfy CLI: `runcomfy run openai/gpt-image-2/text-to-image` (or `/edit`). GPT Image 2 has 3 fixed sizes and supports up to 10 reference images on the GPT Image 2 edit endpoint. Triggers on "gpt image 2", "gpt-image-2", "ChatGPT Images 2", "ChatGPT Image 2", "OpenAI Image 2", "GPT Image", or any explicit ask to generate or edit with GPT Image 2.
GPT Image 2 on RunComfy.
As a process C 63/100 · Has gaps — weak spots: result and completion, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "displayName" - note
frontmatter-keyunknown frontmatter key "emoji" - note
frontmatter-keyunknown frontmatter key "homepage" - note
frontmatter-keyunknown frontmatter key "clawdis"
Process rating: all ten parameters 63/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 30 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3245 tokens
- 100Running it twice. No mutating operations
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 14 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (4 tags): a typed call is more reliable
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 592: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 30 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.