How do I install the Library Curator skill?

Run npx skillmds@latest add mhassan0000/library-curator in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Library Curator safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Library Curator?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Library Curator free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Library Curator?

MHassan0000 (@mhassan0000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Library Curator by mhassan0000 — Agent Skill

Name: Library Curator
Rating: 4.5 (4 reviews)
Author: MHassan0000

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.

MHassan0000 Updated Sep 8, 2026 1 repo stars

File contents

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.

---name: library-curatordescription: 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.---# library-curatorReuse assets that already live in the user's OD Library — images captured withthe OD Clipper, manual uploads, agent-generated media, and design-systemmaterial — 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`, injectedby the daemon) and operate on the project the run belongs to.### Search`POST /api/tools/library/search````json{ "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 modelconfigured). Filter and rank the results yourself from the asset metadata.### Apply`POST /api/tools/library/apply````json{ "assetId": "<id from search>", "dir": "assets" }```Copies the asset into the project (default subdir `library/`, or the `dir` youpass) and returns `{ "relPath": "assets/<hash>.png" }`. Reference that`relPath` from the HTML/CSS you write (e.g. `<img src="assets/ab12cd34ef.png">`).## Recipe1. Search with a tight query for the kind you need.2. Pick the best result by dimensions / title / source.3. Apply it to get a project-relative path.4. Wire that path into the artifact you're editing.If search returns nothing, fall back to media generation rather than guessing apath — never invent a `relPath` that `apply` did not return.

Frequently asked questions