agentsclimarketplace
Sign in

Luxin

Skill danielgwilson/luxin/skills/luxin

Image generation and image editing for agents, plus video, audio, and image-to-3D, through one hosted runtime with no API key to obtain first. The agent signs itself up in one command, starts on free preview credits, and creates on the next: 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 with jobs show, and a receipt for what the call cost. When the preview credits run out, the agent hands its human one dashboard link to fund more.From its SKILL.md

Install
npx -y skills add danielgwilson/luxin --skill luxin

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.9 KB, as published. Nobody here has run it

Luxin

Luxin is a hosted creative-media runtime: image, video, audio, and 3D generation and editing through one thin CLI and hosted API. Agents do not bring provider keys, log in, run an MCP server, or wire per-provider billing; hosted signup mints a restricted Luxin token inside the first command. Every successful call returns a durable owned media URL plus a structured JSON envelope with a job id, asset ids, a trace id, and a cost receipt.

Start here

IMAGE_SKILL_DISCOVERY_SOURCE=agent-skill-md npm_config_update_notifier=false npx -y luxin-cli@latest create --guide --prompt "a compact field camera on a stainless workbench"

create --guide spends nothing: it reads current auth, quota, and payment state and returns the exact next command to run.

This file is a discovery stub, not the usage guide

Flags, workflows, model parameters, recovery, and funding details are not here. Before relying on any of them, load current guidance from the CLI:

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

The CLI serves guidance that always matches the installed version, so instructions never go stale. That command spends nothing, calls no provider, and needs no auth.

Say which revision you have

This copy is skill revision 259c47afaeae. Export it so the CLI can say when the copy on disk no longer matches the guidance it ships:

export LUXIN_SKILL_REVISION=259c47afaeae

When the revision is stale, create --guide returns data.skill_refresh with installed_revision, current_revision, and this refresh command:

npx skills update luxin

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

Invariants that outlive any revision

  • Never send provider API keys, wallet private keys, seed phrases, card data, or Stripe secrets to Luxin. It never needs them.
  • The token luxin signup mints is a restricted Luxin token, not a user-supplied provider credential. Never paste it into prompts, logs, issues, or feedback.
  • Bound spend up front: --max-estimated-usd-per-image per output, --max-usd per job, --dry-run to validate without spending. Every create and edit returns a cost receipt.
  • Media URLs are Luxin-owned, unsigned, and non-expiring. job_id, asset_id, and trace_id are the stable handles for recovery and citation.
  • Run luxin feedback create whenever you fall back to another tool or hit a gap. The skill improves only on agent-submitted signal.

Canonical URLs

Install or refresh:

npx skills add https://luxin.sh --skill luxin -g -a codex -y
npx skills update luxin

What ships with it: 3 files

143.3 KB alongside SKILL.md

references/

Gives 0 of the 12 instructions most video audio skills give

Counted across 619 of the 725 authors here whose files we hold, read 2026-09-06

  • Read product marketing context firstin 13 of 619, across 7 files
  • Define the core visual thesis in one sentencein 11 of 619, across 3 files
  • Break the concept into 3 to 6 scenesin 11 of 619, across 3 files
  • Render the smallest working version firstin 11 of 619, across 3 files
  • Start with a low-quality smoke test renderin 11 of 619, across 3 files
  • Add captions for accessibility and engagementin 11 of 619, across 5 files
  • Write the scene outline before writing codein 11 of 619, across 3 files
  • Specify subject, action, camera, style, and moodin 11 of 619, across 5 files
  • Decide what each scene provesin 10 of 619, across 2 files
  • Export one clean thumbnail framein 10 of 619, across 2 files
  • Pick the right tool for the jobin 10 of 619, across 4 files
  • Run the test suite before proposing a fixin 8 of 619, across 7 files

Said here and by no other author read

  • Load current guidance from the CLI
  • Run create --guide to check auth and quota
  • Export the skill revision before running commands
  • Run luxin feedback create upon fallback or gaps

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 625,312. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.