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", "icone", "mascote", "illustration", "remover fundo", "transparent icon", "tauri icons".
78
Quality
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/17-image-generator/SKILL.mdQuality
Discovery
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 excels across all dimensions. It provides specific asset types, explicit trigger guidance with a dedicated 'Trigger em:' section, and clear context about when to use it (app visual assets). The bilingual trigger terms (Portuguese and English) enhance discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'hero image, background, ilustracao, icone, favicon, mascote ou derivacao de imagem existente'. Also mentions specific use case 'sem destoar do app' (without clashing with the app). | 3 / 3 |
Completeness | Clearly answers both what ('geracao e adaptacao de assets visuais' with specific asset types) AND when ('Use quando o projeto precisar de...' plus explicit 'Trigger em:' section with specific keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'gerar imagem', 'criar imagem', 'hero image', 'background image', 'favicon', 'icone', 'mascote', 'illustration', 'remover fundo', 'transparent icon', 'tauri icons'. Includes both Portuguese and English variations. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on visual assets for apps with distinct triggers like 'favicon', 'mascote', 'tauri icons', 'hero image'. Unlikely to conflict with general image or document skills due to specific app-context framing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid conceptual guidance for image generation with good organizational structure and clear integration points with other skills. However, it lacks concrete executable examples (actual prompts, commands, or code), and the workflow could benefit from explicit validation checkpoints. The content is moderately efficient but includes some redundant or misplaced sections.
Suggestions
Add 2-3 concrete prompt examples showing before/after for t2i and i2i modes with actual prompt text
Include explicit validation steps after generation (e.g., 'verify asset matches palette using X method' or 'check dimensions before committing')
Remove or relocate the 'Codigo Limpo' section which doesn't fit this skill's purpose
Add a concrete example of the handoff output format showing actual paths, prompts, and metadata structure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some redundant sections (e.g., 'Quando Usar' and 'Quando Nao Usar' could be tighter, 'Codigo Limpo' section at the end seems out of place). The governance references at the top add overhead without immediate value. | 2 / 3 |
Actionability | Provides good conceptual guidance with checklists and tables, but lacks concrete executable examples. No actual prompt templates, no code snippets for image generation commands, and no specific tool invocations are shown. | 2 / 3 |
Workflow Clarity | The 'Analise de Contexto Visual' section provides a clear sequence, and there's a checklist before generation. However, there are no explicit validation steps or feedback loops for verifying generated assets meet requirements before finalizing. | 2 / 3 |
Progressive Disclosure | References external policies and templates appropriately, but the skill itself is somewhat monolithic. The content could benefit from splitting detailed sections (like model selection criteria or prompt rules) into separate reference files. | 2 / 3 |
Total | 8 / 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
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 | |
524725e
Table of Contents
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.