CtrlK
BlogDocsLog inGet started
Tessl Logo

image-generation

Generate or refine one image with Kun's image tool using explicit composition and authorized references.

61

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./resources/bundled-skills/image-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 well-structured, brief instruction-only skill with clear sequencing, explicit completion gates, and sensible boundaries. The main gap is execution-level detail: without an example generate_image call, available aspect ratios, or reference-attachment mechanics, Claude must fill in how to actually invoke the tool.

Suggestions

Add a short example generate_image invocation showing the key parameters (prompt, aspect_ratio, reference images) so the guidance is copy-paste executable.

List the available aspect ratios (or how to discover them) in the workflow step that currently just says to "choose an aspect ratio that matches the destination".

Specify what makes a reference "authorized" (current-thread attachment vs. workspace file) and how to attach one, since this is referenced in both the workflow and boundaries.

DimensionReasoningScore

Conciseness

The body is lean — a compact tool-routing table, a 5-step workflow, and short gate/boundary sections with no explanation of concepts Claude already knows. Minor trimmable redundancy remains: the "Purpose" section restates the frontmatter description verbatim, and "Delivery" is generic boilerplate, so it sits just below the every-token-earns-its-place level 5.

4 / 5

Actionability

Guidance is partially concrete — named tools ("generate_image", "read"), the image_size/1K-2K rule, and the dimension checklist for translating a request — but key execution details are missing: no example tool invocation, no list of available aspect ratios, and no specifics on how reference images are attached or what makes a reference "authorized". This places it at "some concrete guidance but incomplete" rather than the mostly-executable level 4.

3 / 5

Workflow Clarity

The workflow is a clearly sequenced 5-step process with an explicit validation checkpoint ("Inspect the result" plus the "Completion gates" checklist covering faces, hands, text, logos, geometry, and cropping) and a built-in feedback loop ("refine only when necessary or requested"). It is not level 4 because the validation steps are explicit rather than merely implied, and the operation is neither destructive nor batch, so no cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files (no references/, scripts/, or assets/ directories exist), and needs no external references, so the simple-skill exception applies: well-organized sections (Purpose, Tool routing, Workflow, Completion gates, Boundaries, Delivery) with every part of the task covered inline merit a 5.

5 / 5

Total

17

/

20

Passed

Description

66%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 concrete and clean — it names the tool, the single-image constraint, and the composition/reference model without any fluff. Its main weakness is the complete absence of a "when to use" trigger clause, which both caps completeness and slightly raises conflict risk with similarly-scoped image skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create, edit, or refine a single image."

Include natural synonyms users would say — "create", "edit", "photo", "picture" — to broaden trigger coverage.

Optionally mention what refinement covers (e.g., adjusting composition, style, or identity from a reference image) to sharpen the what.

DimensionReasoningScore

Specificity

"Generate or refine one image with Kun's image tool using explicit composition and authorized references" lists several concrete capabilities — generation, refinement, composition control, and reference-based editing — with only minor gaps (no mention of aspect ratio, size, or text rendering). It falls below the level-5 anchor, which expects comprehensive multi-action coverage, but clearly exceeds the 1–2-action scope of level 3.

4 / 5

Completeness

The "what" is clear (generate or refine one image with explicit composition and authorized references via Kun's image tool), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. This is not level 2 because the "what" is concrete rather than vague, and not level 4 because "when" is entirely absent rather than just under-specified.

3 / 5

Trigger Term Quality

Natural terms users would say include "generate", "image", "refine", and "references", giving good keyword coverage. A few common variations are missing (e.g., "create", "edit", "draw", "photo", "picture"), so it does not reach the comprehensive synonym coverage of level 5, but it is well above the sparse coverage of level 3.

4 / 5

Distinctiveness Conflict Risk

Scoping to "Kun's image tool" and "exactly one image" with composition and reference constraints carves out a mostly distinct niche. Minor overlap risk remains with other image-generation/editing skills since the description shares generic image vocabulary and offers no trigger context to disambiguate, keeping it below the minimal-conflict level 5.

4 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
KunAgent/Kun
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.