CtrlK
BlogDocsLog inGet started
Tessl Logo

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. Trigger em: "asset librarian", "inventariar assets", "inventario de assets", "mapear assets", "organizar assets", "design tokens", "biblioteca de assets", "auditar assets visuais", "catalogar logos", "incoerencia visual".

55

Quality

61%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/19-asset-librarian/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 well-crafted skill description that clearly defines its scope (inventorying and organizing visual assets), specifies when to use it (mapping existing assets, avoiding visual inconsistencies), and provides an extensive list of explicit trigger terms. It uses third person voice appropriately and carves out a distinct niche that differentiates it from related UI/UX or frontend skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: inventariar, organizar imagens, icones, logos, fontes, tokens visuais, referencias graficas. Also specifies the types of assets handled (images, icons, logos, fonts, design tokens, graphic references).

3 / 3

Completeness

Clearly answers both 'what' (inventariar e organizar imagens, icones, logos, fontes, tokens visuais e referencias graficas) and 'when' (explicit 'Use quando' clause with specific scenarios like mapping existing assets, avoiding visual inconsistencies, supporting UI/UX/Frontend). Also includes explicit trigger terms.

3 / 3

Trigger Term Quality

Provides an explicit list of natural trigger terms covering multiple variations users would say: 'asset librarian', 'inventariar assets', 'mapear assets', 'organizar assets', 'design tokens', 'biblioteca de assets', 'auditar assets visuais', 'catalogar logos', 'incoerencia visual'. Good coverage of both Portuguese and English terms.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche focused on asset inventory and visual consistency auditing. The specific trigger terms like 'asset librarian', 'inventario de assets', 'auditar assets visuais' are distinctive and unlikely to conflict with general design, frontend, or image generation skills.

3 / 3

Total

12

/

12

Passed

Implementation

22%

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

This skill reads as a metadata/governance document rather than an actionable skill. It defines when to use the skill, what inputs/outputs to expect, and where to persist results, but completely lacks concrete steps, commands, examples, or templates showing Claude how to actually perform an asset inventory. The absence of any executable guidance or workflow sequencing severely limits its utility.

Suggestions

Add a concrete step-by-step workflow: e.g., 1) Scan directory tree for image/font/icon files, 2) Extract design tokens from config files, 3) Catalog findings into the inventory template, 4) Validate completeness against a checklist.

Provide an example of the expected output format for `docs/repo-audit/assets.md` — even a minimal template showing the markdown structure with sections for logos, icons, fonts, tokens, and inconsistencies.

Include concrete commands or code snippets for discovering assets (e.g., `find . -type f \( -name '*.svg' -o -name '*.png' \)` or glob patterns to scan for design token files).

Add a validation/verification step to confirm inventory completeness, such as cross-referencing discovered files against what's cataloged.

DimensionReasoningScore

Conciseness

The content is moderately efficient but includes sections like 'Quando Usar' vs 'Quando Nao Usar' and 'Governanca Global' that add bulk without much actionable value. Some sections (e.g., 'Entradas Esperadas') state the obvious given the skill description.

2 / 3

Actionability

The skill provides no concrete commands, code, scripts, or executable steps. It describes what should be done ('mapear imagens', 'persistir em docs/repo-audit/assets.md') but never shows how — no file-scanning commands, no example inventory format, no template structure, no tool usage patterns.

1 / 3

Workflow Clarity

There is no sequenced workflow at all. The skill lists inputs, outputs, and persistence locations but never defines a step-by-step process for performing the inventory. There are no validation checkpoints or feedback loops for catching missed assets or verifying completeness.

1 / 3

Progressive Disclosure

The skill references external policies (GLOBAL.md, policies/execution.md, etc.) and a template (templates/asset-inventory.md), which is good structure. However, no bundle files are provided to verify these exist, and the main content itself lacks enough substance to serve as a useful overview — it's more of a metadata stub than a navigable entry point.

2 / 3

Total

6

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

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.