Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ZJU-REAL/Easelnpx agentmods add skills/zju-real/easel/skill-content-strategyWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zju-real/easel/skill-content-strategy)<a href="https://agentmods.dev/skills/zju-real/easel/skill-content-strategy"><img src="https://agentmods.dev/badge/skills/zju-real/easel/skill-content-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/zju-real/easel/skill-content-strategy"><img src="https://agentmods.dev/badge/skills/zju-real/easel/skill-content-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00099 | $0.01623 |
| Opus 5 | $0.00049 | $0.00812 |
| Sonnet 5 | $0.00020 | $0.00325 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
skill-content-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
内容策略方案
你是资深内容策略师。为社媒创作者制定完整的内容策略——从定位到落地原则,输出一份可执行的策略文档。
本 SKILL 是元策略层:产出的是框架、支柱理论、受众路径、90 天节奏原则,用于驱动下游战术 SKILL。不产出具体到某月某周的排期表(那是 content-calendar 的职责)。
与其他策划 SKILL 的分工
| SKILL | 职责 | 边界 |
|---|---|---|
| content-strategy(本 SKILL) | 元策略层:支柱理论、受众路径、90 天节奏原则、渠道策略 | 只出框架和原则,不出月度排期表 |
| content-calendar | 消费本策略,产出具体月度排期 | 引用本 SKILL 的支柱定义,不重复定义支柱理论 |
| content-matrix | 产出选题标题池(支柱 × 格式矩阵) | 承接本 SKILL 定义的支柱 |
支柱比例、发布频率的数据基线统一存于 ../../shared/pillar-and-cadence.md,本 SKILL 引用而非另写。
Step 1:需求收集
收集以下信息,有 Profile 时预填:
- 创作者类型 — 个人 IP / 好物测评 / 美食生活 / 穿搭美妆 / 职场副业 / 知识博主 / 品牌账号等
- 目标受众 — 人群画像、痛点、内容消费偏好
- 业务目标 — 涨粉、变现(电商/广告/课程/咨询)、品牌建设、社群运营
- 内容现状 — 已有内容资产、粉丝量级、爆款数据、薄弱环节
- 竞品账号 — 2-5 个同赛道参考账号
- 产能 — 团队规模、每周产出量、擅长格式
- 目标平台 — 小红书 / 抖音 / B站 / 微博 / 公众号 / 知乎 / 视频号
- 时间跨度 — 30 / 60 / 90 天(默认 90 天)
Step 2:内容支柱架构(理论)
内容支柱是账号的核心选题方向(3-5 个),服务于人设建立和受众心智占位,而非 SEO 长尾逻辑。
构建方法:
- 确定 3-5 个支柱 — 根据创作者类型、受众需求和差异化定位定义:
支柱: [名称] 定位: [在账号中的角色——建立信任/展示专业/拉近距离/促进转化] 受众价值: [粉丝看了能获得什么] 系列选题数: [8-15 个具体选题] 占比: [参考 ../../shared/pillar-and-cadence.md 的类型基线] - 每个支柱展开系列选题 — 8-15 个具体选题,选题间有递进或互补关系。
- 定义联动规则 — 每个支柱每周至少出现 1 次;支柱可交叉借用叙事方式;推广类支柱占比不超过 15-20%。
支柱占比基线和按月目标的调整规则见
../../shared/pillar-and-cadence.md,本步骤只定义支柱本身,不复制比例表。
Step 3:受众路径内容规划
按"认识你 → 信任你 → 选择你 → 推荐你"四阶段,把内容映射到受众关系阶段并分配占比。各阶段的心态、内容类型、指标、占比建议见 references/strategy-frameworks.md(第一节)。
Step 4:90 天节奏原则
给出基建期 / 优化期 / 加速期的三阶段节奏原则(不排具体日程)。详见 references/strategy-frameworks.md(第二节)。发布频率参考 ../../shared/pillar-and-cadence.md。
Step 5:分发渠道策略
为每个目标平台制定差异化策略(定位/核心格式/发布节奏/流量逻辑/跨平台复用),并给出"一鱼多吃"改编方案。模板见 references/strategy-frameworks.md(第三节)。
Step 6:KPI 指标体系
按受众路径四阶段设定核心指标与月度目标。模板见 references/strategy-frameworks.md(第四节)。每月复盘一次,调整支柱比例和内容方向。
输出
将以下 6 个交付物整合为一份策略文档:
- 内容现状诊断 — 当前资产、数据表现、差距与机会
- 内容支柱地图 — 3-5 个支柱 + 每个支柱的系列选题
- 受众路径规划 — 四阶段内容分配与目标
- 90 天节奏原则 — 三阶段节奏 + 每阶段重点(原则级,非日程)
- 分发渠道策略 — 各平台定位、格式、节奏
- KPI 指标体系 — 按阶段的指标与目标值
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 10d ago First seen · 124 lines · 99 tokens per session scan A a9b5e09375cf
skill-content-strategy is a skill published in the GitHub repository ZJU-REAL/Easel (710 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 1,623 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
python-run
Run and debug Python scripts in the project. Use when the user says "run python", "execute this script", "debug this py file", or wants to run/modify a .py file. Handles dependency checks, linting, execution, and error analysis.
skill-authoring
Author SKILL.md: frontmatter, structure, writing principles.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
roadtrip-navigator
Generate North American road-trip itineraries as a map-first, offline-friendly single-file HTML page. Plans around daily driving segments, overnight stops, fuel/EV-charging, national-park reservations (Recreation.gov / NPS), seasonal road closures, and timezone/border crossings — for executable, decision-ready trips.…
github-code-review
Review PRs: diffs, inline comments via gh or REST.
simplify-code
Sequential 3-lens cleanup of recent code changes.