mcpbeat Sign in

SEO Image Gen Skill for Claude

Create or edit SEO images with ChatGPT's integrated image generation. Use for requested blog heroes, social previews, product illustrations, local-service visuals and infographics.

952 tokens
context cost
SKILL.md, read when the skill is used
2
files
plus reference files
0
copies elsewhere
how many repositories repackaged it
834
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/AgriciDaniel/chatgpt-seo --skill seo-image-gen

What comes with it

187 bytes besides the instruction
agents/openai.yaml

The instruction itself

6 sections, as written by the author

SEO image generation

Input

The requested image, its placement and known brand/product facts. Existing

images can be edit targets or visual references; identify their role.

Evidence and runtime

If a skill-resource reader fails to open a linked supporting file, try the

available file or execution tool using the installed plugin root returned by

the host or resolved from this skill's location. Do not hardcode a home folder,

version, or working directory. Distinguish a failed reader call from an absent

file, and files actually attempted from files not attempted. Report a resource

as unavailable only after the supported access paths have failed. If no file

or execution access is available, continue within the evidence you can read

and state that limit.

Read the operating contract and

native image workflow. Choose a relevant

asset recipe when the brief needs one.

Workflow

  • Preserve the user's concept, exact requested text, brand cues and supplied

product details. Ask one question only if an essential input is missing.

  • Decide whether this is creation, a variant or an edit. For an edit, inspect

the actual target first and state which elements must be preserved.

  • Build a concise prompt: purpose, subject, composition, style, exact text,

reference roles and constraints. Use known facts for diagrams, labels and

infographics. Generated visuals cannot establish real product appearance,

business premises, staff identities, testimonials or statistical evidence.

  • Call the host's integrated image-generation/editing tool directly when it

is available. Follow that tool's current instructions for reference-image

selection, transparency and returning the result. A normal creation request

does not require an API key, provider installation or another confirmation.

  • Use genuine transparency for a requested cutout and preserve existing

alpha on edits. Include the actual edit target/reference using the tool's

supported mechanism. If a required reference is missing, request that image.

  • Inspect the returned image for subject fidelity, text accuracy, composition,

cropping and preserved edit constraints. Make a targeted correction when

the result materially misses the brief. Do not manufacture a success claim

after a failed generation or use unrelated output as the requested asset.

  • Deliver the generated image inline and any actual file the host returned.

Include a useful filename, context-sensitive alt text and intended placement.

State actual dimensions/format only from the returned file or metadata.

Provide responsive/lazy-loading guidance through seo-images when relevant.

Deliverable

The requested visual, a concise prompt/recipe record, filename and alt text.

Use the image delivery template for multiple

assets or implementation handoff. Preserve existing files; a generated draft

does not authorize replacing or publishing a live asset.

Boundary

If integrated image generation is unavailable in this chat, state that limit

and deliver a ready-to-run visual brief. Do not switch to an external provider,

paid API, CLI or dependency installation. Existing editable SVG/icon assets

can be edited as vectors when that better fits the user request.

Adapted from the public SEO image workflow.

How to use it

Copy the folder

Take agricidaniel/seo-image-gen from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.