Back to skills
SKILL.md
Content Strategy
ASecurityContent strategy and sales briefing. Build content pillars from sales data, create editorial calendar, and produce sales briefs with pipeline highlights. Triggers on: content plan, content strategy, editorial calendar, sales brief, what should we post.
- 417 stars
- 0 votes
- 0 copies
- 4 views
- Added September 8, 2026
Security analysis
100/100npx -y skills add infometa/workbuddyskills --skill content-strategy --agent claude-codeAre you the author of Content Strategy?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/infometa-content-strategy)---
name: content-strategy
description: >-
Content strategy and sales briefing. Build content pillars from sales data, create editorial calendar, and produce sales briefs with pipeline highlights.
Triggers on: content plan, content strategy, editorial calendar, sales brief, what should we post.
---
# Content Strategy
## Overview
Turn sales data into a content machine. This skill extracts customer language from real conversations, builds revenue-tied content pillars, creates a 4-week editorial calendar, and produces pipeline-matched sales briefs — so every piece of content drives deals forward.
## Workflow
### Step 1: Extract Customer Language
From sales conversations, support tickets, and CRM notes, pull:
- **Exact phrases** customers use to describe their problems
- **Common objections** that kill deals
- **Win quotes** — what happy customers say after closing
- **Pain frequency** — which problems come up most often
Output a "Customer Voice Bank" organized by theme.
### Step 2: Build Content Pillars
Create 3-5 content pillars, each tied to a revenue driver:
| Pillar | Revenue Driver | Customer Pain | Content Angle |
|--------|---------------|---------------|---------------|
| [Pillar 1] | [What revenue it drives] | [Pain it addresses] | [Angle/hook] |
| [Pillar 2] | ... | ... | ... |
Each pillar must pass the "so what?" test — if you can't explain how it connects to pipeline or revenue, replace it.
### Step 3: Create 4-Week Editorial Calendar
For each week, specify:
```
## Week [N] — [Theme]
| Day | Channel | Format | Pillar | Title/Hook | CTA |
|-----|---------|--------|--------|------------|-----|
| Mon | 抖音 | 短视频 30s | Pillar 1 | [钩子] | [CTA] |
| Tue | 小红书 | 图文 6 张 | Pillar 2 | [标题] | [CTA] |
| Wed | 公众号 | 长文 | Pillar 1 | [标题] | [CTA] |
| Thu | 视频号 | 直播切片 | Pillar 3 | [标题] | [CTA] |
| Fri | 企微社群 | 案例分享 | Pillar 2 | [标题] | [CTA] |
```
Rules:
- 一周至少 3 个跨渠道触点
- 每篇内容至少改成 2 种格式复用(公众号长文 → 小红书图文 → 视频号短视频)
- CTA 按管道阶段定(漏斗顶 → 教育引流加企微,漏斗底 → 预约咨询/下单)
### Step 4: Pipeline Snapshot & Stage-Matched Outreach
Produce a sales brief:
```
## Sales Brief — [Date]
### Pipeline Overview
| Stage | Count | Total Value | Stalled > 7 days |
|-------|-------|-------------|-------------------|
| 方案沟通 | 3 | ¥450K | 1 |
| 商务谈判 | 2 | ¥300K | 0 |
### Stage-Matched Content
| Stage | Recommended Content | Delivery Method |
|-------|-------------------|----------------|
| 方案沟通 | 同行业案例: [X] | 企微 1v1 发送 |
| 商务谈判 | ROI 测算表 | 企微/邮件附件 |
### Stalled Deal Actions
| Deal | Days Stalled | Recommended Nudge |
|------|-------------|-------------------|
| [Deal A] | 12 | 推送行业基准报告 |
```
### Step 5: Distribution Plan with Repurposing
For each content piece, specify:
- 主投渠道和格式
- 2+ 衍生格式(如:公众号长文 → 小红书图文 → 视频号短视频 → 企微社群素材)
- 各渠道的最佳发布时间(抖音晚 8-10 点、小红书午休 12-14 点、公众号 7-9 点或 21-22 点)
- 平台关键词/话题标签(抖音 # 话题、小红书关键词、公众号长尾搜索词)
## Data Requirements
- Sales conversation transcripts or notes
- CRM pipeline data (stage, value, stalled deals)
- Existing content inventory (to avoid duplication)
- If any data is missing, ask the user — do not fabricate customer quotes or pipeline figures
## Notes
- Content pillars must tie directly to revenue, not vanity metrics
- Use exact customer language in headlines — don't paraphrase into marketing jargon
- Editorial calendar should be immediately actionable, not aspirational
Attribution
Related skills
View all in business →Comments
Loading comments…
Newsletter
Get the weekly list of safe new skills, and the ones we pulled.