asset-librarian
Skill para inventariar e organizar imagens, icones, logos, fontes, tokens visuais e referencias graficas do projeto. Use quando precisar mapear assets existentes, evitar inconsistencias visuais e apoiar UI/UX, Frontend e Image Generator.
76
Quality
69%
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/19-asset-librarian/SKILL.mdQuality
Discovery
82%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 solid skill description that clearly communicates its purpose for visual asset inventory and organization. It has good trigger term coverage in Portuguese and includes an explicit 'Use when' clause. The main weakness is that the action verbs are somewhat generic ('inventariar', 'organizar', 'mapear') rather than describing specific concrete operations the skill performs.
Suggestions
Add more specific concrete actions like 'catalog asset file paths', 'detect duplicate assets', 'generate asset inventory reports', or 'validate asset naming conventions' to improve specificity.
Consider adding file type triggers (.png, .svg, .ico, .ttf, .woff) to further distinguish from general design or organization skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (visual assets) and lists types of assets (images, icons, logos, fonts, visual tokens, graphic references), but actions are somewhat vague - 'inventariar e organizar' (inventory and organize) and 'mapear' (map) are general verbs without concrete specifics like 'catalog file paths', 'generate asset reports', or 'detect duplicates'. | 2 / 3 |
Completeness | Clearly answers both what (inventory and organize images, icons, logos, fonts, visual tokens, graphic references) AND when (explicit 'Use quando' clause specifying mapping existing assets, avoiding visual inconsistencies, and supporting UI/UX, Frontend, and Image Generator work). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'imagens', 'icones', 'logos', 'fontes', 'tokens visuais', 'referencias graficas', 'assets', 'UI/UX', 'Frontend', 'Image Generator'. These are terms designers and developers naturally use when discussing visual assets. | 3 / 3 |
Distinctiveness Conflict Risk | Reasonably specific to visual asset management, but could overlap with general design system skills, UI component libraries, or image processing skills. The mention of 'Image Generator' support adds some distinction, but 'organizar' is broad enough to potentially conflict with other organizational skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise, with good use of external references for governance and templates. However, it lacks actionable guidance—there are no concrete commands, code snippets, or step-by-step instructions for actually performing the asset inventory. It reads more like a specification than an executable skill.
Suggestions
Add concrete commands or code examples for scanning asset directories (e.g., using find, glob, or a script to list images/fonts)
Include a step-by-step workflow with numbered actions: 1. Scan directories, 2. Extract metadata, 3. Generate inventory, 4. Validate completeness
Provide an example of what the output file (docs/repo-audit/assets.md) should look like with sample content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points and minimal prose. It assumes Claude understands concepts like design tokens, favicons, and visual identity without explanation. | 3 / 3 |
Actionability | The skill provides no concrete code, commands, or executable examples. It describes what to do ('mapear imagens', 'inventario visual') but never shows how to actually scan directories, extract metadata, or generate the inventory file. | 1 / 3 |
Workflow Clarity | The skill lists inputs, outputs, and persistence location, providing implicit sequence. However, there are no explicit numbered steps, validation checkpoints, or feedback loops for the inventory process. | 2 / 3 |
Progressive Disclosure | The skill appropriately references external policies and templates (GLOBAL.md, policies/, templates/asset-inventory.md) with clear one-level-deep navigation. Content is well-organized into logical sections. | 3 / 3 |
Total | 9 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- felvieira/claude-skills-fv
- Commit
524725e
- 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.