CD gpt-image
Generate or edit images with GPT Image 2 or 2.5 through the packaged CLI and Reference Gallery. Use for image requests including imprecise 'GPT 2.5' model names, posters, typography, reference edits, and inpainting; resolve the model choice before generation.
Generate or edit images with GPT Image 2 or 2.5 through the packaged CLI and Reference Gallery. Use for image requests including imprecise 'GPT 2.5' model…
As a process D 47/100 · Unfinished process — References files that are not bundled: references/gallery-*.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The text contains phrases like "ignore previous instructions" or "you are now…". That is an attempt to hijack the agent: it may break your rules, the system limits or company policy.
An honest skill does not need them: state the role and the rules directly without overriding other instructions. Otherwise catalog scanners and corporate filters will block the listing.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The files contain invisible characters, encoded commands or comments hidden from readers but visible to the model. What you read differs from what the agent sees.
Remove invisible characters (they usually sneak in through copy-paste) and encoded strings: no catalog will pass them. Instructions for the model must be readable by a human too.
How to improve
- The text references files that are not there: add them or drop the references.
- 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 · 4
✓ No critical or high findings
Medium and low: 4
-
medium Instruction override
en-ignore-previousreferences/craft.md:161Instruction-override phrase ("ignore previous instructions") (detector / deny-list definition)- If illustrating prompt injection, quote the payload visibly as a harmless example string such as `<!-- IGNORE previous instructions... -->`, then label it `injected instructions` / `payload`.
detector -
medium Obfuscation
obf-html-comment-instructionreferences/craft.md:161Hidden instruction inside an HTML comment (detector / deny-list definition)- If illustrating prompt injection, quote the payload visibly as a harmless example string such as `<!-- IGNORE previous instructions... -->`, then label it `injected instructions` / `payload`.
detector -
low Instruction override
en-ignore-previousreferences/gallery-research-paper-figures.md:400Instruction-override phrase ("ignore previous instructions") (security demo / example; quoted — discussed, not commanded)COLUMN 3 "Third-party content (attack surface)": stacked boxes "Public Slack message" (slate gray), "Web page" (slate gray), and "Attacker-controlled document" (soft-terracotta fill, dashed border) co
demoquoted -
low Obfuscation
obf-html-comment-instructionreferences/gallery-research-paper-figures.md:400Hidden instruction inside an HTML comment (security demo / example; quoted — discussed, not commanded)COLUMN 3 "Third-party content (attack surface)": stacked boxes "Public Slack message" (slate gray), "Web page" (slate gray), and "Attacker-controlled document" (soft-terracotta fill, dashed border) co
demoquoted
Files scanned: 44. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/gallery-*.md
Process rating: all ten parameters 47/100
- 0Tools and files. 1 referenced file(s) missing: references/gallery-*.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 3 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 85Steps. 36 steps, 1 vague phrases
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2397 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
- +1No license
- +2Single-language instructions
- +3Description length 259: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 36 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (10 of 41)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.