image-skill
Skill1 starsChanged 2 months agoMITView on GitHub
Generate/Edit images using Modelscope API Inference. Use when user wants to generate, or edit images via Modelscope's hosted models (Z-Image-Turbo, Qwen-Image, FLUX, etc.). Trigger phrases: "generate image", "create image", "image generation", "edit image", "Modelscope image", "AI image", "画图", "生成图片".
1 other project uses a version of this.
Adopted by
Most recently taken up by
- danielgwilson/luxintheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- danielgwilson/luxin★ 2same 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 repositoryOne other file it gives its agents.
- CLAUDE.mdCLAUDE.md
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
If image-gen is not found on PATH, or config.yaml is missing/needs an API key, stop and read references/AGENTS_README.md first.
- Very specific: line 27
Every generate/edit command accepts: --negative-prompt, --steps, --cfg-scale, --width, --height, --seed, -o/--output (output directory, …
≈ “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 — Modelscope API Inference
Generate and edit images via Modelscope's API Inference, through the image-gen CLI.
If image-gen is not found on PATH, or config.yaml is missing/needs an API key, stop and read references/AGENTS_README.md first.
Commands
| Command | Description |
image-gen generate "prompt" | Generate image with default model |
image-gen generate "prompt" --model <model-id> | Generate with specific model |
image-gen edit <image> "prompt" | Edit an existing image (local path or URL) with a prompt |
image-gen edit <image> "prompt" --model <model-id> | Edit with a specific edit-capable model |
image-gen generate/edit ... --no-wait | Submit only — prints a task id immediately instead of blocking |
image-gen status <task_id> | Check a submitted task once; downloads output if it finished |
image-gen status <task_id> --wait | Block until that task finishes, then download output |
image-gen list-models | List available models |
image-gen set-model <model-id> | Set default model (persists to config.yaml) |
image-gen current-model | Show current default model |
Every generate/edit command accepts: --negative-prompt, --steps, --cfg-scale, --width, --height, --seed, -o/--output (output directory, defaults to ./outputs relative to wherever the command runs), -p/--prefix (filename prefix).
edit defaults to Qwen/Qwen-Image-Edit when --model is omitted, since not all models support editing.
By default generate/edit block until Modelscope's async task finishes — typically 20s to 2min, occasionally longer for edit. If you need to keep working while it runs, don't background the whole image-gen process at the shell/tool level — a nested background job (a backgrounded command that itself launches another background job) can report "completed" as soon as the outer wrapper returns, before image-gen has actually finished and written its output. Instead, add --no-wait: it submits the job and returns a task id in well under a second, so no OS-level backgrounding is needed at all. Do other work, then check it with image-gen status <task_id> (single check, exits immediately either way) or image-gen status <task_id> --wait (blocks, then downloads) whenever it's convenient — that final status call only reports done when the task is genuinely done.
Writing the prompt
Apply before every generate/edit call — generation and editing need genuinely different prompt shapes, and getting this wrong is the main cause of bad output:
- Generate with Qwen-Image: order the prompt subject → style/medium → setting → lighting/mood → detail, 1–3 sentences. Any text that must render in the image goes in
"double quotes"— this alone is the biggest lever on text accuracy. - Generate with Z-Image-Turbo: write a long, detailed creative brief instead — this model rewards detail. It has no negative-prompt support at all;
--negative-promptis silently ignored, so fold every constraint into the main prompt as a positive statement ("sharp focus" not "not blurry"). - Edit with Qwen-Image-Edit: write an instruction describing the change, never a description of the end state. Bad:
"A woman with short brown hair in a blue blouse". Good:"Change her hair to short brown and her blouse to blue". When multiple similar objects are in frame, disambiguate by position/attribute ("the second person from the left"). For in-image text edits, quote the exact replacement text — font/size/style carry over unless you say otherwise. - For a multi-stage edit, run
edittwice — feed the first result back in as the nextimageargument — rather than stacking unrelated changes into one instruction.
Full rationale, more examples, and per-model parameter recommendations (--cfg-scale/--steps) — references/prompt-guide.md.
Available Models (from config.yaml)
Tongyi-MAI/Z-Image-Turbo— Fast, low cost, LoRA support (generate only)Qwen/Qwen-Image— High quality, editing support, LoRA supportQwen/Qwen-Image-Edit— Image editing, LoRA support
Further reference
- Full prompt-writing rationale, examples, and sources —
references/prompt-guide.md. - Installing
image-genas auv tool, first-timeconfig.yamlsetup, adding new models, and howoutput_dirresolves —references/AGENTS_README.md. - Calling
ModelscopeClientdirectly from Python and passingloras(not exposed via the CLI) —references/python-api.md.
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.

