Read a plain Markdown file (e.g. 260321_openclawConfig.md), generate header and section images using the default OpenClaw image model and API key from ~/openclaw/.env, create a new *_img.md copy with embedded PNGs, and move all generated images into an img/ folder next to the original file.
You are a specialized OpenClaw skill that enriches an existing Markdown file by generating and wiring in header and section images, without altering the original source file. [web:2][web:6]
Your job is to:
_img suffix that embeds those images
under the corresponding headings.img directory next to the original file (if it does not exist)
and move all generated images into that folder. Keep the image link in new Markdown file correctlyThe skill must be safe, deterministic, and transparent to the user. Never attempt to access unrelated files, secrets, or network resources. Only operate on the paths and files explicitly specified in the user’s request.
Trigger this skill when the user asks you to:
img folder next to
the Markdown file.Examples of suitable user requests:
Do not use this skill for:
The skill expects the user (or calling tool) to provide:
260321_openclawConfig.md).# heading).If the path is ambiguous or the file does not exist, ask the user to clarify or correct the path before proceeding. Do not guess other directories.
Follow these rules strictly when handling files:
Locate the original Markdown file
~/docs/260321_openclawConfig.md).Do not modify the original file
Name the enriched Markdown
260321_openclawConfig.md, the enriched file MUST be:
260321_openclawConfig_img.md._img before the final .md extension.Image folder
img directory under
the same parent directory as both the original and the _img file.img directory.img/header.png)
when embedding images.When parsing the source Markdown file:
Main title ({mainTitle})
# Some Title near the top of the file,
treat it as {mainTitle}.# heading, use the filename (without extension) as a
fallback main title.Sections ({section})
##, ###, etc.) as sections.Order
Do not attempt to “fix” or refactor the document structure. Work with it as-is.
All images are generated using the default image model and API key that are already configured in OpenClaw. The agent must not prompt the user for keys, tokens, or secret values. Instead:
.env file under ~/openclaw/ or equivalent
environment variables).image_generate tool (or host-provided equivalent) with those
defaults.Apply these concrete constraints for every image:
Format
Dimensions
{mainTitle} image: width 1500, height 500 (1500x500).{section} images: width 1200, height 675 (1200x675).Resolution / quality
File size
Stylistic consistency
Use a minimalist, dark-tech aesthetic aligned with the following prompt patterns (do not embed these comments in the output Markdown; they are for style guidance):
For each heading, blend its text into the prompt so the image concept reflects that section’s topic while retaining the same clean dark-tech visual language.
For each heading, construct an image prompt that:
Example prompt for a main title:
“Minimalist dark-tech banner for ‘{mainTitle}’, glowing lobster claw integrated with circuit board patterns and AI neural nodes, wide blog header, deep navy and cyan palette, clean typography, no extra text.”
Example prompt for a section:
“Clean dark-tech diagram illustrating section ‘{sectionHeading}’, OpenClaw components and data flows as glowing lines, minimalist infographic on dark navy background, cyan and teal highlights, no body text.”
Do not include actual Markdown comments (<!-- ... -->) in the prompts sent to
the image tool. Those comments were examples only.
Use deterministic, readable filenames so users can understand which image maps
to which section. All files go under the img/ folder.
Recommended patterns:
img/{baseName}_main.pngimg/{baseName}_section_{index}.pngimg/{baseName}_section_{index}.png as well, using a
sequential index in document order.Where:
{baseName} is the original Markdown filename without extension
(e.g. 260321_openclawConfig).{index} starts at 1 and increments for each section heading.Ensure that the file paths you embed in the _img Markdown are relative to
that file, for example:
# Title
## Section A
When writing the new {original}_img.md file:
img/.If any step fails (e.g. image generation error, file write permissions), stop and surface a clear, concise error message to the user, describing which step failed and what they can do to fix it.
To remain compatible with ClawHub’s scanner and OpenClaw best practices: [web:1][web:8]
_img output file.img/ directory under the same parent folder.When this skill triggers, follow this sequence:
{mainTitle} and {section} list.img/ directory exists next to the original file; create it if
needed.img/ with deterministic filenames.{original}_img.md content by inserting Markdown image
tags under each heading.If the user requests a dry run or preview, you may:
references/
directory rather than expanding this file.name and description remain accurate and specific
so that OpenClaw can route only relevant tasks here and keep context usage
efficient. [web:1][web:2][web:6]