Blog Polish (zh-CN) + Image Pack

This skill takes a technical blog draft and turns it into a publish-ready package:

• - Polish: spelling/grammar fixes + clarity improvements
• Structure: reorganize into 3–4 sections total (not more)
• Length: final content 1000–1200 words
• Translation: English → Simplified Chinese, while preserving:

- technical terms like skills, plugin, openclaw, clawhub - code blocks and commands (no translation inside code fences) - inline code spans (backticks) as-is unless obviously wrong

• - Images: generate a hero prompt + one prompt per section, all in the same style/tone
• Save: write everything to ~/.openclaw/workspace/contentPolished/ using yymmddhhmm-* naming

When to Use This Skill

When the user asks to polish a technical blog, translate it to Simplified Chinese, and create images, you MUST use this skill and follow the workflow below step by step.

Use this when:

• - You already have a draft at INLINECODE6
• You want a polished zh-CN version without losing technical accuracy
• You want consistent illustrations for the article

Defaults

If not provided via input:

• - draftPath: INLINECODE8
• INLINECODE9: INLINECODE10
• INLINECODE11: INLINECODE12
• INLINECODE13: INLINECODE14
• INLINECODE15: INLINECODE16
• INLINECODE17: INLINECODE18

Workflow Step-by-Step

Step 0 — Resolve Paths and Timestamp

1. 1. Resolve defaults:

- draftPath = input.draftPath || "~/.openclaw/workspace/contentDraft/latestDraft.md" - outputDir = input.outputDir || "~/.openclaw/workspace/contentPolished/"

1. 2. Create a timestamp prefix ts in yymmddhhmm format (Linux/macOS):

CODEBLOCK0

1. 1. Ensure output dir exists (shell is fine):

CODEBLOCK1

Step 1 — Read Draft Exactly

Read the draft content in full before editing anything:

INLINECODE22

Step 2 — Extract Title, Topic, and Section Candidates

1. 1. Identify:

- Draft title (first # heading; otherwise infer a short title) - Main topic and intended audience

1. 2. Plan a 3–4 section outline (including intro/conclusion counts as sections if they have headings):

- Prefer: short intro, 2–3 core sections, short wrap-up - If the draft is long, merge similar paragraphs - If the draft is messy, reorder paragraphs for a cleaner flow

Step 3 — Polish English (Meaning First)

Before translating, make sure the English content makes sense:

• - Fix misspellings, grammar, punctuation
• Paraphrase confusing sentences
• Add missing connective tissue only where the meaning is unclear
• Do not reduce content (no big deletions)

Step 4 — Translate to Simplified Chinese (With Preservation Rules)

Translate the full draft into zh-CN with these hard rules:

• - Keep code fences unchanged (commands/code stay exactly the same)
• Keep inline code (backticks) unchanged unless it contains an obvious typo
• Keep common technical terms in English (examples):

- skills, plugin, openclaw, clawhub, cli, markdown, yaml

• - If a technical term has a standard Chinese translation but the English term is common in your audience, keep the English term and (optionally) add a short Chinese clarification once on first use

Step 5 — Enforce Length (1000–1200 Words) Without Cutting Meaning

Target final length 1000–1200 words (counting Chinese words approximately by rough equivalence).

To fit without “reducing content”:

• - Tighten redundancy (same idea repeated)
• Use shorter sentences
• Prefer combining adjacent sentences that restate the same point

Step 6 — Add Citations If You Introduce Outside Facts

If you add any information that is not clearly present in the draft:

• - Add a short citation marker in text like: INLINECODE31
• Add a footnotes section at the end:

CODEBLOCK2

Step 7 — Generate Image Prompts (Hero + Per Section)

Create one single-line prompt for:

• - Hero image (for the whole post)
• Each section (exactly one per section heading)

Use this strict ordering and keep the same style/tone across all prompts:

CODEBLOCK3

Constraints:

• - No text in the image (prefer icons/arrows)
• Keep a consistent palette (neutral + one accent color)
• Keep prompts to a single line each

Step 8 — Save Outputs

1. 1. Decide subject:

- subject = input.subject || slugify(title) (lowercase, hyphens)

1. 2. Write the polished markdown:

- {{outputDir}}/{{ts}}-{{subject}}.md

1. 3. Determine image filenames:

- Hero: {{ts}}-main.png - Per section: {{ts}}-section1.png, {{ts}}-section2.png, ...

1. 4. Save:

- Write the polished .md file via write_file - For images: - If you have an image-generation tool available in your OpenClaw setup, generate and save the actual PNG/JPGs - Otherwise: still create an image-prompts block inside the markdown and return the intended filenames (so you can generate them later)

Output Format (What You Return)

Return:

• - INLINECODE41
• INLINECODE42 (actual or intended)
• INLINECODE43 (single-line prompts in the same order)

Also print a short summary:

CODEBLOCK4

Example Invocation

User says:

• - “Polish my latest draft, translate to zh-CN, and make images.”

You do:

• - Read from INLINECODE44
• Produce INLINECODE45
• Produce 26031214xx-main.png + 26031214xx-section1.png ...

Dependencies

None (pure Markdown in/out). Uses the same file read/write capability as your other skills.