SuperAPI AI Directory
Partner中文AI newsFavorites
Skillscontent-creator

content-creator

General & other

View repository

Updated 10-16 05:00

About this skill

Content Creator - Professional Content Creation Workflow

This Skill provides a complete workflow from style extraction, requirement analysis, and in-depth research to final creation. It strictly follows the order of "analyze first, then research, then create" to ensure output quality.

Boundary Description (Important)

This Skill is only used for content creation from 0 to 1, and in the following situationsdo not use this Skill：

Scenario Handling Method
Existing content needs to be formatted and published This is the publishing stage, not the creation stage
Simple text editing, format adjustment Use MCP tools directly
Translating, summarizing, or rewriting existing content Use Claude's built-in capabilities directly
Finding existing note content Use note search tools

One-sentence judgment: If the user says "help me write..." or "I want to write...", use this Skill; if the user says "format..." "publish..." or "export...", it means the content is already complete and creation is not needed.

Contract

Input Contract

Trigger Conditions：

  • "Help me write an article"
  • "Write a WeChat official account/Xiaohongshu/Zhihu answer"
  • "Create content about XX"
  • "Write a draft"
  • "Write in the style of this piece"
  • "Analyze my writing style"
  • "Extract a writing template"
  • "Write imitating this style"

Input Types：

  1. Sample article(optional): a reference article used to extract writing style
  2. Creation topic: a one-sentence description of what you want to write (required)
  3. Target platform: WeChat official account/Xiaohongshu/Zhihu/Toutiao, etc. (optional, defaults to WeChat official account)
  4. Additional requirements: length, tone, specific key points (optional)

Prerequisites：

  • If style extraction is needed, the sample must be > 500 characters and be a complete article
  • The creation topic must be clear (the user can be guided to refine it)

Output Contract

Output Content：

File Description
persona.md Writing style profile (if extracted based on a sample)
brief.md Requirements document (goals, audience, core information)
outline.md Article outline (structure, key points, research needs)
research_notes.md Research notes (internal materials + external materials)
draft.md Draft content
final.md Final content

Quality Assurance：

  • Strictly follow the extracted writing style
  • Create based on research materials, not improvisation
  • Comply with the content standards of the target platform

Error Contract

Error Scenario Handling Method
Sample is too short Prompt to provide a longer, more complete sample (over 500 words)
Unclear topic Guide the user to answer: What are you writing? Who is it for? What goal do you want to achieve?
Insufficient research material Proactively ask the user to provide more background information or keywords

Core workflow

Mandatory 6-step process,cannot be skipped：

风格画像 → 需求确认 → 大纲设计 → 深度研究 → 文章创作 → 定稿交付

Step 1: Style Persona

Goal: Establish or load the user's writing style persona.

Execution：

  1. Check whether there is already persona.md or a historical template
  2. If there is a sample article, extract style features:
    • Sentence preferences (long/short sentences, rhythm)
    • Vocabulary characteristics (level of professionalism, degree of colloquialism)
    • Structural habits (opening style, paragraph length)
    • Emotional tone (serious/light, rational/emotional)
  3. Generate persona.md and confirm with the user

Key validation point: Without a style persona, you must not enter the creation stage

Step 2: Brief Confirmation

Goal: Fully understand the writing requirements.

Required questions：

  • What is the purpose of this article? (Inform/persuade/entertain)
  • Who is the target reader?
  • What is the core information/viewpoint?
  • Where will it be published? (WeChat Official Account/Xiaohongshu/Zhihu...)
  • Roughly how long does it need to be?
  • Deadline?

Output：brief.md requirements document

Step 3: Outline Design

Goal: Create a clear article structure.

Content：

  • Title (working title)
  • Opening approach
  • Main structure (2-5 sections)
  • Key points for each section
  • Ending approach
  • Research needs marking: Which arguments need supporting evidence

Output：outline.md outline document, requires user confirmation

Step 4: In-depth Research

Goal: Collect supporting materials,this step cannot be skipped。

Internal research(WPS Notes history):

  • Use search_notes to search for relevant materials in the user's historical notes
  • Use search_note_content to precisely search for keywords within relevant notes
  • Find reusable cases, data, and expressions

External research(web search):

  • Search for the latest industry trends and data reports
  • Find authoritative viewpoints and case support
  • Understand hot topics and discussions

Output：research_notes.md research notes

Key validation point: Each main argument needs 2+ supporting materials

Step 5: Article Creation

Goal: Based on all the above preparation, write the first draft.

Creation principles：

  1. Style consistency: Strictly follow the persona.md style persona
  2. Structural fidelity: Expand according to the outline.md framework
  3. Material integration: naturally integrate research_notes.md 's research findings
  4. Requirement fit: satisfy brief.md all requirements in

Output：draft.md draft

Step 6: Final delivery (Delivery)

Goal: revise based on feedback and output the final draft.

Execute：

  1. Show draft.md to the user
  2. Collect feedback and revise
  3. Save final.md final draft
  4. (Optional) Save the article to the sample library for future style extraction

Common orchestration patterns

Pattern 1: Creation based on a sample (recommended)

When the user provides a reference article and wants to create in imitation of its style:

检查 persona.md → 如不存在，分析样张提取风格 → 确认需求 → 设计大纲 → 深度研究 → 创作 → 定稿

Key tools：

  • wps-read.py Read the sample article
  • extract-template.py Extract the style template

Pattern 2: Creation on a brand-new topic

When the user only has a topic idea and no specific style requirements:

检查 persona.md → 使用通用风格或加载历史画像 → 需求访谈 → 设计大纲 → 深度研究 → 创作 → 定稿

Pattern 3: Rapid iterative creation

When the user is dissatisfied with an existing draft and needs major revisions:

加载已有 brief/outline → 重新确认需求变化 → 调整大纲 → 补充研究 → 重写 → 定稿

Troubleshooting

Style extraction fails

Symptom：extract-template.py reports an error or the extraction result is empty Cause: the sample article's section structure is unclear, the content is too short (<500 characters), or there is an XML parsing error Solution：

  1. Check whether the sample is a complete article (has a beginning and an end)
  2. Make sure the sample is > 500 characters
  3. Read the sample manually and observe the style characteristics directly

Insufficient research materials

Symptom：search_notes returns empty or irrelevant results Cause: inaccurate keywords, or the note library truly contains no related content Solution：

  1. Try synonym-expanded searches
  2. Use web search to supplement external materials
  3. Proactively ask the user for background materials

The user drastically changes requirements after outline confirmation

Symptom: the user says "No, that's not what I meant" Cause: misunderstanding during the requirements interview stage Solution：

  1. Do not directly modify the original outline; return to Step 2 to reconfirm requirements
  2. Update brief.md to record the new understanding
  3. Redesign the outline based on the new brief

MCP tool call fails

Symptom：mcp__wpsnote__search_notes and other tools report errors Cause: EDITOR_NOT_READY, BLOCK_NOT_FOUND, network issues Solution：

  1. Check whether the WPS Notes app is running properly
  2. Re-obtain the block_id (the ID changes after editing)
  3. Refer to wps-note SKILL's Troubleshooting

Creation deviates from the style

Symptom: the user says "This doesn't sound like my style" Cause: persona.md is not described specifically enough, or it was not strictly followed during creation Solution：

  1. Refine persona.md and add more specific examples
  2. Check paragraph by paragraph against persona.md during creation
  3. Rewrite key sentences in the user's original wording style

Integration with WPS Notes

After creation is complete, you can write directly to WPS Notes:

# 写入 WPS 笔记
python scripts/wps-write.py --input final.md --title "文章标题" --tags "公众号"

Write via MCP tool：

create_note({ title: "文章标题" }) → note_id
batch_edit({ note_id, operations: [
  { op: "replace", block_id, content: "<h1>标题</h1>..." }
]})

Resources (resource references)

  • Writing paradigm reference:references/writing-paradigm.md
  • WPS integration script:scripts/wps-read.py、scripts/wps-write.py
  • Style extraction script:scripts/extract-template.py

Examples (usage examples)

Example 1: Creating based on a sample

  • User: "Following the style of my article, write one about AI programming tools"
  • Skill：
    1. Analyze the sample → Extract persona.md
    2. Confirm requirements → Target readers are programmers, the purpose is to introduce tools
    3. Design outline → Three parts: introduction, comparison, recommendation
    4. In-depth research → Search for the latest information on AI programming tools
    5. Create first draft → Write in the style of the sample
    6. Finalize and deliver

Example 2: Creating on a new topic

  • User: "Help me write a WeChat official account article about time management"
  • Skill：
    1. Check/create persona (if the user has no specific sample, use a general style)
    2. Confirm requirements → Workplace audience, practical tips category
    3. Design outline
    4. In-depth research → Search for time management methodologies and cases
    5. Create first draft
    6. Finalize and deliver