npx skills add smithery/embassy-of-the-free-mind --skill library-curator
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.
Installation
npx skills add nexu-io/open-design --skill library-curator
Similar popular skills
Related neighbors and high-traction skills in the same topics — useful to compare before installing.
Guidance for distinctive, intentional visual design when building new UI or reshaping an existi…
866.4K installsBrowser automation CLI for AI agents. Use when the user needs to interact with websites, includ…
810.4K installsReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "chec…
617.3K installsBuild, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and …
576.5K installsDebug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe …
568.9K installsAlso in this package
Other skills from nexu-io/open-design · top by installs.
npx skills add nexu-io/open-design
More details
Agent compatibility
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
Also listed on
Alternate registries and mirrors of this skill.
Repository health
main
Package contents
Files included with this skill beyond the listing page.
-
skill md
SKILL.md2,301 B -
docs
SUMMARY.md310 B
History
- First seen on skills.sh
- First recorded snapshot · 672 installs
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 (ODTOOLTOKEN, 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.