mcpbeat Sign in

Self Media Content Strategy Agent Skill

把账号定位和业务目标转成可执行的自媒体内容策略。用于账号冷启动、重新定位、制定内容配比、规划系列栏目、建立选题池、安排周度或月度内容日历、评估产能和确定平台分工。单篇内容写作或纯数据复盘不使用此 Skill。

1k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
343
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/yanhua1010/self-media-content-workflow --skill self-media-content-strategy

The instruction itself

5 sections, as written by the author

内容策略

输入

优先读取已有账号说明、历史内容和数据。只有缺失且会改变策略时,确认:

  • 领域、人设和目标受众。
  • 业务目标和本阶段优先级。
  • 已有平台、账号阶段和历史表现。
  • 更新频率、团队规模和可投入时间。
  • 可持续的一手证据和内容来源。
  • 商业目标、品牌边界和不能做的内容。

可从 account-profile-template.md 建立账号档案。

方法

1. 写清定位承诺

用一句话说明“谁,为谁,持续提供什么价值,凭什么相信”。定位必须能约束选题,不写空泛口号。

2. 将目标映射为内容类型

| 类型 | 主要作用 | 常见形式 |

|---|---|---|

| 涨粉 | 被新用户发现 | 教程、避坑、反常识、趋势解释 |

| 互动 | 激活现有受众 | 问题、选择、争议、共同经历 |

| 信任 | 建立专业度和人格 | 案例、幕后、复盘、深度方法 |

| 转化 | 承接产品或服务 | 测评、答疑、案例、合作内容 |

不要套用固定比例。根据账号阶段、历史数据和产能提出初始比例,并明确这是待验证假设。

3. 建立选题池

每条选题至少记录:

  • 母题和一句话钩子。
  • 内容目标和目标受众。
  • 主平台和可扩展平台。
  • 一手证据和仍缺证据。
  • 时效窗口、优先级和预计成本。
  • 是否属于系列。

使用 topic-pool-template.md。优先留下可持续生产、能强化定位和有真实证据的选题。

4. 设计系列栏目

将零散选题收敛为 2 到 4 个栏目。每个栏目写清内容承诺、证据来源、适合平台、更新频率和停止条件。

5. 生成内容日历

先分配产能,再排日期。保留热点插槽,避免把未来内容全部写死。每个周期只设置一个可归因的实验变量。使用 content-calendar-template.md。只有用户明确要求提醒且当前环境提供调度能力时,才创建排期提醒。

输出

交付:

  • 一句话定位。
  • 阶段目标和内容配比假设。
  • 2 到 4 个栏目。
  • 选题池。
  • 周度或月度日历。
  • 成功指标、停止条件和本周期唯一实验。

如果历史数据不足,明确写“建立基线”,不伪造精确目标。

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Test Driven Development
by w95
×7

Use when implementing any feature or bugfix, before writing implementation code

2k tokens
Writing Plans
by ZhanlinCui
×4

Use when you have a spec or requirements for a multi-step task, before touching code

816 tokens
Writing Skills
by ZhanlinCui
×4

Use when creating new skills, editing existing skills, or verifying skills work before deployment

26k tokens scripts
Crafting Effective Readmes
by softaworks
×3

Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.

15k tokens
Humanizer
by softaworks
×3

| Remove signs of AI-generated writing from text. Use when editing or reviewing text to make it sound more natural and human-written. Based on Wikipedia's inflated symbolism, promotional language, superficial -ing analyses, vague attributions, em dash overuse, rule of three, AI vocabulary words, negative parallelisms, and excessive conjunctive phrases.

6k tokens
Opentrons Integration
by christophacham
×3

Official Opentrons Protocol API for OT-2 and Flex robots. Use when writing protocols specifically for Opentrons hardware with full access to Protocol API v2 features. Best for production Opentrons protocols, official API compatibility. For multi-vendor automation or broader equipment control use pylabrobot.

9k tokens scripts

How to use it

Copy the folder

Take yanhua1010/self-media-content-strategy from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.