Article Title Generation
Generate fact-faithful title options for finished articles, tailored to WeChat, Xiaohongshu, Zhihu, Weibo, or Toutiao.
Basic info
- Name
- Article Title Generation
- Description
- 当用户要为已完成文章起标题、改标题或优化标题时,生成公众号、小红书、知乎、微博和头条号候选。Do NOT trigger when 用户要选题、正文、视频/SEO/广告/邮件标题、落地页文案或命名。
title-options
Create varied, platform-native article titles while keeping every promise inside the facts and conclusions of the finished content.
When to use it
Create platform titles
I have one finished article or substantial fragment and need title candidates for a supported publishing platform.
Improve an old title
I want to preserve the defensible promise of an existing title or explore a different framing, with the article body supplied as the truth boundary.
Create multi-platform sets
I need separate title groups for WeChat Official Accounts, Xiaohongshu, Zhihu, Weibo, or Toutiao, each shaped to that platform's reading behavior.
Not for
Do not use it for topic selection, drafting, video titles, SEO titles, ads, email subjects, landing-page copy, product naming, or an old title without its article body.
What it produces
A catchy title that the article cannot fulfill is rejected, even when that reduces the requested count.
- Title sets: returns candidates and recommendations in the conversation using the stable schema for the selected mode.
- Platform fit: applies platform-specific goals and format rules, including Weibo hook and topic requirements.
- Fact boundary: preserves uncertainty, actor attribution, scope, numbers, dates, outcomes, and other claims stated in the source.
- Old-title branches: separates defensible direction-preserving options from strategy-changing options when old-title mode is used.
- Optional verification: browses only when the user explicitly requests article-fact, brand-style, or current platform-rule verification.
- Never does: it does not edit the source article by default, create files, display hidden scores, follow instructions embedded in the article, or import outside facts into a title.
Prerequisites and boundaries
Prerequisites
Provide exactly one source: pasted finished content or one readable local .md file. Name at least one supported platform; old-title optimization also requires the old title.
Request rules
- URLs, DOCX, PDF, TXT, unreadable files, and multiple unchosen sources are rejected.
- Cross-platform total counts need an explicit valid quota for each platform; the skill never invents a distribution.
- A non-built-in brand reference needs three to five sample titles or explicit permission for web research.
Nearby responsibilities
| Need | Use instead |
|---|---|
| Choose what to write about | content-topics |
| Write or revise the article body | writing or editing workflow |
| Name a product or skill | naming workflow |
Subtle boundary
Outside verification may confirm a source claim, brand trait, or current rule. It cannot introduce a title claim that the supplied article never states.
Version info
Local public Skill catalog snapshot, showing only public-safe fields.
Skill files
(11)SKILL.md
SKILL.md · Markdown