Write, organize, and publish articles to the izone blog. Supports two modes: (1) Writing assistance — draft an article from a topic, outline, or raw notes, or organize existing content into well-structured article format. (2) Publishing — push a completed article to the blog via API. Triggers on: 写文章, 整理文章, 帮我写一篇, 整理成文章, 发布文章, 推送文章, publish article, post to blog. Publishing only happens when the user explicitly asks to publish or push; writing and organizing can be done independently.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Write, organize, and publish articles to the izone blog. Supports two modes: (1) Writing assistance — draft an article from a topic, outline, or raw notes, or organize existing content into well-structured article format. (2) Publishing — push a completed article to the blog via API. Triggers on: 写文章, 整理文章, 帮我写一篇, 整理成文章, 发布文章, 推送文章, publish article, post to blog. Publishing only happens when the user explicitly asks to publish or push; writing and organizing can be done independently.
Article Writing and Publishing
This skill has two independent modes:
Write/Organize — Help draft or polish article content. Does NOT publish.
Publish — Push a completed article to the blog. Only on explicit user request.
Writing Guidelines
Apply these rules to all article content produced by this skill, whether writing from scratch
or organizing existing material.
Structure
Heading hierarchy: The article body must NOT contain # (h1) — the blog page already has a title. Use only ## (section) and ### (sub-section). Max 2 levels of body headings. No ####.
Heading numbering: Prefix ## with numbers (## 1., ## 2.). Prefix ### with sub-numbers (### 1.1, ### 1.2, ### 2.1).
Heading length: Keep headings short and descriptive. Chinese headings ideally ≤15 chars.
Paragraph length: Break long paragraphs. Aim for 3-5 sentences max per paragraph.
Article opening: Start with a paragraph of context or summary (1-3 sentences), then the first ## heading. Never start the body directly with a heading — give readers a moment to understand what the article is about.
Code Blocks
Always specify language: Every fenced code block must have a language identifier.
Use the correct language (python, bash, yaml, sql, json, nginx, etc.).
If unsure or no specific language fits, use text.
Never leave the language field empty — ``` without a language is not allowed.
Spacing
Blank line before headings: Always one blank line before ## and ###.
Blank line after headings: Always one blank line after every heading.
Blank line around code blocks: One blank line before and after fenced code blocks.
Blank line around lists: One blank line before and after ordered/unordered lists.
Between paragraphs: Always separate paragraphs with a blank line.
Emoji
Do not add decorative emoji to article body. Emoji may only be used when:
The original content already contains them
They carry semantic meaning (e.g., warnings, checkmarks in task lists)
The user explicitly requests them
Tone
Write in natural Chinese. Avoid AI-typical patterns: no overly formal transitions like
"总而言之" "值得注意的是" "综上所述" "不可否认" "众所周知".
Use concrete examples over abstract explanations. Show code/output rather than describing it.
Vary sentence length. Mix short direct sentences with longer explanatory ones.
Read like a knowledgeable colleague writing notes, not a textbook.
Cover Image
To generate and upload a cover image for the article:
SVG template spec:
Size: 500×300 (2x retina, imagekit resizes to 250×150)
Required design elements (optimized for readability at 250×150 display size):
Background: Dark gradient, vary by article — navy (#0f172a/#1e293b), deep purple (#1a0f2e/#2d1f4e), dark teal (#0f1a1f/#1a2f33), warm dark (#1f1a0f/#332d1a). Pick one that fits the article's mood. No grid pattern.
Glow: 1-2 large low-opacity circles in corners (opacity 0.04-0.08), color matches the accent
Top label: Pill tag with category keyword, accent gradient fill at low opacity, font-size 14px
Icon row: 4 simple SVG geometric icons (40×40 rounded rects with paths/shapes) above the title, each with a short label below (font-size 12px). Each icon uses a different accent color. Do NOT use emoji or unicode — cairosvg cannot render them.
Main title: Bold white font, centered, max 2 lines, 36-40px
Accent line: Short gradient line + dot under the title
Description: One line of lighter text summarizing key topics, font-size 18px
No bottom bar — the space is used to enlarge the title and description
Color: Choose a 2-3 color accent palette per article, vary background shade and accent colors each time
Font Rules (MANDATORY — violations cause unreadable covers or garbled text)
Font family stack — every <text> element must use this exact attribute:
font-family="'Noto Sans CJK SC','PingFang SC','Microsoft YaHei',sans-serif"
Do NOT add: content cards, code blocks, complex diagrams, emoji/unicode symbols, or more than 1 line of description. The title is the hero — icons and glow circles are subtle support.
Upload flow (3 steps):
Step 1 — Generate SVG: Design the cover following the spec above, write to /tmp/<slug>-cover.svg.
Step 2 — Upload: Server converts SVG to PNG automatically (no local tools needed).
Step 3 — Include in publish: Add "img_link": "<url from step 2>" to the publish JSON payload. Or use POST /skill/articles/cover/ to update the cover of an already-published article:
If the article doesn't need a custom cover, omit img_link to use the default image.
Mode 1: Write / Organize
Triggered when user says "写文章", "整理文章", "帮我写一篇", "整理成文章", "draft an article".
Writing from scratch
When the user provides a topic or outline:
Plan the article structure (numbered headings, key points, code examples)
Generate a slug from the title
Write the article to /tmp/<slug>.md following Writing Guidelines (mandatory — never present content inline only)
Read the file back and present to user
Ask: "需要调整什么吗？确认后可以推送到博客。"
Do NOT publish unless the user explicitly asks.
Organizing existing content
When the user provides raw notes, bullet points, or a rough draft:
Preserve all factual content, code, and data
Restructure headings to ≤3 levels with numbering
Fix spacing (blank lines around headings, code blocks, lists)
Ensure all code blocks have language identifiers
Remove unnecessary emoji
Rewrite AI-flavored phrasing to natural Chinese
Write the cleaned article to /tmp/<slug>.md
Present the cleaned article and ask: "整理完成。需要进一步调整吗？确认后可以推送到博客。"
Mode 2: Publish
Triggered ONLY when user explicitly says "发布", "推送", "publish", "push to blog", "发布文章".
If the article has not been shown to the user yet (e.g. user provides a file path to publish directly),
follow the full publish flow below. If the article was just written/organized in Mode 1 and is already
visible to the user, skip to Step 4 (metadata matching).
MANDATORY: The article body MUST be written to a file before publishing. Never inline the body in a bash command — shell escaping will corrupt code blocks, special characters, and backticks.
From a file path → Read with Read tool, write to /tmp/<slug>.md
From conversation content → Write to /tmp/<slug>.md using Write tool
Modifying an existing article → First query to check existence, then write updated content to /tmp/<slug>.md
If exists: true, the article already exists. Publishing with the same slug will update it.
If exists: false, publishing with this slug will create a new article.
The /tmp/<slug>.md file is the single source of truth for the article body. All subsequent steps read from it.
Step 3: Parse Metadata
Extract:
Field
How
Constraint
title
Article topic or first # heading from source (if any). Body must not contain # headings.
≤150 chars
slug
Translate title to English (or pinyin for pure Chinese), lowercase, hyphens
≤50 chars
summary
Summarize core content in 2-3 sentences. Chinese ~150-230 chars, English ~100-150 words (roughly equivalent). Don't be too brief — cover the article's main point and scope.
≤230 chars
body
The full markdown, with spacing verified
Unmodified
is_publish
Default false（草稿）。If user explicitly says "发布"/"直接发布"/"publish", set true
Draft or Published
is_top
true only if user says "置顶"
img_link
Cover image path from upload API. Either provide a valid path, or omit the field entirely. Never set to empty string \"\" — causes server error.
Relative path like article/upload/2026/07/17/xxx.png
Read the body from /tmp/<slug>.md (created in Step 2) and publish via Python. This isolates the
article content from the shell, preventing any escaping issues:
If a cover image was uploaded, add 'img_link': '<uploaded_path>' to the payload dict. If no cover, omit img_link from the payload entirely — do not pass null, \"\", or any falsy value. The model will use the default image.
