把账号定位和业务目标转成可执行的自媒体内容策略。用于账号冷启动、重新定位、制定内容配比、规划系列栏目、建立选题池、安排周度或月度内容日历、评估产能和确定平台分工。单篇内容写作或纯数据复盘不使用此 Skill。
npx skills add https://github.com/yanhua1010/self-media-content-workflow --skill self-media-content-strategy
优先读取已有账号说明、历史内容和数据。只有缺失且会改变策略时,确认:
可从 account-profile-template.md 建立账号档案。
用一句话说明“谁,为谁,持续提供什么价值,凭什么相信”。定位必须能约束选题,不写空泛口号。
| 类型 | 主要作用 | 常见形式 |
|---|---|---|
| 涨粉 | 被新用户发现 | 教程、避坑、反常识、趋势解释 |
| 互动 | 激活现有受众 | 问题、选择、争议、共同经历 |
| 信任 | 建立专业度和人格 | 案例、幕后、复盘、深度方法 |
| 转化 | 承接产品或服务 | 测评、答疑、案例、合作内容 |
不要套用固定比例。根据账号阶段、历史数据和产能提出初始比例,并明确这是待验证假设。
每条选题至少记录:
使用 topic-pool-template.md。优先留下可持续生产、能强化定位和有真实证据的选题。
将零散选题收敛为 2 到 4 个栏目。每个栏目写清内容承诺、证据来源、适合平台、更新频率和停止条件。
先分配产能,再排日期。保留热点插槽,避免把未来内容全部写死。每个周期只设置一个可归因的实验变量。使用 content-calendar-template.md。只有用户明确要求提醒且当前环境提供调度能力时,才创建排期提醒。
交付:
如果历史数据不足,明确写“建立基线”,不伪造精确目标。
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.
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.
Use when implementing any feature or bugfix, before writing implementation code
Use when you have a spec or requirements for a multi-step task, before touching code
Use when creating new skills, editing existing skills, or verifying skills work before deployment
Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.
| 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.
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.
Take yanhua1010/self-media-content-strategy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.