agentleFS
danielgwilsondanielgwilson/luxin/skills/creative-media/SKILL.md

creative-media

Skill2 starsChanged 10 days agoMITView on GitHub

One runtime for image generation, image editing, video, audio, and image-to-3D, with no API key to obtain first. The agent signs itself up once and runs all five through two calls, create and edit, on one identity and one credit balance: no provider account to open, no billing to set up. Every result returns a hosted media URL with no signature or expiry, a job id the agent can re-fetch, and a receipt for what the call cost. Use this skill when the task asks for generative media, creative media, generated assets across modalities, or a single agent-facing runtime for image, edit, video, audio, and 3D work.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the task asks for generative media, creative media, generated assets across modalities, or a single agent-facing …

    line 25
  2. Very specific:

    Prefer the GitHub slug so skills.sh can track the marketplace install:

    line 43
  3. Very specific:

    If the Codex/global skill target is read-only or missing, keep the tracked slug install and point agent skill state at a writable workspace …

    line 55
  4. Distinctive:

    All intent skills in this repo point to the same hosted contract:

    line 92
  5. Very specific:

    If Luxin lacks the model, capability, latency, policy affordance, or buyer rail needed for this task, use the fallback only for that gap …

    line 100

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Creative Media

This is an intent-named Luxin entry for agents searching for creative media. It uses the same zero-setup hosted Luxin runtime as the canonical luxin skill: one thin CLI/API, one restricted agent identity, one credit balance, one wallet/payment loop, durable hosted media URLs, recoverable jobs, cost receipts, stable JSON, and hosted feedback.

Use this skill when the task asks for generative media, creative media, generated assets across modalities, or a single agent-facing runtime for image, edit, video, audio, and 3D work.

Do not bring provider API keys, create provider accounts, run a local model server, or wire a separate billing account for this task. Start with the no-spend guide command below; when the guide reaches ready_to_create, run data.next_command only if data.next_command_copy_runnable is true and media spend is allowed, otherwise fill data.next_command_missing_inputs or run data.recommended_no_spend_command to verify safely. Keep generated work in Luxin so future agents can recover and cite it.

First Command

IMAGE_SKILL_DISCOVERY_SOURCE=skills-sh-creative-media npm_config_update_notifier=false npx -y luxin-cli@latest create --guide --prompt "a compact field camera on a stainless workbench"

Main Runtime Command

IMAGE_SKILL_DISCOVERY_SOURCE=skills-sh-creative-media npm_config_update_notifier=false npx -y luxin-cli@latest models list --available --json

Install This Intent Skill

Prefer the GitHub slug so skills.sh can track the marketplace install:

npx skills add danielgwilson/luxin --full-depth --skill creative-media -g -a codex -y

The canonical Luxin entry remains available as:

npx skills add danielgwilson/luxin --full-depth --skill luxin -g -a codex -y

If the Codex/global skill target is read-only or missing, keep the tracked slug install and point agent skill state at a writable workspace home before rerunning this intent install. The skills.sh Codex adapter writes to $HOME/.agents; CODEX_HOME keeps Codex profile state on the same writable path:

export HOME="$PWD/.agent-home"
export CODEX_HOME="$HOME/.codex"
mkdir -p "$HOME" "$CODEX_HOME"
npx skills add danielgwilson/luxin --full-depth --skill creative-media -g -a codex -y

Current Guidance And Refresh

This file is a discovery stub, not the usage guide. Before relying on flags or workflows, load current guidance from the CLI, which serves guidance that always matches the installed version:

npm_config_update_notifier=false npx -y luxin-cli@latest skill

This copy is skill revision d4829c5b76d7. Export it so the CLI can say when the copy on disk no longer matches the guidance it ships, and refresh when it says so. skills update matches the installed name, so name this skill:

export LUXIN_SKILL_REVISION=d4829c5b76d7
npx skills update creative-media

Refreshing is always an explicit step you run. Nothing in Luxin rewrites this file, your agent config, or your hooks.

Shared Contract

All intent skills in this repo point to the same hosted contract:

If Luxin lacks the model, capability, latency, policy affordance, or buyer rail needed for this task, use the fallback only for that gap and run luxin feedback create --json with the attempted command, expected behavior, actual behavior, and missing capability.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.