Skip to content

nexu-io/open-design / skills/library-curator

library-curator

Verified

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-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

  1. 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 a path — never invent a relPath that apply did not return.

algorithmic-artanthropics/skillsCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.Stars: 195kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode: the smallest change that fully solves the task, and a reply a busy human understands in one read. Use on any coding task (writing, fixing, refactoring, reviewing, choosing dependencies) and when the user says "ponytail", "be lazy", "simplest solution", "yagni", or complains about over-engineering or bloat. Levels: lite, full (default), ultra.Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-gainDietrichGebert/ponytailShow ponytail's measured savings (code, cost, speed) from the benchmark. One-shot display. Use for /ponytail-gain, "what does ponytail save", "ponytail impact".Stars: 192kUpdated Claude CodeCodexVerifiedInstall
ponytail-reviewDietrichGebert/ponytailQuality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.Stars: 192kUpdated Claude CodeCodexVerifiedInstall