CtrlK
BlogDocsLog inGet started
Tessl Logo

image-generator

Skill para geracao e adaptacao de assets visuais. Use quando o projeto precisar de hero image, background, ilustracao, icone, favicon, mascote ou derivacao de imagem existente sem destoar do app. Trigger em: "gerar imagem", "criar imagem", "hero image", "background image", "favicon png", "icone", "mascote", "illustration", "remover fundo", "transparent icon", "tauri icons".

57

Quality

67%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/17-image-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

This skill covers a broad scope of image generation workflows with useful model selection guidance and concrete CLI examples, but suffers significantly from verbosity and redundancy. Multiple sections restate the same core principle (analyze existing context first), pricing tables with specific dates will become stale, and the content that should be in referenced guide files is inlined. The workflow would benefit from consolidation into a single clear sequence with explicit validation steps.

Suggestions

Consolidate the 4+ sections that all say 'analyze existing context first' (Regra Mais Importante, Analise de Contexto Visual, Checklist, Responsabilidades) into a single concise checklist, cutting at least 30-40 lines.

Move the full model pricing table, provider alternatives, and pipeline details into the already-referenced `docs/skill-guides/image-generator-models.md` — keep only the decision tree and default rule in SKILL.md.

Add explicit validation checkpoints after image generation: e.g., 'Verify output dimensions match target', 'Confirm visual consistency with existing assets before saving to final path'.

Remove explanatory content Claude already knows (what types of assets are, what providers exist) and replace with a single unified workflow: Analyze → Decide mode → Generate → Validate → Save → Handoff.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~200+ lines. It over-explains concepts Claude already knows (what a hero image is, what a favicon is), includes lengthy pricing tables that will become stale, repeats the same ideas multiple times (e.g., 'analyze context first' appears in at least 4 different sections), and has significant redundancy between sections like 'Quando Usar', 'Responsabilidades', 'Regra Mais Importante', 'Analise de Contexto Visual', and 'Checklist Antes de Gerar'.

1 / 3

Actionability

The skill provides concrete CLI commands for `generate-image.mjs` with real flags and examples, plus a decision tree for model selection. However, much of the content is procedural guidance rather than executable steps — the checklist items are abstract questions rather than concrete actions, and there's no example of a complete end-to-end workflow with actual input/output. The referenced script and config files aren't provided in the bundle.

2 / 3

Workflow Clarity

The multi-model pipeline (iterate → validate → final) is a clear sequence, and the decision tree helps with model selection. However, there are no explicit validation checkpoints — no step says 'verify the generated image meets X criteria before proceeding' or provides error recovery guidance. The overall workflow across the many sections is fragmented and hard to follow as a coherent sequence.

2 / 3

Progressive Disclosure

The skill references external files appropriately (image-generator-models.md, models/image-models.json, various policies) and delegates favicon/OG/PWA to skill 36. However, the main file itself is a wall of content that should have been split — the full pricing table, model comparison, and provider alternatives could live in the referenced guide file. No bundle files are provided to verify the references exist.

2 / 3

Total

7

/

12

Passed

Description

100%

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

This is a strong skill description that clearly defines its scope (visual asset generation and adaptation), provides explicit trigger guidance with a dedicated trigger term list, and covers both what the skill does and when to use it. The bilingual trigger terms (Portuguese and English) broaden its matching capability. The description is concise yet comprehensive, with minimal fluff.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: hero image generation, background creation, illustration, icon/favicon generation, mascot creation, image derivation, and background removal. These are clearly defined visual asset tasks.

3 / 3

Completeness

Clearly answers both 'what' (generation and adaptation of visual assets including hero images, backgrounds, icons, favicons, mascots, illustrations) and 'when' (explicit 'Use quando' clause and a dedicated 'Trigger em' list with specific keywords).

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms in both Portuguese and English: 'gerar imagem', 'criar imagem', 'hero image', 'background image', 'favicon png', 'icone', 'mascote', 'illustration', 'remover fundo', 'transparent icon', 'tauri icons'. These are terms users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to visual asset generation and adaptation for app contexts. The specific triggers like 'hero image', 'favicon png', 'mascote', 'tauri icons' create a distinct niche unlikely to conflict with other skills such as code generation or document processing.

3 / 3

Total

12

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

9

/

11

Passed

Repository
felvieira/claude-skills-fv
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.