CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable skill body with genuinely strong workflow sequencing and validation, undermined by repetition and by inlining fallback-CLI detail that the bundle already stores in reference files. The structure and navigation are good, but token budget is not respected as tightly as the content quality deserves.

Suggestions

State the gpt-image-1.5/true-transparency escalation rule once (e.g., in the Top-level modes rules) and reference it from the Workflow and Transparent image requests sections instead of repeating the full rationale four times.

Move the gpt-image-2 quality values, size constraints, and popular sizes list into references/image-api.md (which already documents them), keeping only the model default and a pointer in SKILL.md.

Move the Fallback CLI dependencies, environment, and OPENAI_API_KEY setup steps into references/cli.md, leaving a one-line pointer since the skill already instructs not to enter CLI mode without explicit user request.

DimensionReasoningScore

Conciseness

The body is mostly operational instruction, but the gpt-image-1.5 transparency warning is repeated nearly verbatim in at least four places ("Never silently switch from built-in image_gen...", "If this path looks unsuitable or fails, ask before switching to CLI gpt-image-1.5", "true transparency requires the CLI fallback with gpt-image-1.5", "use the built-in-first chroma-key workflow unless...") and the inline "gpt-image-2 guidance for CLI fallback" section (quality values, size constraints, popular sizes) duplicates content that already exists in references/image-api.md and references/cli.md. It is noticeably tighter than anchor 2 because almost everything is concrete skill-specific policy rather than concept explanation or padding, but the repetition and inline CLI detail keep it below anchor 4's 'minor instances that could be trimmed'.

3 / 5

Actionability

Fully executable guidance throughout: a copy-paste bash invocation with exact flags ("--auto-key border --soft-matte --transparent-threshold 12 --opaque-threshold 220 --despill"), verbatim prompt templates for chroma-key generation and user confirmation, exact install commands ("uv pip install openai"), explicit size constraints and API-key setup steps, and concrete validation criteria ("alpha channel, transparent corners, plausible subject coverage, no key-color fringe"). This matches anchor 5's copy-paste-ready commands covering common cases.

5 / 5

Workflow Clarity

An 18-step workflow with explicit sequencing, plus a dedicated transparent-image sequence that includes a validation checkpoint ("Validate that the output has an alpha channel, transparent corners...") and an error-recovery loop ("If a thin fringe remains, retry once with --edge-contract 1") and iteration policy ("Iterate with a single targeted change, then re-check"). The destructive/batch cap does not apply: batch and edit operations have validation steps ("Inspect outputs and validate: subject, style, composition, text accuracy, and invariants"), non-destructive save rules, and a no-overwrite/versioned-filename policy. This matches anchor 5's explicit validation with feedback loops.

5 / 5

Progressive Disclosure

A clear closing "Reference map" labels every bundle file as shared or "fallback-only" ("references/cli.md: fallback-only CLI usage via scripts/image_gen.py"), all referenced paths exist (references/prompting.md, sample-prompts.md, cli.md, image-api.md, codex-network.md, scripts/image_gen.py), and cross-references between reference files are peer navigation links rather than chained indirection, so depth is one level. It falls short of anchor 5 because meaningful fallback-only content (gpt-image-2 quality/size tables, dependency installation, environment/key setup) is inlined in SKILL.md instead of deferred to the existing reference files — more than the 'minor organization gaps' of anchor 4 would allow as a 5.

4 / 5

Total

17

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete capabilities, explicit use/non-use triggers, and clear boundaries against vector/code-native alternatives. The only gap is modest coverage of common user synonyms and file extensions.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "Generate or edit raster images", "create a brand-new image, transform an existing image, or derive visual variants from references" — which comprehensively covers the skill's actual capabilities. Not 4: unlike 'minor gaps in coverage', every operation mode of the skill (generate, edit, variant derivation) is explicitly named with concrete object types (photos, illustrations, textures, sprites, mockups, transparent-background cutouts).

5 / 5

Completeness

It explicitly answers both questions with concrete triggers: what ("Generate or edit raster images... bitmap visuals") and when ("Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references"), plus explicit negative triggers ("Do not use when the task is better handled by editing existing SVG/vector/code-native assets..."). This matches anchor 5's 'clearly and explicitly answers both what AND when'.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "photos, illustrations, textures, sprites, mockups", "transparent-background cutouts", "brand-new image", "transform an existing image". A few natural terms users would say are missing — e.g. "picture", "render", "AI image", and file extensions like .png/.jpg — so it falls between anchor 4 and anchor 5, closer to 4.

4 / 5

Distinctiveness Conflict Risk

A clear niche (AI-created bitmap assets) with explicit boundary carving against the nearest competing skills: "Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas." This matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

jscraik/Agent-Skills

Path

skills-system/imagegen/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.