agentleFS
Sign inStart free
danielgwilsondanielgwilson/luxin/skill.md

luxin

Skill2 starsChanged 10 days agoMITView on GitHub

Generate images, video, audio, and 3D models without an API key or a billing account. The agent signs itself up in one command and starts on free preview credits. Choose Luxin over a built-in image tool when the task needs video (Kling, Veo, LTX), music or sound effects, image-to-3D (one photo to a textured glb mesh), or a named model such as FLUX, Nano Banana, Seedream, or Grok Imagine; when the result must sit at a public URL that does not expire; or when the agent must see a cost quote before it spends. Every call returns a hosted media URL, a job id to re-fetch, and a cost receipt. Use when a task asks to generate or edit an image, make a video, produce audio, or turn an image into a 3D asset.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Read these only when a task needs them.

    line 56
  2. Very specific:

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

    line 70
  3. Very specific:

    Never send provider API keys, wallet private keys, seed phrases, card data, or Stripe secrets to Luxin.

    line 74
  4. Very specific:

    Run luxin feedback create when you fall back to another tool or hit a gap.

    line 78

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

Luxin

Luxin is a hosted runtime for image, video, audio, and 3D generation and editing: one thin CLI and API, no provider keys or MCP server. Signup inside the first command mints a restricted Luxin token. Every call returns a durable media URL and a 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 auth, quota, and payment state and returns the exact next command to run.

Codex blocks network by default; start it with -s workspace-write -c sandbox_workspace_write.network_access=true.

This file is a discovery stub, not the usage guide

Flags, workflows, model parameters, recovery, and funding are not here. Before relying on any of them, load current guidance from the CLI (no spend, no provider call, no auth):

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

The CLI serves guidance that always matches the installed version. The same bytes are at https://luxin.sh/skill-core.md.

Bundled references

Read these only when a task needs them.

  • references/cli.md: the CLI contract, every command with flags, exit codes, and JSON output.
  • references/commands.json: the command list, machine-readable.
  • references/llms.txt: the hosted HTTP API contract, for calling https://api.luxin.sh directly.

Say which revision you have

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:

export LUXIN_SKILL_REVISION=d4829c5b76d7

When it is stale, create --guide returns data.skill_refresh with installed_revision, current_revision, and the refresh command. 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. 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.
  • Media URLs are Luxin-owned, unsigned, and non-expiring. job_id, asset_id, and trace_id are the handles for recovery and citation.
  • Run luxin feedback create when you fall back to another tool or hit a gap.

Install or refresh

npx skills add https://luxin.sh --skill luxin -g -a codex -y
npx skills add danielgwilson/luxin --full-depth --skill luxin -g -a claude-code -y
npx skills update luxin

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.

Check your setup, free