Load Context First
Before executing this skill, read the following files from the project folder if they exist:
- USER.md — who the user is, how they think, how they work
- BUSINESS.md — their business, products, positioning, brand voice, content strategy
- ICP.md — their ideal customer, their language, their fears, what makes them buy
- Voice or brand voice skill — look for any installed skill related to voice, tone, or brand voice and apply it automatically
- Any additional context provided by the user in this session
Use all context silently. Do not reference or summarize files unless asked.
Content Map
Purpose: Transform an IP map (or list of topics/assets) into a detailed 4-week content plan. Every piece of content maps back to a specific intellectual property asset, ensuring consistency and strategic coverage.
When to Activate
Use this skill when:
- User has an IP map and wants a content plan built from it
- User wants a month of content planned out
- User mentions "content map", "content plan from IP", or "month of content"
- User has stories, frameworks, and topics they want to turn into a publishing calendar
Required Input
- IP Map (from the ip-mapper skill) OR a list of topics, stories, and frameworks
- Platforms the client publishes on
- Publishing cadence (or let this skill recommend one)
- Any upcoming launches, events, or themes to plan around
Process
Step 1: Analyze Available IP
Review the IP map and categorize assets by:
- Freshness — Has this been used recently? Never? Overused?
- Depth — Is this a full newsletter topic or a social post?
- Audience stage — Does this attract new readers, nurture existing ones, or convert?
- Platform fit — Which format/platform suits this asset best?
Step 2: Build the 4-Week Plan
Each week follows a content rhythm:
- 1 Main Piece — Newsletter, long-form article, or video (the hub content)
- 3 Social Posts — Platform-native posts derived from or related to the main piece
- 1 Substack Note / Quick Hit — Short-form insight to keep presence between main pieces
Weekly theme: Each week anchors on one IP asset (a framework, story, or topic area) and explores it from multiple angles.
Step 3: Map Every Piece to IP
Every content piece must trace back to:
- A specific story, framework, opinion, or topic from the IP map
- A clear angle (which content lens: story, observation, contrarian, how-to, etc.)
- A target audience stage (awareness, trust, conversion)
Output Format
# 4-Week Content Map: [Client Name]
> Built from: [IP Map / Topic List]
> Platforms: [List of platforms]
> Date range: [Start — End]
---
## Recommended Cadence
| Platform | Frequency | Best Days |
|----------|-----------|-----------|
| Newsletter | [1x/week] | [Day] |
| LinkedIn | [3x/week] | [Days] |
| Twitter/X | [Daily] | [Any] |
| Substack Notes | [2x/week] | [Days] |
| Instagram | [2-3x/week] | [Days] |
---
## Week 1: [Theme — tied to IP asset]
**IP Focus:** [Framework/Story/Topic being featured]
**Audience Goal:** [Awareness / Trust / Conversion]
| Day | Platform | Format | Title/Hook | IP Asset | Lens |
|-----|----------|--------|------------|----------|------|
| Mon | Newsletter | Thought Leadership | [Title] | [Framework X] | How-to |
| Tue | LinkedIn | Post | [Hook line] | [Framework X] | Observation |
| Wed | Twitter/X | Thread | [Hook tweet] | [Story Y] | Story |
| Thu | Substack | Note | [Opening line] | [Opinion Z] | Contrarian |
| Fri | LinkedIn | Post | [Hook line] | [Framework X] | Lesson |
| Sat | Twitter/X | Standalone | [Tweet] | [Framework X] | Tip |
---
## Week 2: [Theme]
**IP Focus:** [Asset]
**Audience Goal:** [Stage]
| Day | Platform | Format | Title/Hook | IP Asset | Lens |
|-----|----------|--------|------------|----------|------|
[Full table for week 2...]
---
## Week 3: [Theme]
[Same structure...]
---
## Week 4: [Theme]
[Same structure...]
---
## IP Coverage Summary
| IP Asset | Times Used | Platforms | Notes |
|----------|-----------|----------|-------|
| [Framework X] | [3] | Newsletter, LinkedIn, Twitter | Well covered |
| [Story Y] | [1] | Twitter | Could expand to newsletter |
| [Opinion Z] | [2] | Substack, LinkedIn | Strong engagement potential |
| [Topic A] | [0] | — | **Gap — schedule for next month** |
---
## Month-End Review Questions
1. Which pieces got the most engagement?
2. Which IP assets resonated most?
3. What topics should we double down on?
4. What gaps remain in the IP coverage?
5. What new stories or frameworks emerged this month?
Quality Checklist
1---2name: content-map3description: Turn an IP map document into a 4-week content plan with topics, angles, and formats. Each piece maps back to a specific IP asset. Includes posting cadence and platform recommendations. Use when user wants a "content plan", "content calendar from IP", or to plan a month of content from existing intellectual property.4---5
6## Load Context First
7
8Before executing this skill, read the following files from the project folder if they exist:
9
101. **USER.md** — who the user is, how they think, how they work
112. **BUSINESS.md** — their business, products, positioning, brand voice, content strategy
123. **ICP.md** — their ideal customer, their language, their fears, what makes them buy
134. **Voice or brand voice skill** — look for any installed skill related to voice, tone, or brand voice and apply it automatically
145. Any additional context provided by the user in this session
15
16Use all context silently. Do not reference or summarize files unless asked.
17
18---
19
20# Content Map
21
22**Purpose:** Transform an IP map (or list of topics/assets) into a detailed 4-week content plan. Every piece of content maps back to a specific intellectual property asset, ensuring consistency and strategic coverage.
23
24## When to Activate
25
26Use this skill when:
27- User has an IP map and wants a content plan built from it
28- User wants a month of content planned out
29- User mentions "content map", "content plan from IP", or "month of content"
30- User has stories, frameworks, and topics they want to turn into a publishing calendar
31
32## Required Input
33
34- **IP Map** (from the ip-mapper skill) OR a list of topics, stories, and frameworks
35- **Platforms** the client publishes on
36- **Publishing cadence** (or let this skill recommend one)
37- **Any upcoming launches, events, or themes** to plan around
38
39## Process
40
41### Step 1: Analyze Available IP
42
43Review the IP map and categorize assets by:
44- **Freshness** — Has this been used recently? Never? Overused?
45- **Depth** — Is this a full newsletter topic or a social post?
46- **Audience stage** — Does this attract new readers, nurture existing ones, or convert?
47- **Platform fit** — Which format/platform suits this asset best?
48
49### Step 2: Build the 4-Week Plan
50
51**Each week follows a content rhythm:**
52- **1 Main Piece** — Newsletter, long-form article, or video (the hub content)
53- **3 Social Posts** — Platform-native posts derived from or related to the main piece
54- **1 Substack Note / Quick Hit** — Short-form insight to keep presence between main pieces
55
56**Weekly theme:** Each week anchors on one IP asset (a framework, story, or topic area) and explores it from multiple angles.
57
58### Step 3: Map Every Piece to IP
59
60Every content piece must trace back to:
61- A specific story, framework, opinion, or topic from the IP map
62- A clear angle (which content lens: story, observation, contrarian, how-to, etc.)
63- A target audience stage (awareness, trust, conversion)
64
65## Output Format
66
67```markdown
68# 4-Week Content Map: [Client Name]
69
70> Built from: [IP Map / Topic List]
71> Platforms: [List of platforms]
72> Date range: [Start — End]
73
74---
75
76## Recommended Cadence
77
78| Platform | Frequency | Best Days |
79|----------|-----------|-----------|
80| Newsletter | [1x/week] | [Day] |
81| LinkedIn | [3x/week] | [Days] |
82| Twitter/X | [Daily] | [Any] |
83| Substack Notes | [2x/week] | [Days] |
84| Instagram | [2-3x/week] | [Days] |
85
86---
87
88## Week 1: [Theme — tied to IP asset]
89
90**IP Focus:** [Framework/Story/Topic being featured]
91**Audience Goal:** [Awareness / Trust / Conversion]
92
93| Day | Platform | Format | Title/Hook | IP Asset | Lens |
94|-----|----------|--------|------------|----------|------|
95| Mon | Newsletter | Thought Leadership | [Title] | [Framework X] | How-to |
96| Tue | LinkedIn | Post | [Hook line] | [Framework X] | Observation |
97| Wed | Twitter/X | Thread | [Hook tweet] | [Story Y] | Story |
98| Thu | Substack | Note | [Opening line] | [Opinion Z] | Contrarian |
99| Fri | LinkedIn | Post | [Hook line] | [Framework X] | Lesson |
100| Sat | Twitter/X | Standalone | [Tweet] | [Framework X] | Tip |
101
102---
103
104## Week 2: [Theme]
105
106**IP Focus:** [Asset]
107**Audience Goal:** [Stage]
108
109| Day | Platform | Format | Title/Hook | IP Asset | Lens |
110|-----|----------|--------|------------|----------|------|
111[Full table for week 2...]
112
113---
114
115## Week 3: [Theme]
116
117[Same structure...]
118
119---
120
121## Week 4: [Theme]
122
123[Same structure...]
124
125---
126
127## IP Coverage Summary
128
129| IP Asset | Times Used | Platforms | Notes |
130|----------|-----------|----------|-------|
131| [Framework X] | [3] | Newsletter, LinkedIn, Twitter | Well covered |
132| [Story Y] | [1] | Twitter | Could expand to newsletter |
133| [Opinion Z] | [2] | Substack, LinkedIn | Strong engagement potential |
134| [Topic A] | [0] | — | **Gap — schedule for next month** |
135
136---
137
138## Month-End Review Questions
139
1401. Which pieces got the most engagement?
1412. Which IP assets resonated most?
1423. What topics should we double down on?
1434. What gaps remain in the IP coverage?
1445. What new stories or frameworks emerged this month?
145```
146
147## Quality Checklist
148
149- [ ] 4 full weeks planned with daily content
150- [ ] Every piece maps to a specific IP asset
151- [ ] Content lenses vary (not all how-to, not all story)
152- [ ] Main piece each week anchors the theme
153- [ ] Social content derives from or supports the main piece
154- [ ] Platform cadence is realistic for the client
155- [ ] Audience stages are balanced (awareness + trust + conversion)
156- [ ] IP coverage summary identifies gaps
157- [ ] No IP asset overused (variety across weeks)
158- [ ] Plan is actionable and ready to execute
majiayu000