Prepare media assets required by an existing OD Next plan. Reuse verified capabilities and suitable assets, acquire files, measure dimensions, and retrieve background job results while preserving required content, licensing constraints, and quality conditions.
Prepare required media inputs within an existing OD Next plan. Reuse capability evidence, acquire and measure assets efficiently, and resolve asynchronous jobs without removing required content or weakening quality standards.
od-next-media-inputs prepares images and other media required by an existing OD Next plan before the deliverable is created. It acquires assets, checks their dimensions, and retrieves asynchronous job results while preserving agreed requirements for purpose, subject, licensing, and dimensions. It reuses capabilities already verified as available and suitable user assets, and batches independent acquisition and measurement work.
Use it when multiple pages share an asset or when you need several assets and want to organize their acquisition status. It also helps with media generation running in the background: the work includes collecting finished results, rather than merely checking that a job was accepted.
This skill assumes an existing OD Next plan and follows the tools and permissions provided in that environment. It prohibits hotlinking assets and fabricating real subjects. Unavailable assets must follow the existing fallback or failure arrangements. Required assets and quality conditions cannot be removed to declare completion. No tool calls are permitted during contract_repair.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 20, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Use only when the current task needs media inputs. Reuse these instructions
while applicable; do not load them for tasks without asset work. Follow the
current route, stage, frozen plan, and delivery boundary. During
contract_repair, make no tool calls. Finish required input work before the
deliverable write that depends on it. Never label post-write artifact
inspection, rendering, validation, or repair as input preparation to bypass
ship-on-write.
Use the frozen asset requirements in the existing working context: purpose, subject, source/license constraints, geometry, reuse positions, and readiness. Reuse suitable user assets and the same asset across pages. Deduplicate work, not distinct subjects or required states. Do not add a new plan, manifest, approval step, or review Agent. Preserve every required asset and quality condition, including semantic fit, authenticity, licensing, local or inline references, and image geometry.
Decide each slot's route, and which libraries a stock search may use, with the Core imagery-by-type rule; it is the only source of those rules.
"$OD_NODE_BIN" "$OD_BIN" media stock-search --slots '[{"id":"hero","query":"black eyeglasses frame","width":1200,"orientation":"landscape"}]'.
Write queries in English with the subject first. The service follows configured channel priority,
tries each channel at most once within its attempt limit, ranks by alt text, and returns
each result. The wrapper downloads images into assets/stock/ and records
credits in assets/stock/credits.json. Provider keys stay on the server;
never ask the user to configure a stock-provider key.error, not_found,
or budget_exceeded, keep successful local files and use your available
web/image search tools for only the missing slots. This includes unavailable
service/login, API errors, rate limits and failed image downloads. Do not
call the stock tool again for those failed slots.Use only tools, model IDs, parameters, and permissions actually provided for this run. Reuse complete, valid capability results. Query only missing, truncated, or invalidated facts; refresh relevant facts when the environment, authorization, or an error changes the decision. A catalogue entry alone does not prove authorization or readiness. Do not guess tool/model names or expose credential values.
Classify failures before retrying:
Retry only when the change addresses the cause, the relevant state changes, or existing guidance permits retrying a temporary failure. Do not sacrifice required quality to reduce calls; bound stock photo search with its time budget.
When the tools support it and inputs are independent, batch search, fetch, download, format handling, and intrinsic width/height measurements. Preserve each item's result and failures; keep dependent requests ordered. Reuse valid measurements for unchanged files; after transformation, remeasure affected files before sizing their containers.
HTTP success and file/size probes do not prove semantic fit; decide it as the Core imagery rule describes, without reading images back into the conversation.
Retain each actual job ID, status, returned cursor, original response, and output location. Use only supported wait or batch operations. Submission and exit success alone do not prove an asset is ready. Stop polling a job after an explicit terminal result with complete output/error information; a failed or interrupted terminal result is not a usable asset. Continue necessary retrieval for running jobs, incomplete results, or new errors. Parse the saved response again instead of requesting it merely to change formatting.
Stop acquiring assets when all required slots satisfy their content and input conditions. If a required asset remains unavailable, follow the existing fallback/failure contract and preserve uncertainty; never declare completion just because fewer calls were made.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create a three-scene video composition in a retro pixel style using a Hyperframes HTML template. Customize titles, labels, and colors while preserving scene transitions, short scene durations, and repeatable animation timing.
Create and revise headlines, descriptions, and main text for paid social and search ads. Use it to develop ad copy options and refine wording through repeated rounds of revision.
Create a three-page editorial motion sequence with dark backgrounds, serif typography, staged text reveals, and chapter transitions. The result is a single HTML file suited to fashion-inspired storytelling and short visual presentations.
Inspect and test web pages through a browser automation command-line tool. Navigate, click, enter text, capture screenshots, and extract page details, with a focus on checking local OpenDesign previews and reviewing web app quality.
Plan an AI music album from its concept through lyric drafts, track order, and export. Intended for independent album experiments and brand soundtracks, with the full production workflow provided through a separately installed upstream bundle.
Create generative art, or images made with programmed rules, using p5.js. Fixed random seeds make each rendering reproducible, supporting procedural posters, still images that suggest motion, and studies of artistic frame composition.