Run the Markster OS content playbook
Content Operator

Run the Markster OS content playbook. CHECK prerequisites (ICP, messaging guide, platform, time), DO theme definition + 30-day calendar + writing + distribution, VERIFY output before declaring done.
--- name: content description: 'Run the Markster OS content playbook. CHECK prerequisites (ICP, messaging guide, platform, time), DO theme definition + 30-day calendar + writing + distribution, VERIFY output before declaring done. Routes through ScaleOS G2 Warm.' --- # Content Operator --- ## CHECK Do not proceed past any failed check. **1. F1 complete?** Read `company-context/audience.md`. Required before this skill runs:
Overview
Required before this skill runs: - ICP defined with company type and specific pain - Decision-maker title named - Buying trigger identified
Manual install (npx, ZIP)
npx skills add markster/markster-os --skill content -g -a claude-codemkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/markster/markster-os/tar.gz/b1da50054715 \
| tar -xz -C ~/.claude/skills --strip-components=2 markster-os-b1da50054715/skills/contentNew-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/9babbdd6a40abd173a5f/content.zip" -OutFile "$env:TEMP\content.zip"; Expand-Archive "$env:TEMP\content.zip" -DestinationPath "$HOME\.claude\skills" -ForceConnects with Agent Alley MCP · agentalley.io/mcp
Files included
SKILL.md6.0 KB
Read the files here
markster/
Shared references2SKILL.md reads these from elsewhere in the repo. Not in the ZIP.
- article.mdplaybooks/warm/content/long-form/templates/13.6 KB
- linkedin-post.mdplaybooks/warm/content/short-form/templates/12.1 KB
Show the full text164 lines
Content Operator
CHECK
Do not proceed past any failed check.
1. F1 complete?
Read company-context/audience.md.
Required before this skill runs:
- ICP defined with company type and specific pain
- Decision-maker title named
- Buying trigger identified
If missing: "Content without ICP produces generic output that your buyer does not recognize themselves in. Open methodology/foundation/F1-positioning.md and complete it first."
2. Messaging guide complete?
Read company-context/messaging.md and methodology/foundation/messaging-guide.md.
Required:
- Problem statement in the buyer's words (not category descriptions)
- Mechanism (why this problem exists or has gotten worse now)
- At least one specific proof point with company type, result, and timeframe
If missing: "The messaging guide defines the language the content must use. Without it, every piece will sound like marketing copy the buyer ignores. Complete methodology/foundation/messaging-guide.md first."
3. Platform and time commitment
Ask the user:
- What platform do they primarily publish on? (LinkedIn, website, newsletter, X?)
- How much time per week can they dedicate to content? (30 min / 1 hour / 2+ hours)
This determines calendar density and format mix. Do not generate a calendar without knowing the platform.
4. Your archetype
Before writing content, confirm the business type. Route to the correct segment file.
| Your type | Read this first |
|---|---|
| B2B SaaS, devtools, marketplace | playbooks/segments/startup-archetypes/ |
| Agency, consulting, IT/MSP, advisory | playbooks/segments/service-firms/ |
| Residential or commercial services | playbooks/segments/trade-businesses/ |
The archetype determines which GOD Engine bricks matter most and what the G2 Warm motion looks like for your category.
DO
Run these four steps in order. Do not skip a step unless the user confirms it is already done.
Step 1: Define core theme
Help them define their theme as a one-sentence statement:
"I write about [specific intersection of ICP problem + your unique perspective]."
Push back if the theme is too broad. Use these as failure examples:
- "AI and marketing" -- not a theme
- "Business growth tips" -- not a theme
- "Why B2B service firms under 20 people should treat content as a sales warmer, not a brand play" -- this is a theme
The theme must:
- Be specific enough that their ICP recognizes themselves in it
- Have a point of view that goes beyond category average
- Be something they have evidence for (data, client results, direct experience)
If they cannot produce a theme that passes these three tests, do not move to Step 2. The calendar will be useless without it.
Step 2: Build a 30-day calendar
Generate 30 days of specific content ideas scaled to their time commitment:
| Time per week | Mix |
|---|---|
| 30 min | 8-10 short posts (under 150 words) |
| 1 hour | 4-6 LinkedIn posts + 4-6 short hooks |
| 2+ hours | 2 long-form + 6-8 LinkedIn posts + 6-8 short hooks |
For each calendar item, define:
- Specific topic (not "content marketing tips" -- something concrete and named)
- Core insight (one sentence -- what is the non-obvious thing?)
- Connection to ICP's situation (why does this matter to them right now?)
- Format (long-form / LinkedIn post / short hook)
Step 3: Write
For long-form content: Use playbooks/warm/content/long-form/templates/article.md
For short-form content: Use playbooks/warm/content/short-form/templates/linkedin-post.md
Apply these rules to every piece:
- First line must earn the scroll -- do not warm up, do not start with "I want to talk about"
- Problem-first framing -- ICP's situation before your solution
- Use buyer verbatims from the messaging guide -- their language, not yours
- No em dashes
- Short paragraphs (3-4 sentences max)
- One CTA per piece
- No category claims ("AI-powered," "data-driven," "full-service")
Step 4: Distribute
Remind them: publishing is not distribution.
Distribution plan for every piece published:
- Post natively on primary platform
- Send to email list (even if under 100 subscribers)
- Share in 1-2 relevant communities where ICP is active
- Repurpose each long-form piece into 3-5 short-form posts
- Reference in cold outreach as proof of expertise and point of view
VERIFY
Before this session ends:
1. Theme passes the specificity test?
Read the theme out loud. Can a stranger identify if they are the target audience from that one sentence? If not, rewrite.
2. 30-day calendar exists?
Confirm there are at least 10 specific, named topics -- not category titles but real arguments and angles.
3. First piece written?
Do not leave the session with only a calendar. Write at least the first piece before closing. Momentum beats planning.
4. Distribution plan set?
Confirm they know exactly what happens the day they publish. Not "I'll share it around" -- name the specific communities, the email list action, and whether it feeds into outreach.
5. Metrics baseline set?
State the starting numbers: "Before this content cycle, our profile visits from content are [X]. Success this month = at least [Y] inbound inquiries sourced from content."
Monthly metrics to track:
- Impressions per post
- Comments per post
- Profile visits from content
- Inbound inquiries sourced from content
Reference files
- Full playbook:
playbooks/warm/content/README.md - Long-form guide:
playbooks/warm/content/long-form/README.md - Short-form guide:
playbooks/warm/content/short-form/README.md - Article template:
playbooks/warm/content/long-form/templates/article.md - LinkedIn post template:
playbooks/warm/content/short-form/templates/linkedin-post.md - Messaging guide:
methodology/foundation/messaging-guide.md
| 1 | |
| 2 | name content |
| 3 | description 'Run the Markster OS content playbook. CHECK prerequisites (ICP, messaging guide, platform, time), DO theme definition + 30-day calendar + writing + distribution, VERIFY output before declaring done. Routes through ScaleOS G2 Warm.' |
| 4 | |
| 5 | |
| 6 | # Content Operator |
| 7 | |
| 8 | |
| 9 | |
| 10 | ## CHECK |
| 11 | |
| 12 | Do not proceed past any failed check. |
| 13 | |
| 14 | **1. F1 complete?** |
| 15 | |
| 16 | Read `company-context/audience.md`. |
| 17 | |
| 18 | Required before this skill runs: |
| 19 | ICP defined with company type and specific pain |
| 20 | Decision-maker title named |
| 21 | Buying trigger identified |
| 22 | |
| 23 | If missing: "Content without ICP produces generic output that your buyer does not recognize themselves in. Open `methodology/foundation/F1-positioning.md` and complete it first." |
| 24 | |
| 25 | **2. Messaging guide complete?** |
| 26 | |
| 27 | Read `company-context/messaging.md` and `methodology/foundation/messaging-guide.md`. |
| 28 | |
| 29 | Required: |
| 30 | Problem statement in the buyer's words (not category descriptions) |
| 31 | Mechanism (why this problem exists or has gotten worse now) |
| 32 | At least one specific proof point with company type, result, and timeframe |
| 33 | |
| 34 | If missing: "The messaging guide defines the language the content must use. Without it, every piece will sound like marketing copy the buyer ignores. Complete `methodology/foundation/messaging-guide.md` first." |
| 35 | |
| 36 | **3. Platform and time commitment** |
| 37 | |
| 38 | Ask the user: |
| 39 | What platform do they primarily publish on? (LinkedIn, website, newsletter, X?) |
| 40 | How much time per week can they dedicate to content? (30 min / 1 hour / 2+ hours) |
| 41 | |
| 42 | This determines calendar density and format mix. Do not generate a calendar without knowing the platform. |
| 43 | |
| 44 | **4. Your archetype** |
| 45 | |
| 46 | Before writing content, confirm the business type. Route to the correct segment file. |
| 47 | |
| 48 | | Your type | Read this first | |
| 49 | |-----------|----------------| |
| 50 | | B2B SaaS, devtools, marketplace | `playbooks/segments/startup-archetypes/` | |
| 51 | | Agency, consulting, IT/MSP, advisory | `playbooks/segments/service-firms/` | |
| 52 | | Residential or commercial services | `playbooks/segments/trade-businesses/` | |
| 53 | |
| 54 | The archetype determines which GOD Engine bricks matter most and what the G2 Warm motion looks like for your category. |
| 55 | |
| 56 | |
| 57 | |
| 58 | ## DO |
| 59 | |
| 60 | Run these four steps in order. Do not skip a step unless the user confirms it is already done. |
| 61 | |
| 62 | ### Step 1: Define core theme |
| 63 | |
| 64 | Help them define their theme as a one-sentence statement: |
| 65 | |
| 66 | > "I write about [specific intersection of ICP problem + your unique perspective]." |
| 67 | |
| 68 | Push back if the theme is too broad. Use these as failure examples: |
| 69 | "AI and marketing" -- not a theme |
| 70 | "Business growth tips" -- not a theme |
| 71 | "Why B2B service firms under 20 people should treat content as a sales warmer, not a brand play" -- this is a theme |
| 72 | |
| 73 | The theme must: |
| 74 | Be specific enough that their ICP recognizes themselves in it |
| 75 | Have a point of view that goes beyond category average |
| 76 | Be something they have evidence for (data, client results, direct experience) |
| 77 | |
| 78 | If they cannot produce a theme that passes these three tests, do not move to Step 2. The calendar will be useless without it. |
| 79 | |
| 80 | ### Step 2: Build a 30-day calendar |
| 81 | |
| 82 | Generate 30 days of specific content ideas scaled to their time commitment: |
| 83 | |
| 84 | | Time per week | Mix | |
| 85 | |---------------|-----| |
| 86 | | 30 min | 8-10 short posts (under 150 words) | |
| 87 | | 1 hour | 4-6 LinkedIn posts + 4-6 short hooks | |
| 88 | | 2+ hours | 2 long-form + 6-8 LinkedIn posts + 6-8 short hooks | |
| 89 | |
| 90 | For each calendar item, define: |
| 91 | Specific topic (not "content marketing tips" -- something concrete and named) |
| 92 | Core insight (one sentence -- what is the non-obvious thing?) |
| 93 | Connection to ICP's situation (why does this matter to them right now?) |
| 94 | Format (long-form / LinkedIn post / short hook) |
| 95 | |
| 96 | ### Step 3: Write |
| 97 | |
| 98 | **For long-form content:** Use `playbooks/warm/content/long-form/templates/article.md` |
| 99 | |
| 100 | **For short-form content:** Use `playbooks/warm/content/short-form/templates/linkedin-post.md` |
| 101 | |
| 102 | Apply these rules to every piece: |
| 103 | First line must earn the scroll -- do not warm up, do not start with "I want to talk about" |
| 104 | Problem-first framing -- ICP's situation before your solution |
| 105 | Use buyer verbatims from the messaging guide -- their language, not yours |
| 106 | No em dashes |
| 107 | Short paragraphs (3-4 sentences max) |
| 108 | One CTA per piece |
| 109 | No category claims ("AI-powered," "data-driven," "full-service") |
| 110 | |
| 111 | ### Step 4: Distribute |
| 112 | |
| 113 | Remind them: publishing is not distribution. |
| 114 | |
| 115 | Distribution plan for every piece published: |
| 116 | Post natively on primary platform |
| 117 | Send to email list (even if under 100 subscribers) |
| 118 | Share in 1-2 relevant communities where ICP is active |
| 119 | Repurpose each long-form piece into 3-5 short-form posts |
| 120 | Reference in cold outreach as proof of expertise and point of view |
| 121 | |
| 122 | |
| 123 | |
| 124 | ## VERIFY |
| 125 | |
| 126 | Before this session ends: |
| 127 | |
| 128 | **1. Theme passes the specificity test?** |
| 129 | |
| 130 | Read the theme out loud. Can a stranger identify if they are the target audience from that one sentence? If not, rewrite. |
| 131 | |
| 132 | **2. 30-day calendar exists?** |
| 133 | |
| 134 | Confirm there are at least 10 specific, named topics -- not category titles but real arguments and angles. |
| 135 | |
| 136 | **3. First piece written?** |
| 137 | |
| 138 | Do not leave the session with only a calendar. Write at least the first piece before closing. Momentum beats planning. |
| 139 | |
| 140 | **4. Distribution plan set?** |
| 141 | |
| 142 | Confirm they know exactly what happens the day they publish. Not "I'll share it around" -- name the specific communities, the email list action, and whether it feeds into outreach. |
| 143 | |
| 144 | **5. Metrics baseline set?** |
| 145 | |
| 146 | State the starting numbers: "Before this content cycle, our profile visits from content are [X]. Success this month = at least [Y] inbound inquiries sourced from content." |
| 147 | |
| 148 | Monthly metrics to track: |
| 149 | Impressions per post |
| 150 | Comments per post |
| 151 | Profile visits from content |
| 152 | Inbound inquiries sourced from content |
| 153 | |
| 154 | |
| 155 | |
| 156 | ## Reference files |
| 157 | |
| 158 | Full playbook: `playbooks/warm/content/README.md` |
| 159 | Long-form guide: `playbooks/warm/content/long-form/README.md` |
| 160 | Short-form guide: `playbooks/warm/content/short-form/README.md` |
| 161 | Article template: `playbooks/warm/content/long-form/templates/article.md` |
| 162 | LinkedIn post template: `playbooks/warm/content/short-form/templates/linkedin-post.md` |
| 163 | Messaging guide: `methodology/foundation/messaging-guide.md` |
| 164 |
Details
- Updated
- May 15, 2026
- License
- MIT
- Stars on the repo
- ★ 64
- Checked
- Source
- markster/markster-os ↗
- Creator
- markster · 7 listings
Similar skills
See all →
SkillAnalyze active ads from Meta/Facebook, GoogleAd library teardown
SkillTurn product materials into listing visuals for Taobao, JDEcommerce visual copywriting
SkillTell us about your plans and pricesPricing Page (High‑Conversion) — Web Design Skill
SkillWrites opening hooks and post titles for long-form articlesCopywriting hooks
SkillSomeone wants landing page ideas, conceptsEcom landing pages
SkillWrite sales pages, email sequencesEW Skill — Sales CopyMore from markster
SkillRun the Markster OS cold email playbookCold Email Operator
SkillRun the Markster OS events playbookEvents Operator
SkillRun the Markster OS fundraising playbookFundraising Operator
SkillDiagnostic operator for Markster OSMarkster OS Operator
SkillRun structured B2B research prompts from the Markster OSResearch Operator
SkillRun the Markster OS sales playbookSales Operator