image-skill
Skill2 starsChanged 10 days agoMITView on GitHub
Image generation and image editing for agents under Luxin's original skill name, 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, and a receipt for what the call cost. Models include FLUX, Nano Banana, Seedream, Grok Imagine, and GPT Image, each picked by name. Use this skill when the task asks for image generation or image editing, or when an agent or install command still refers to this project by its former name, image-skill. It resolves to the same Luxin runtime as the canonical luxin skill.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- szchan/image-skilltheir own version, first seen Aug 31, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- szchan/image-skill★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- llms.txtllms.txt
- skills/luxin/references/llms.txtllms.txt
- luxinSkill
- agent-image-generationSkill
- ai-audio-generationSkill
- ai-image-generationSkill
- ai-video-generationSkill
- creative-mediaSkill
- image-editSkill
- image-generationSkill
- image-to-3dSkill
- luxinSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 25
Use this skill when the task asks for image generation or image editing, or when an agent or install command still refers to this project …
- Very specific: line 43
Prefer the GitHub slug so skills.sh can track the marketplace install:
- Very specific: line 55
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 …
- Distinctive: line 92
All intent skills in this repo point to the same hosted contract:
- Very specific: line 100
If Luxin lacks the model, capability, latency, policy affordance, or buyer rail needed for this task, use the fallback only for that gap …
≈ “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.
Files
Image Skill
This is an intent-named Luxin entry for agents searching for image generation and editing. 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 image generation or image editing, or when an agent or install command still refers to this project by its former name, image-skill. It resolves to the same Luxin runtime as the canonical luxin skill.
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-image-skill 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-image-skill npm_config_update_notifier=false npx -y luxin-cli@latest create --prompt "PROMPT" --intent explore --max-estimated-usd-per-image 0.07Install This Intent Skill
Prefer the GitHub slug so skills.sh can track the marketplace install:
npx skills add danielgwilson/luxin --full-depth --skill image-skill -g -a codex -yThe canonical Luxin entry remains available as:
npx skills add danielgwilson/luxin --full-depth --skill luxin -g -a codex -yIf 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 image-skill -g -a codex -yCurrent 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 skillThis 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 image-skillRefreshing 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:
- Skill: https://luxin.sh/skill.md
- Full guidance: https://luxin.sh/skill-core.md
- LLM contract: https://luxin.sh/llms.txt
- CLI contract: https://luxin.sh/cli.md
- Hosted API: https://api.luxin.sh
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.
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
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.

