Marketing Os
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
April Dunford's 10-step positioning methodology for B2B tech products.
$ npx skills add getagentseal/founder-playbook --skill obviously-awesome -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install getagentseal/founder-playbook obviously-awesome --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/obviously-awesome .claude/skills/obviously-awesome && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "obviously-awesome" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesome into .claude/skills/obviously-awesome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obviously-awesome", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesomeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add getagentseal/founder-playbook --skill obviously-awesome -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install getagentseal/founder-playbook obviously-awesome --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/obviously-awesome .agents/skills/obviously-awesome && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "obviously-awesome" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesome into .agents/skills/obviously-awesome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obviously-awesome", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill obviously-awesome -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install getagentseal/founder-playbook obviously-awesome --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/obviously-awesome .cursor/skills/obviously-awesome && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "obviously-awesome" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesome into .cursor/skills/obviously-awesome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obviously-awesome", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/getagentseal/founder-playbook.git --path skills/obviously-awesome--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add getagentseal/founder-playbook --skill obviously-awesome -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install getagentseal/founder-playbook obviously-awesome --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/obviously-awesome .gemini/skills/obviously-awesome && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "obviously-awesome" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesome into .gemini/skills/obviously-awesome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obviously-awesome", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install getagentseal/founder-playbook obviously-awesomeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add getagentseal/founder-playbook --skill obviously-awesome -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/obviously-awesome .github/skills/obviously-awesome && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "obviously-awesome" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesome into .github/skills/obviously-awesome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obviously-awesome", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add getagentseal/founder-playbook --skill obviously-awesome -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install getagentseal/founder-playbook obviously-awesome --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/getagentseal/founder-playbook.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/obviously-awesome .opencode/skills/obviously-awesome && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "obviously-awesome" agent skill from https://github.com/getagentseal/founder-playbook/tree/main/skills/obviously-awesome into .opencode/skills/obviously-awesome/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "obviously-awesome", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
obviously-awesomeApril Dunford's 10-step positioning methodology for B2B tech products.
Obviously Awesome is an agent skill from getagentseal/founder-playbook. April Dunford's 10-step positioning methodology for B2B tech products. Use when customers don't understand the product, sales cycles are long because reps must "explain it," prospects compare you to wrong competitors, or you face price pressure despite a good product. Covers competitive alternatives, unique attributes, value themes, target market characteristics, market category (Head to Head / Big Fish Small Pond / New Game), and trend layering.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `cases.md`, `examples.md` and `frameworks.md`).
It sits in Marketing & SEO, covering Positioning and messaging. The repository describes itself as: 15 proven business books distilled into AI-native skills. Works with Claude Code, ChatGPT, Gemini, Cursor. The licence is MIT.
Read from SKILL.md and the folder at commit e811e63. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Obviously Awesome loads about 3.6k tokens when it runs. Until then it costs about 117 tokens; SKILL.md has 1,663 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from getagentseal/founder-playbook at commit e811e63, republished under its MIT licence (© getagentseal). 1,663 words, ~3,606 tokens.
.claude/skills/obviously-awesome/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Note: This skill is independent analysis and commentary, not a reproduction of the original text. It synthesizes the book's core ideas with modern startup practice, surfaces where frameworks are outdated or incomplete, and integrates perspectives from adjacent disciplines. For the full argument and context, read the original book.
"Positioning is the act of deliberately defining how you are the best at something that a defined market cares a lot about." - April Dunford (2019)
Investigate positioning when ANY of these is true:
| Sign | What It Looks Like |
|---|---|
| Confused prospects | Compare you to products you're nothing like |
| Long sales cycles | Reps spend most calls explaining what you are |
| High churn | Customers who buy don't get the expected value |
| Price pressure | Can't command premium despite real differentiation |
Dunford does not give a strict numerical threshold - one strong sign is enough to warrant a positioning audit.
You probably have a positioning problem, not a marketing problem.
When prospects don't understand your product, it's not because you haven't said it loud enough. It's because the CONTEXT they're using to evaluate you is wrong.
Joshua Bell experiment: World-class violinist played 45 min in a DC subway in 2007. 1,070 people walked past. Earned $32.17. Two days earlier: sold-out Boston Symphony Hall at $100/seat. Same person, same skill. Different context = different perceived value.
Cake → Muffin: Sometimes the same product needs a different category. Almost no physical difference between cake and muffin. Big contextual difference.
Positioning is built from 5 components, plus 1 optional layer:
| Component | Question | Example |
|---|---|---|
| 1. Competitive Alternatives | What would they use without you? | Excel, hire intern, do nothing |
| 2. Unique Attributes | What do you have that alternatives don't? | Features, capabilities, partnerships |
| 3. Value | What can they DO because of those attributes? | Save time, increase revenue (with proof) |
| 4. Target Market Characteristics | Who cares MOST? | Best-fit customer profile |
| 5. Market Category | What context makes your value obvious? | "CRM for X" |
| +1. Relevant Trends | What in the world makes you matter MORE NOW? | AI, remote work |
Critical: Dependency chain. Get the order wrong and the whole thing collapses.
Alternatives → Attributes → Value → Target Market → Category → (Trends)Why traditional "For X who Y, our product is a Z that does W unlike V" template fails: assumes you already know category and competitors. For novel products, those are exactly what you're trying to figure out.
Detailed component definitions: see frameworks.md.
| # | Step |
|---|---|
| 1 | Understand customers who LOVE the product (best-fit) |
| 2 | Form cross-functional positioning team (CEO mandatory) |
| 3 | Align vocabulary, let go of positioning baggage |
| 4 | List true competitive alternatives (customer view) |
| 5 | Isolate unique attributes (with proof) |
| 6 | Map attributes to value themes (1-4 themes) |
| 7 | Determine who cares a lot (behavioral segmentation) |
| 8 | Find market frame of reference (the core step) |
| 9 | Layer on a trend (optional) |
| 10 | Capture positioning so it can be shared |
Step-by-step detail with team formation, baggage handling, value-theme clustering, segmentation: see frameworks.md.
You can't position for your target market until you know who loves you. You can't know who loves you without selling first. You can't sell without some positioning.
Break the cycle: Cast wide early ("fishing-net analogy"). Don't position narrowly until you have signal from real users. Then narrow to best-fit.
If you don't have happy customers yet → you don't have positioning yet, you have hypotheses. Use Mom Test for problem validation FIRST. Don't position what you haven't built.
Market category is the context customers use to evaluate you. Three styles:
Compete in an existing category by being better at one specific dimension.
When to use: Established category exists, you have a clear advantage on something customers care about, you can be top-3. When NOT: Category leader is too entrenched, your advantage isn't category-level important.
Find a subsegment where YOUR strengths are most valuable.
When to use: A subset of customers has needs the leader doesn't address well, your strengths align, the subsegment is big enough.
This is often the best fit for startups - you can't out-spend the leader on the broad category, but you can dominate a slice.
Example: Janna Systems failing at "CRM for everyone." Repositioned as "CRM for investment banks": $2M → $70M revenue → $1.7B Siebel acquisition.
Define a new category you can lead.
When to use: Existing categories don't fit, you can clearly explain the new category in customer terms, you have resources to educate the market (expensive). When NOT (most cases): You think your product is "unique" (everyone thinks that), no budget to educate, existing categories work "well enough."
Example: Eloqua coined "marketing automation": $12M → $96M → $870M Oracle acquisition.
Mark Organ (Eloqua founder) found that successful category creation comes from deeply understanding a narrow set of extreme early customers, not from executives brainstorming acronyms at offsites. The category emerges from observed behavior, not invented positioning.
When both a new market boundary AND new evaluation criteria are needed, consider creating a new category. With only one needed, stay within existing category structure. Treat as a heuristic.
Does an existing category fit?
├─ YES → Are you the leader or can become one?
│ ├─ YES → HEAD TO HEAD
│ └─ NO → Is there a subsegment where you'd be leader?
│ ├─ YES → BIG FISH, SMALL POND ← often the answer
│ └─ NO → Reconsider product, or move to Style 3
└─ NO → Can you afford to educate the market?
├─ YES → CREATE NEW GAME (rare and risky)
└─ NO → Force-fit Style 1 or 2Dunford's hypothetical: take Coke and reposition for the pet-treat subsegment ("tastes like bones"). Different competitors, different value, different category - same product. Sometimes a subsegment IS available; you just have to look creatively.
Wattpad case (often omitted): repositioned a writing-platform product after finding a subset of users using it differently. See cases.md.
Are any of these true?
├─ Confused prospects (compare you to wrong things)
├─ Long sales cycles (always explaining)
├─ High churn (buyers don't get expected value)
├─ Price pressure (can't command premium)
└─ If multiple signs apply → likely positioning problemMajor trigger occurred?
├─ New competitor changes landscape
├─ Regulations change
├─ Economic climate shift
├─ New technology disrupts category
├─ Customer attitude shifts
└─ YES to any → Run the 4 weak-positioning signs check
├─ Multiple failing → Start at Step 4 (re-check alternatives)
└─ All clear → Stay courseDunford recommends "checking in" on positioning every six months OR when there's a major event - not mandatory periodic repositioning. Reposition when triggers occur, not on schedule. Adding a large competitor doesn't necessarily mean positioning should change.
Once positioning is locked, build a sales story in 6 stages:
| # | Stage | Content |
|---|---|---|
| 1 | The Problem | Pain customers feel |
| 2 | Current Solutions / Gap | Why alternatives fail |
| 3 | Perfect World | What it would look like solved |
| 4 | Product Introduction | Here's how we solve it |
| 5 | Value Themes | The 1-4 ways we deliver value |
| 6 | Next Steps | What to do now |
Sales story comes BEFORE messaging. Story drives messaging, not vice versa. Then write a master messaging document to prevent message creep.
Customers vs investors warning: Don't say "disruption" to customers. Investor language alienates buyers. Save category-creation language for fundraising.
These three terms are used interchangeably and shouldn't be.
Key Dunford point: Most teams skip positioning and jump straight to messaging. The messaging then changes weekly because there's no foundation underneath it - every new opinion reshapes the copy. Fix the positioning first; the messaging becomes obvious.
| Layer | What It Is | Who Owns It | How Often It Changes |
|---|---|---|---|
| Positioning | Internal strategic foundation | CEO + cross-functional team | Rarely (major triggers only) |
| Messaging | Customer-facing language | Marketing | Quarterly or as tests demand |
| Branding | Emotional associations | Marketing + Design (long game) | Slowly, over years |
| Number | Rule |
|---|---|
| 5+1 | Components of positioning |
| 10 | Steps in the process |
| 3 | Positioning styles |
| 3-12 | Team size for workshop |
| 1-2 | Members per function on positioning team |
| 1-4 | Value themes |
| 2-5 | Clusters of competitive alternatives |
| 6 months | Frequency to check in (not mandatory reposition) |
| 30 sec | Time customer should need to "get it" |
Pre-product, validating problem? → Mom Test instead. Don't position what you haven't built.
Pure consumer (TikTok-style)? → Brand and content matter more than positioning
Commodity goods? → Price is the only differentiator
Internal tools? → No customer-facing positioning needed
Genuine 10x product / strong network effects / PLG with self-explaining UX? → Positioning matters but doesn't WIN the gameModern counter-examples to "positioning is foundational":
| Company | What Won (Positioning Was Secondary) |
|---|---|
| TikTok | Algorithm + content distribution |
| Stripe | Developer experience + API quality |
| OpenAI / ChatGPT | Product capability shock |
| Linear | Product craft + design |
| Cursor | Better-than-Copilot AI; word-of-mouth |
| Figma | Browser-based collab + free tier; network effects |
Pattern: When product is genuinely 10x better, OR strong network effects, OR product-led, positioning matters but doesn't win.
"Context is everything. Without context, no one can know if your product is good, bad, or even relevant to them."
Positioning isn't marketing, branding, or messaging. It's choosing the context customers use to evaluate you.
The frame determines: who shows up as a customer, who shows up as a competitor, what "value" means, what "expensive" means, what "good" means.
Most companies let positioning happen accidentally. Dunford's contribution: positioning is a deliberate choice, not a default.
© getagentseal, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files in skills/obviously-awesome of getagentseal/founder-playbook.
Open the folder on GitHubat commit e811e63
Obviously Awesome next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Obviously Awesome this skillgetagentseal/founder-playbook | 729 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Marketing OsYuzzyuk/marketing-os | 538 | — | ~2.5k | Automated safety check: Pass | MIT | |
| Revenue Centric Designheliocosta-dev/revenue-centric-design | 740 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Startup Positioningferdinandobons/startup-skill | 1.2k | — | ~4.6k | Automated safety check: Pass | MIT | |
| Stanley Druckenmiller Investmenttradermonty/claude-trading-skills | 3k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| B2b Playbookweilun88313/B2B-Playbook | 203 | — | ~3.1k | Automated safety check: Pass | Proprietary |
Yuzzyuk/marketing-os
A complete marketing department in one skill. An agent skill from Yuzzyuk/marketing-os.
heliocosta-dev/revenue-centric-design
Playbook for designing SaaS and startup products that convert, retain, and monetize — landing pages & CRO, checkout & forms, onboarding/activation, churn reduction, pricing psychology, dashboards…
ferdinandobons/startup-skill
Market positioning strategy using the April Dunford framework, enriched with JTBD discovery, Moore positioning statement, and Neumeier's Onliness Test.
tradermonty/claude-trading-skills
Druckenmiller Strategy Synthesizer - Integrates 8 upstream skill outputs (Market Breadth, Uptrend Analysis, Market Top, Macro Regime, FTD Detector, VCP Screener, Theme Detector, CANSLIM Screener)…
weilun88313/B2B-Playbook
Turn B2B marketing work into evidence-aware outputs using market, positioning, demand, account-program, lifecycle, and tool-selection guidance.
onvoyage-ai/gtm-engineer-skills
Researches a company from its URL and produces a Brand DNA file covering positioning, audience, competitors, voice, and messaging.
getagentseal/founder-playbook
Builds lead generation systems using Alex Hormozi's Core Four framework (warm outreach, content, cold outreach, paid ads), lead magnets, and Rule of 100.
getagentseal/founder-playbook
Designs irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns.
getagentseal/founder-playbook
Frameworks from Kim & Mauborgne for creating uncontested market space and making competition irrelevant.
getagentseal/founder-playbook
Startup diagnostic router. An agent skill from getagentseal/founder-playbook.
getagentseal/founder-playbook
Cialdini's seven principles of compliance (the classic six — reciprocation, commitment-consistency, social proof, liking, authority, scarcity — plus Unity, added 2016) and Pre-Suasion.
getagentseal/founder-playbook
Applies Eric Ries's Lean Startup methodology for building products under extreme uncertainty.
Categories
April Dunford's 10-step positioning methodology for B2B tech products. Obviously Awesome is an agent skill from getagentseal/founder-playbook. April Dunford's 10-step positioning methodology for B2B tech products.
Obviously Awesome fits situations like: customers dont understand the product; sales cycles are long because reps must explain it; prospects compare you to wrong competitors; you face price pressure despite a good product.
Run `npx skills add getagentseal/founder-playbook --skill obviously-awesome -a claude-code`. Or copy the skill folder (skills/obviously-awesome in getagentseal/founder-playbook) into .claude/skills/obviously-awesome in your project. Claude Code loads it when a task matches its description.
Run `npx skills add getagentseal/founder-playbook --skill obviously-awesome -a codex`. Or copy the skill folder (skills/obviously-awesome in getagentseal/founder-playbook) into .agents/skills/obviously-awesome in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add getagentseal/founder-playbook --skill obviously-awesome -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/obviously-awesome, .gemini/skills/obviously-awesome, .github/skills/obviously-awesome and .opencode/skills/obviously-awesome in your project.
SKILL.md names no scripts, command-line tools or credentials: Obviously Awesome is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Obviously Awesome is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Obviously Awesome: Marketing Os (Yuzzyuk/marketing-os, 538 stars), Revenue Centric Design (heliocosta-dev/revenue-centric-design, 740 stars), Startup Positioning (ferdinandobons/startup-skill, 1.2k stars) and Stanley Druckenmiller Investment (tradermonty/claude-trading-skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
getagentseal (a GitHub organization) maintains it in getagentseal/founder-playbook, which has 729 GitHub stars. The repository holds 16 skills in this directory. The repository was last updated on October 6, 2026.
Source: getagentseal/founder-playbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.