New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Run the Markster OS content playbook

Content Operator

by markster · MIT license · ★ 64 on GitHub · updated May 15

Content Operator cover

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)
Claude Codenpx skills add markster/markster-os --skill content -g -a claude-code
Claude Code (manual)mkdir -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/content
Windows (PowerShell)New-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" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md6.0 KB
Read the files here
markster/b1da5001 file
Shared references2SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
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:

  1. Post natively on primary platform
  2. Send to email list (even if under 100 subscribers)
  3. Share in 1-2 relevant communities where ICP is active
  4. Repurpose each long-form piece into 3-5 short-form posts
  5. 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---
2name: content
3description: '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 
12Do not proceed past any failed check.
13 
14**1. F1 complete?**
15 
16Read `company-context/audience.md`.
17 
18Required before this skill runs:
19- ICP defined with company type and specific pain
20- Decision-maker title named
21- Buying trigger identified
22 
23If 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 
27Read `company-context/messaging.md` and `methodology/foundation/messaging-guide.md`.
28 
29Required:
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 
34If 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 
38Ask 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 
42This determines calendar density and format mix. Do not generate a calendar without knowing the platform.
43 
44**4. Your archetype**
45 
46Before 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 
54The 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 
60Run 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 
64Help them define their theme as a one-sentence statement:
65 
66> "I write about [specific intersection of ICP problem + your unique perspective]."
67 
68Push 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 
73The 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 
78If 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 
82Generate 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 
90For 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 
102Apply 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 
113Remind them: publishing is not distribution.
114 
115Distribution plan for every piece published:
1161. Post natively on primary platform
1172. Send to email list (even if under 100 subscribers)
1183. Share in 1-2 relevant communities where ICP is active
1194. Repurpose each long-form piece into 3-5 short-form posts
1205. Reference in cold outreach as proof of expertise and point of view
121 
122---
123 
124## VERIFY
125 
126Before this session ends:
127 
128**1. Theme passes the specificity test?**
129 
130Read 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 
134Confirm there are at least 10 specific, named topics -- not category titles but real arguments and angles.
135 
136**3. First piece written?**
137 
138Do 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 
142Confirm 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 
146State 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 
148Monthly 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 
View all files on GitHub →

Details

Updated
May 15, 2026
License
MIT
Stars on the repo
★ 64
Checked
Source
markster/markster-os ↗
Creator
markster · 7 listings
View creator

Similar skills

See all →
SkillAnalyze active ads from Meta/Facebook, GoogleAd library teardownScrapeCreators/social-media-research-skills · by ScrapeCreatorsUse when the user wants to analyze active ads from Meta/Facebook, Google, or LinkedIn ad libraries; tear down a competitor's messaging; extract hooks, offers, CTAs, video transcripts, landing page claims, and test ideas from public ads.★ 2.6k GitHub starsSkillTurn product materials into listing visuals for Taobao, JDEcommerce visual copywritingfeichanggege/ecommerce-visual-copywriting-skill · by feichanggegeTurn product materials into listing visuals for Taobao, JD, Douyin, Amazon, Shopify and TikTok Shop: main-image and detail-page storyboards, in-image copy, image prompts, plus an evidence and ad-compliance check.★ 985 GitHub starsSkillTell us about your plans and pricesPricing Page (High‑Conversion) — Web Design Skillboraoztunc/skills · by Meng ToTell us about your plans and prices, and get back a ready-to-build pricing page: plan layout, what each tier includes, buttons, and answers to common buyer questions.★ 361 GitHub starsSkillWrites opening hooks and post titles for long-form articlesCopywriting hookssamber/cc-skills · by samberWrites opening hooks and post titles for long-form articles in EN or FR — blog posts, Substack/Medium/dev.to, LinkedIn long-form, newsletters, essays. Trigger whenever the user asks for a hook, opening, lede, intro, first sentence/paragraph, opener, accroche, attaque, phrase d'accroche, or première phrase — including punching up a flat intro or draft opening — or for a post title, titre d'article, or headline. Do NOT trigger for social posts (LinkedIn feed, Twitter/X, TikTok, Bluesky), READMEs, taglines, email subjects, ad copy, landing-page headlines, press releases, SEO meta, or body rewrites. Do NOT use for end-of-article CTAs — use samber/cc-skills@copywriting-cta instead.★ 222 GitHub starsSkillSomeone wants landing page ideas, conceptsEcom landing pageskgelster/awesome-ecom-skills · by kgelsterUse when someone wants landing page ideas, concepts, or angles for a store: give me landing page concepts", "LP ideas", "landing page angles", a campaign or ad landing page, pages for a new audience/segment, a seasonal/event/promo page, or a geo/local page. Also use when a chosen concept gets picked and needs building out into an actual page (section-by-section blueprint), or when auditing an existing landing page against best practice. The core insight: one product becomes dozens of pages by varying the ANGLE, not the product. Not for full-site information architecture, product detail pages, collection pages, or blog/SEO content (a landing page has ONE goal, no site chrome). Use an SEO/content skill. Not for the ad or email creative itself, though message match with the page matters.★ 49 GitHub starsSkillWrite sales pages, email sequencesEW Skill — Sales CopyDeupaxx/EveryDay-Writer · by DeupaxxWrite sales pages, email sequences, and direct-response copy that converts through clarity and specificity rather than manipulation. Use for launches, offers, and conversion-focused email. Enforces the EW anti-AI rules, proof standards, and the writer's voice profile.★ 32 GitHub stars

More from markster

SkillRun the Markster OS cold email playbookCold Email Operatormarkster/markster-os · by marksterRun the Markster OS cold email playbook. CHECK prerequisites, DO the sequence build, VERIFY before sending. Routes through ScaleOS G3 Book with context from F1/F2.★ 64 GitHub starsSkillRun the Markster OS events playbookEvents Operatormarkster/markster-os · by marksterRun the Markster OS events playbook. CHECK prerequisites (ICP, offer, specific event), DO pre-event targeting + during-event conversation system + post-event follow-up, VERIFY before leaving the event pipeline empty. Routes through ScaleOS G2 Warm.★ 64 GitHub starsSkillRun the Markster OS fundraising playbookFundraising Operatormarkster/markster-os · by marksterRun the Markster OS fundraising playbook. CHECK stage, traction, and funding path before building anything. DO investor ICP + list + outreach + pitch + close. VERIFY investor pipeline is real before claiming readiness. Routes through ScaleOS Biz Dev.★ 64 GitHub starsSkillDiagnostic operator for Markster OSMarkster OS Operatormarkster/markster-os · by marksterDiagnostic operator for Markster OS. Identifies the constraint brick, runs the Hormozi diagnostic, and routes to the right playbook with context pre-filled. Run this before any other skill.★ 64 GitHub starsSkillRun structured B2B research prompts from the Markster OSResearch Operatormarkster/markster-os · by marksterRun structured B2B research prompts from the Markster OS library. CHECK what they are trying to learn and ICP context. DO one or more of 9 prompts (competitive intelligence, buyer JTBD, buying signals, pricing perception, GTM channels, objection research, market positioning, mental category positioning, first 60 seconds). VERIFY output is documented back into Foundation.★ 64 GitHub starsSkillRun the Markster OS sales playbookSales Operatormarkster/markster-os · by marksterRun the Markster OS sales playbook. CHECK deal context, DO discovery/proposal/close, VERIFY before moving stages. Includes 9 Kill Skills audit for conversion problems.★ 64 GitHub stars