Article Title Generation Agent Skill

Generates platform-tailored, fact-grounded article headlines and title variations for Chinese social media and publishing channels.

Context cost
37k tokensestimated from the bundle, loaded when it triggers
Bundle
12 files · 165.4 kB1 script among them — read before you run
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

为已完成的文章、片段或“旧标题 + 正文”生成和优化可兑现、平台适配的文章标题,支持微信公众号、小红书、知乎、微博和头条号。当用户说“起标题”“取标题”“给几个标题”“改标题”或“标题优化”时适用;also use for requests to generate article-title options, rewrite an article headline, or improve an article title. 不用于选题策划、正文写作、封面/开头创作、视频标题、SEO title tags、落地页或广告 headline、邮件主题、其他营销文案标题,或书籍、产品、课程命名;不接受 URL、DOCX、PDF 或 TXT 作为文章输入。绝不新增原文没有的时间、数字、权威、引语、因果、冲突或结果。

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

content

The skill itself

A skill is instructions the model reads, so you can see what you are getting: below is the start of its SKILL.md. The front matter loads with every session, the body loads when the skill triggers, and the whole file comes with the install.

SKILL.md28.6 kB · preview
--- name: title-options display_name: Article Title Generation display_name_zh: 文章标题生成 ---
9# Title Options / 标题选项
10
11仅为已完成内容生成文章标题。允许表达有张力,但每个标题都必须被输入正文完整兑现。
12
13Generate article titles only from finished content. Permit tension in wording, but require the supplied content to fully support every title.
14
15## Orchestrated Provider Route / 总控 Provider 路由
16
17Before the standalone workflow, inspect structured requests. If a request contains any of
18contract: content-production-provider/v2, capability: title_generation,
19provider_contract: title-generation-v1, or content-production-provider: title-generation-v1,
20MUST use [references/orchestrated-provider.md](references/orchestrated-provider.md) and
21scripts/provider-contract.mjs. A partial, conflicting, or invalid marker MUST return structured
22BLOCKED; NEVER fall back to standalone mode.
23
24Provider mode is the only exception to conversation-only output. It NEVER overwrites or edits the
25final_draft source. Without a provider marker, the standalone conversation workflow below remains
26unchanged and creates no files unless the user separately requests a file edit.
27
This is a preview of SKILL.md. Download or install the skill to get the whole thing.
In the file
SKILL.md3,713 words
Files12
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈120
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
36,880
on trigger
The instruction body and 11 supporting files, read only when the skill fires.
18.5%
of a 200k window
Ten skills this size would not fit in the window together.
050k100k150k200k context window

37k tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Heavy. Teams tend to install this one per project rather than globally, and load it only when the job comes up.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md: the start of it is shown above, and the whole file comes with the install.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

12 files, 165.4 kB on disk. Mostly text — the instructions the model reads — with 1 script in it that your client would run only if the instructions tell it to. 1 file of its source is not in the download — listed after these, with why.

  • SKILL.md28.6 kB
  • LICENSE1.1 kB
  • NOTICE2.8 kB
  • README.md2.6 kB
  • README.zh.md2.2 kB
  • agents/openai.yaml0.4 kB
  • assets/icon.svg0.4 kB
  • references/content-routing.md30.8 kB
  • references/orchestrated-provider.md3.5 kB
  • references/platform-playbooks.md32.8 kB
  • references/title-system.md42.8 kB
  • scripts/provider-contract.mjs17.4 kB

Not in the download

Not carried is a type a skill download does not hold. Take it from its source.

  • assets/icon.pngnot carried
What is not in it

A skill installs nothing and depends on nothing: it is a folder your client reads. This one carries 1 script beside the text, so the download is 12 files — not the whole of its source: 1 file is left out. It is listed under the files, with why. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Article Title Generation · 37k tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/article-title-generation/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/article-title-generation" ] && { [ ! -e .claude/skills/article-title-generation ] || { mv .claude/skills/article-title-generation "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/article-title-generation" .claude/skills/ && echo "Installed .claude/skills/article-title-generation"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add gaodalong/article-title-generation

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/article-title-generation/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/article-title-generation/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/article-title-generation" ] && { [ ! -e ~/.claude/skills/article-title-generation ] || { mv ~/.claude/skills/article-title-generation "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/article-title-generation" ~/.claude/skills/ && echo "Installed ~/.claude/skills/article-title-generation" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/article-title-generation/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where. It appears as title-options in Gemini CLI, Codex, Copilot and Grok (its own name); Claude Code lists it by the folder name, article-title-generation. Not in this download: 1 file of its source (which one, and why). Take it from its source.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referencegaodalong/article-title-generation

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill