Publish Sign in

Chickener Image Agent Skill

Default workflow for generating, editing, transforming, or using raster images as references with the configured personal…

Install this skill Read the source first Free Written by abstractSJ
Context cost
4.9k tokensestimated from the bundle, loaded when it triggers
Bundle
6 files · 45.7 kB2 scripts among them — read before you run
Licence
not declarednone named by its author
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Default workflow for generating, editing, transforming, or using raster images as references with the configured personal OpenAI-compatible Images API and gpt-image-2. Use whenever the user asks to generate, create, draw, illustrate, render, edit, transform, or make an image, picture, photo, artwork, poster, banner, mockup, texture, or other bitmap asset. Do not use for SVG/vector work or code-native diagrams.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

design
Filed under

Design & Media

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md10.9 kB · preview
--- name: chickener-image ---
6# Chickener Image
7
8Treat this as the default path for raster image generation and editing. Use this skill's script for every image request; do not call the provider with ad-hoc curl or SDK code.
9
10When input images are present, first determine from the user's wording whether they should be edited independently, used together as references, or handled in stages. Do not infer the relationship from the number of images alone. If the intended relationship is ambiguous, ask a concise clarification before making a billable request.
11
12## Workflow
13
141. Turn the user's request into a concise image prompt. Preserve exact requested text and constraints.
152. Preserve the user's input order as stable labels 图1 through 图4 when they refer to numbered images. Do not renumber after validation or between processing stages.
163. Determine the operation from the user's intent: generation, single-image editing, independent batch editing, joint reference, or a clearly requested multi-stage workflow. Do not silently switch operations; ask when the relationship between multiple images is unclear.
174. Choose an output path. Use output/imagegen/ in the current project when the user does not specify a location; otherwise use the user's location. Resolve relative paths from the current project, never from the installed skill directory.
185. Resolve the skill directory from the location of this SKILL.md; never assume a user name, home directory, operating system, or install root.
196. Run <skill-directory>/scripts/generate_image.py with the explicit operation, --prompt, and output arguments. Use --quality low for a draft and medium or high for a final asset. Refuse before making a request when more than 4 input images or 4 final outputs are requested.
207. Inspect the written image with view_image. Treat this call as internal quality assurance only. If the image misses a required detail, make one targeted prompt revision and regenerate to a new filename.
218. Deliver every approved output in a separate final tool call as a generated-image result block. In functions.exec, load each file with tools.view_image(...), then call generatedImage({ image_url: result.image_url, output_hint: "short descriptive title" }). This makes the image appear directly in the conversation instead of only inside a collapsible view_image trace.
229. Do not use a plain view_image call, the generic image(...) helper, a Markdown link, or a filesystem path as the user-facing image delivery. Each image must be emitted with generatedImage(...). Do not report saved paths unless the user asks for them or needs them integrated into project files.
2310. Report the model, size, quality, and final prompt concisely after the inline images. Never print credentials or configuration-file contents.
24
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md1,590 words
Files6
Licencenot declared
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈110
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
4,765
on trigger
The instruction body and 5 supporting files, read only when the skill fires.
2.4%
of a 200k window
Ten skills this size would take about 24% of the window before you open a file.
050k100k150k200k context window

4.9k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

6 files, 45.7 kB on disk. Mostly text — the instructions the model reads — with 2 scripts in it that your client would run only if the instructions tell it to. 1 file of its source is not in the download — listed after these, with why.

  • SKILL.md10.9 kB
  • README.md8.3 kB
  • requirements.txt0.1 kB
  • agents/openai.yaml0.2 kB
  • scripts/configure.py4.5 kB
  • scripts/generate_image.py21.7 kB

Not in the download

Not carried is a type a skill download does not hold. Take it from its source.

  • .gitignorenot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 2 scripts beside the text, so the download is 6 files — not the whole of its source: 1 file is left out. It is listed under the files, with why.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Chickener Image · 4.9k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/chickener-image/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/chickener-image" ] && { [ ! -e .claude/skills/chickener-image ] || { mv .claude/skills/chickener-image "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/chickener-image" .claude/skills/ && echo "Installed .claude/skills/chickener-image"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add abstractsj/chickener-image

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/chickener-image/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/chickener-image/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/chickener-image" ] && { [ ! -e ~/.claude/skills/chickener-image ] || { mv ~/.claude/skills/chickener-image "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/chickener-image" ~/.claude/skills/ && echo "Installed ~/.claude/skills/chickener-image" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/chickener-image/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. Not in this download: 1 file of its source (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceabstractsj/chickener-image

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Who wrote it

AB
abstractSJ

Publishes on mcprush.

0 servers listed1 skill listednot claimed
Profile
Publisher
Servers0
Claim this skill