CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

image-generation

Generate images from text prompts (and optionally edit/remix input images). Use when the user asks to create, generate, draw, render, or edit an image, illustration, logo, icon, diagram, slide, photo, animated GIF, or SVG.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Medium

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a strong, highly actionable API guide with executable examples for every major flow and concrete error-recovery guidance. Its main weaknesses are structural: everything lives in one long SKILL.md with advanced provider-specific material that belongs in reference files, plus some duplicated and generic guidance that could be trimmed.

Suggestions

Move the OpenAI GPT Image 2.6 specialty sections (Animated GIF, SVG, Markup-guided edits) into a references/ file such as references/openai-gpt-image.md, keeping a one-line pointer plus the default-model choice in SKILL.md — this addresses both the progressive_disclosure and conciseness gaps.

Deduplicate provider/model guidance: the provider table's "Use for" column and the immediately following prose paragraph ("Default to `flux`... Use `gemini`... Use `openai`...") say the same thing; keep only one, and do the same for `quality`/`complexity` which are explained in both the request-body table and the OpenAI section.

Tighten the Prompting section by cutting generic image-prompting advice Claude already knows (e.g., "Describe what's visible. Materials, lighting, colors, medium, framing, texture") and retaining only the workflow-specific directives (preserve-lists for edits, numbered reference-image roles, exact-text-in-quotes rules).

DimensionReasoningScore

Conciseness

The body is dense with non-obvious, API-specific detail (endpoint, auth env vars, request fields, error codes) and largely avoids teaching known concepts, so it is efficient overall. It is not a 5 because of trimmable material: the provider-selection prose after the table repeats the table's "Use for" column, the `quality`/`complexity` fields are explained in both the request-body table and the OpenAI section, and a few prompting items (e.g., "Describe what's visible. Materials, lighting, colors...") state generic image-prompting knowledge.

4 / 5

Actionability

The main example is fully executable end-to-end (curl call, base64/URL handling, file save), and the edit/data-URL one-liner and PIL markup-overlay script are copy-paste ready. Concrete examples cover the common cases (text-to-image, edit/remix, region-marked edit), matching the anchor-5 standard.

5 / 5

Workflow Clarity

The core sequence (generate, save locally, embed inline) is explicit with branching for b64_json vs. signed URL, error-code handling (402/400/500), and useful verification prompts ("Compare the edit with the original", "reduce the frame count or size" on GIF rejection). It is not a 5 because validation is scattered as prose rather than explicit checkpoints — e.g., no step to confirm the response succeeded before saving or to verify the written file.

4 / 5

Progressive Disclosure

Section headers are clear and navigation within the file is easy, but the skill is a ~250-line monolith with no bundle files: the OpenAI GPT Image 2.6 specialty subsections (Animated GIF, SVG, Markup-guided edits, ~80 lines) and the general prompting guide are separable advanced content inlined in SKILL.md. This matches anchor 3 ("content that should be separate is inline") rather than anchor 4, since no references exist at all and the under-50-line self-contained exception does not apply.

3 / 5

Total

16

/

20

Passed

Description

95%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.

The description is exemplary: a concise third-person statement of capability followed by an explicit, comprehensive trigger clause covering how users naturally phrase image requests. The only weakness is that supported outputs like animated GIFs and SVGs are surfaced as triggers rather than stated capabilities, leaving slightly incomplete action coverage.

DimensionReasoningScore

Specificity

"Generate images from text prompts (and optionally edit/remix input images)" names several concrete actions (generate, edit, remix), comparable to the anchor-4 example. It is not a 5 because capability coverage has minor gaps — animated GIF and SVG output are supported per the body but appear only as trigger nouns, not stated capabilities.

4 / 5

Completeness

It explicitly answers both questions: the "what" is "Generate images from text prompts (and optionally edit/remix input images)" and the "when" is an explicit "Use when" clause with concrete trigger phrases. This matches the anchor-5 example structure exactly; anchor 4 would require the when-clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

"Use when the user asks to create, generate, draw, render, or edit an image, illustration, logo, icon, diagram, slide, photo, animated GIF, or SVG" comprehensively covers the natural verbs and object synonyms users actually say. Anchor 4 would apply if natural terms were missing, but the verb list (create/generate/draw/render) and noun list (image/photo/illustration/logo/icon/SVG) leave no common phrasing uncovered.

5 / 5

Distinctiveness Conflict Risk

Image generation is a clear niche with distinct image-creation verbs (create, generate, draw, render) applied to visual-output nouns, giving minimal conflict risk with other skills. The closest overlap ("diagram", "slide") is still qualified as image output, so it does not rise to the anchor-4 "minor overlap risk" level.

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

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

letta-ai/letta-code

Path

src/skills/builtin/image-generation/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.