library-curator

Search the OD Library (the global asset registry) and apply matching assets into the current project mid-task. Use when the user asks to reuse an image they captured/uploaded earlier, "pull a logo/screenshot from my library", or to find and drop a stored asset into the page being built.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

Concise, highly actionable content with concrete API examples and a clear recipe including a fallback for the main failure mode. Minor room to tighten the intro and add an explicit verification step on the apply result.

Dimension	Reasoning	Score
Conciseness	Largely lean with concrete endpoint/JSON examples and no padding of concepts Claude already knows, though the intro and "When to use" sections mildly restate the description's purpose.	4 / 5
Actionability	Fully executable: concrete endpoints, copy-paste-ready JSON request/response payloads, and an explicit recipe plus a hard guardrail ("never invent a relPath that apply did not return").	5 / 5
Workflow Clarity	A clear four-step recipe with an explicit empty-result fallback, but the validation is a guardrail rather than a distinct verify-step on the apply result.	4 / 5
Progressive Disclosure	A short single-file skill (~50 lines) with well-organized sections and no need for external references, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

82%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.

A strong description that clearly states its purpose and gives concrete, natural trigger phrases tied to a distinct niche. The only mild weakness is specificity, which names just two actions rather than a fuller action set.

Dimension	Reasoning	Score
Specificity	Names the domain (OD Library) and two concrete actions ("Search" and "apply matching assets"), but coverage is limited to those two rather than comprehensive.	3 / 5
Completeness	Explicitly states what it does ("Search the OD Library... and apply matching assets into the current project mid-task") and when to use it with concrete trigger phrases ("Use when the user asks to reuse an image...").	5 / 5
Trigger Term Quality	Includes natural user phrases like "pull a logo/screenshot from my library" and "reuse an image they captured/uploaded earlier" with good synonym coverage, though not exhaustive on extensions/variations.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (the OD Library asset registry) with triggers scoped to library assets, minimizing overlap with generic image-generation or insert-image skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: nexu-io/open-design
Path: skills/library-curator/SKILL.md
Commit: df84ae5

Reviewed: ~17 hours ago

Table of Contents

Discovery Implementation Validation

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.