blog-polish-en-astro-cn

Polish and translate a technical blog draft into a 1000–1200 word, 4-5 section Markdown article in English and Simplified Chinese (zh-CN), preserving technic...

Security Scan

This is an instruction-only blog-polishing/translation skill that reads a local draft and writes polished Markdown outputs; its requirements and behavior are coherent aside from minor metadata/path inconsistencies.

Purpose & Capability

The name/description (polish + translate a blog draft and produce an Astro-compatible English file) matches the workflow: read a draft, call the LLM to polish/translate, write out markdown files. The only mismatch is a metadata note that the skill 'requires' jq while the registry summary reported no required binaries — jq is actually used in finalize steps to emit JSON and is reasonable for this purpose.

Instruction Scope

Instructions explicitly read the draftPath file and write outputs to outputDir (creating directories). This is expected. There is no instruction to read unrelated system files, access credentials, or call external endpoints other than invoking the LLM. Note: some included files reference a hardcoded user path (/home/jeff/...) which is likely a leftover and should be corrected or checked before use.

Install Mechanism

No install spec or code files are present (instruction-only), so nothing is downloaded or written during install. Low install risk.

Credentials

The skill does not request environment variables, credentials, or config paths. It operates on user-specified file paths. This is proportionate to a local polishing/translation tool. Reminder: the SKILL metadata lists jq as a required tool — not a credential but a binary dependency.

Persistence & Privilege

always:false and no modifications to other skills or system-wide settings. The skill creates files under the user-specified outputDir only, which is appropriate for its purpose.

Assessment

This skill is primarily an instruction-only workflow that reads a markdown draft from your filesystem and writes polished/translated markdown files. Before installing or running: (1) Confirm the draftPath and outputDir defaults point where you expect (some included files contain a hardcoded /home/jeff path); update them if necessary. (2) Ensure jq is available if your runtime relies on the SKILL metadata (the finalize step calls jq to emit JSON). (3) Do not put secrets or sensitive credentials inside drafts — the content is sent to the LLM for polishing/translation. (4) Because this is an LLM-driven skill, consider which model/provider will be used and review its privacy policy if draft contents are sensitive. Other than the minor metadata/path inconsistencies, the skill's declared purpose matches what it does.

title: "${title:-Generated by OpenClaw}" date: $(date -Iseconds) tags: ${tagsYAML} image: ./hero.png

$(cat "$polishedFile") EOF

  mkdir -p "${outputDir}/${ts}-${slug}/images/"
  save_state outputPath "$outputFile"

• name: finalize description: Emit polished path only run: |

outputPath=$(load_state outputPath)

jq -n --arg outputPath "$outputPath" '{ outputPath: $outputPath }'

    engOutputPath=$(load_state engOutputPath)
    chnOutputPath=$(load_state chnOutputPath)
    outputPath=$(load_state outputPath)
    jq -n \
      --arg engOutputPath "$engOutputPath" \
      --arg chnOutputPath "$chnOutputPath" \
      --arg astroPath "$outputPath" \
      '{ engOutputPath: $engOutputPath, chnOutputPath: $chnOutputPath, astroPath: $astroPath }'

---

Blog Polish (en-US and zh-CN)

This skill polishes a technical blog draft and translates it to English and then Simplified Chinese while preserving technical accuracy.

When to Use

Use when the user asks to polish/translate a technical blog draft to zh-CN without images. Triggers: "polish my draft", "translate blog to Chinese", "enhance latestDraft.md".

Defaults

• draftPath: ~/.openclaw/workspace/contentDraft/latestDraft.md
• outputDir: ~/.openclaw/workspace/contentPolished/
• Output filename: ${ts}-polished.md or ${ts}-${subject}.md

Workflow Summary

Draft → Check → Polish (EN) → Translate (ZH) → Convert EN to Astro format → Emit path JSON.

1. Resolve paths + create timestamp (date +"%y%m%d%H%M")
2. Read draft from draftPath
3. Polish English: Fix grammar/spelling, improve clarity, structure into 4-5 sections, target 1000-1200 words
4. Translate to zh-CN: Preserve code blocks, inline code, technical terms (openclaw, skill, cli)
5. Save polished markdown to ${outputDir}/${ts}-polished.md
6. Return: { outputPath: "/full/path/to/file.md" }

Output

Example

Input: ~/.openclaw/workspace/contentDraft/latestDraft.md
{ "outputPath": "~/.openclaw/workspace/contentPolished/2603142134-openclaw-skills.md" }