Best fit
- 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
nexu-io/open-design
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.
81Collecting
See how to use itView GitHub source
npx skills add https://github.com/nexu-io/open-design --skill "skills/library-curator"Automated source guideGeneral workflowStandard source
Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Source-grounded usage guide: 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.
npx skills add https://github.com/nexu-io/open-design --skill "skills/library-curator"The pinned source supports a structured brief, but not an expanded tutorial. Only detected inputs, outputs, and sections are shown.
259 source words · 5 usable sections
Source workflow
Read library-curator through these 4 source sections
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
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…
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 }.
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.
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. ).
Source checklist
Verify each item before delivery
The source section “When to use” has been checked.
The source section “Tools (tool-token track)” has been checked.
The source section “Search” has been checked.
The source section “Apply” has been checked.
FAQ
What does the library-curator source document cover?
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.
How do I install library-curator?
The source record exposes this install command: npx skills add https://github.com/nexu-io/open-design --skill "skills/library-curator". Inspect the command and pinned source before running it.
Repository stars
82,073
Repository forks
9,485
Quality
81/100
Source repository last pushed
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Documentation26/30
Specificity23/25
Maintenance20/20
Trust signals12/25
View original Skill.mdThis page is parsed directly from the repository SKILL.md without editorial rewriting. Collected: Jul 28, 2026 · about 2 min
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.
- Source repo
- nexu-io/open-design
- Skill path
- skills/library-curator/SKILL.md
- Commit SHA
- 89d6d4ef21ba
- Repository license
- Apache-2.0
- Data collected