library-curator by nexu-io

Decision brief

What it does—and where it fits

Reuse assets that already live in the user's OD Library — images captured with the OD Clipper, manual uploads, agent-generated media, and design-system material — without asking the user to re-upload them.

Best for

The user references an asset they already have ("the screenshot I clipped",
You need an image for the page you're building and the user prefers their own

Not for

Tasks that require unconfirmed production actions or broad system permissions.
Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

Platform	Status	Evidence	What to check
Codex	Not declared	No explicit evidence	Portability before use
Claude Code	Not declared	No explicit evidence	Portability before use
Cursor	Not declared	No explicit evidence	Portability before use
Gemini CLI	Not declared	No explicit evidence	Portability before use

Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource

npx skills add https://github.com/nexu-io/open-design --skill "skills/library-curator"

Safe inspection promptEditorial

Inspect the Agent Skill "library-curator" from https://github.com/nexu-io/open-design/blob/89d6d4ef21baf80f871595abdf6f7de6e941dd44/skills/library-curator/SKILL.md at commit 89d6d4ef21baf80f871595abdf6f7de6e941dd44. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

01
When to use
The user references an asset they already have ("the screenshot I clipped",
The user references an asset they already have ("the screenshot I clipped",You need an image for the page you're building and the user prefers their own- The user references an asset they already have ("the screenshot I clipped", "my logo", "that hero image from earlier"). - You need an image for the page you're building and the user prefers their own library over fres…
02
Tools (tool-token track)
Both endpoints authenticate with the run's tool token (ODTOOLTOKEN, injected by the daemon) and operate on the project the run belongs to.
Both endpoints authenticate with the run's tool token (ODTOOLTOKEN, injected by the daemon) and operate on the project the run belongs to.POST /api/tools/library/searchReturns { "results": [{ "asset": { "id": "...", "kind": "image", "sourceTitle": "...", "width": 1600, "height": 900, "sources": [...] }, "score": 0 }], "semantic": false }.
03
Search
POST /api/tools/library/search
POST /api/tools/library/searchReturns { "results": [{ "asset": { "id": "...", "kind": "image", "sourceTitle": "...", "width": 1600, "height": 900, "sources": [...] }, "score": 0 }], "semantic": false }.semantic: false means keyword/metadata matching (no embedding model configured). Filter and rank the results yourself from the asset metadata.
04
Apply
POST /api/tools/library/apply
POST /api/tools/library/applyCopies the asset into the project (default subdir library/, or the dir you pass) and returns { "relPath": "assets/.png" }. Reference that relPath from the HTML/CSS you write (e.g. ).

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial

Signal	Value	Evidence type	Meaning
Quality score	81/100	Computed	Documentation, specificity, maintenance, and trust rules
Repository stars	82,073	Source	Repository attention, not individual Skill quality
Compatibility	0 platforms	Source	Declared in the catalog source record
Usage guide	automated source guide	Editorial	Generated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository: nexu-io/open-design
Skill path: skills/library-curator/SKILL.md
Commit: 89d6d4ef21baf80f871595abdf6f7de6e941dd44
License: Apache-2.0
Collected: 2026-07-28
Default branch: main

View the original SKILL.md

library-curator

Reuse assets that already live in the user's OD Library — images captured with the OD Clipper, manual uploads, agent-generated media, and design-system material — without asking the user to re-upload them.

When to use

The user references an asset they already have ("the screenshot I clipped", "my logo", "that hero image from earlier").
You need an image for the page you're building and the user prefers their own library over freshly generated media.

Tools (tool-token track)

Both endpoints authenticate with the run's tool token (OD_TOOL_TOKEN, injected by the daemon) and operate on the project the run belongs to.

Search

POST /api/tools/library/search

{ "query": "blue hero background", "kind": "image", "limit": 20 }

Returns { "results": [{ "asset": { "id": "...", "kind": "image", "sourceTitle": "...", "width": 1600, "height": 900, "sources": [...] }, "score": 0 }], "semantic": false }.

semantic: false means keyword/metadata matching (no embedding model configured). Filter and rank the results yourself from the asset metadata.

Apply

POST /api/tools/library/apply

{ "assetId": "<id from search>", "dir": "assets" }

Copies the asset into the project (default subdir library/, or the dir you pass) and returns { "relPath": "assets/<hash>.png" }. Reference that relPath from the HTML/CSS you write (e.g. <img src="assets/ab12cd34ef.png">).

Recipe

Search with a tight query for the kind you need.
Pick the best result by dimensions / title / source.
Apply it to get a project-relative path.
Wire that path into the artifact you're editing.

If search returns nothing, fall back to media generation rather than guessing a path — never invent a relPath that apply did not return.