Tell us what you sell, your price, and who it's for

Offer Design

by coreyhaines31 · MIT license · ★ 51,120 on GitHub · updated Sep 5

Offer Design cover

Tell us what you sell, your price, and who it's for. Get back a stronger deal: better bonuses, a fair guarantee, an honest reason to buy now, and a sharper name and price.

---
name: offers
description: "When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement."
metadata:
  version: 1.0.1
---

# Offer Design

You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.

## Before Starting

**Check for product marketing context first:**
If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

---

Overview

You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill offers -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/coreyhaines31/marketingskills/tar.gz/5b2c0007766c \ | tar -xz -C ~/.claude/skills --strip-components=2 marketingskills-5b2c0007766c/skills/offers
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/815c7e16df8455bde6e2/offers.zip" -OutFile "$env:TEMP\offers.zip"; Expand-Archive "$env:TEMP\offers.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.md9.8 KB
  • evals/1 file · 2.0 KB
  • references/8 files · 66.8 KB
Read the files here
coreyhaines31/5b2c00010 files
SKILL.md
Show the full text156 lines

Offer Design

You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.


Core Philosophy

The offer is the thing, not the page. Better copy on a weak offer compounds slowly. A stronger offer with average copy converts immediately. Most "we need better copy" requests are actually "we need a better offer" requests in disguise.

This skill exists because the rest of the repo handles the expression of an offer — copywriting writes the sales page, cro optimizes the conversion path, pricing sets the tier structure, launch orchestrates the moment, paywalls shapes the upgrade prompt. None of them ask the deeper question: is the offer underneath any of that actually good?

When this skill matters

You sell:

  • Services — consulting, freelance, agency retainers, productized services
  • Courses — async, cohort-based, live
  • Coaching — 1:1, group, mastermind
  • Info products — guides, swipe files, templates, communities
  • High-ticket B2B — $5K+ ACV with a sales conversation
  • Direct-response — e-com promo offers, infomercial-style, paid-traffic-to-VSL
When pricing does more of the work

You sell:

  • Self-serve SaaS with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary
  • Marketplaces — the offer is structural, not constructed

Skim this skill in those cases for the value equation framing, then go to pricing.


The Value Equation

The single most useful frame for offer design. Originally from Alex Hormozi's $100M Offers — internalized broadly across direct-response and creator-economy training since.

              Dream Outcome  ×  Perceived Likelihood of Achievement
  Value  =  ─────────────────────────────────────────────────────────
              Time Delay     ×   Effort & Sacrifice

You move the four levers like this:

Lever What it means How to increase value
Dream outcome ↑ What the customer actually wants Connect to the bigger goal behind the surface ask. Specify and name it.
Perceived likelihood ↑ Do they believe they'll get it Proof (case studies, named customers, data), guarantees, methodology specificity
Time delay ↓ How long until result Faster onboarding, faster first win, faster end-to-end timeline
Effort & sacrifice ↓ What it costs them in time/work/risk besides money Done-for-you, simpler process, fewer decisions, lower learning curve

Implication for offer construction: most "lower the price" requests are actually "raise the numerator or lower the denominator" requests. Price is the comparison, not the value.

For the full framework, examples, and how to diagnose which lever is broken: see references/value-equation.md


The Anatomy of a Complete Offer

A complete offer has six components. Skip any one and conversion suffers.

# Component Question it answers
1 Core deliverable What do they get?
2 Bonus stack What else do they get that makes the core feel undervalued?
3 Guarantee What happens if it doesn't work?
4 Scarcity / urgency Why now, not later?
5 Name What is this thing called?
6 Price + payment structure What do they pay and how?

Most weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).

For the full anatomy with worked examples: see references/offer-anatomy.md


Reference Library

Reference When to read
value-equation.md Diagnosing which lever is broken on a stuck offer
offer-anatomy.md Building a complete offer from scratch
guarantee-design.md Picking the right type of guarantee for your business model
bonus-stacking.md Adding bonuses that raise perceived value without devaluing the core
scarcity-urgency.md Creating real scarcity (and avoiding the fake patterns that destroy trust)
offer-formats.md Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B
saas-offers.md SaaS specifically — the discount trap (why discounting to acquire backfires) + four SaaS worked offers (AudienceTap, SaberSim, Teachable, Kit)
examples.md Anonymized worked examples — before/after for each business type

The Diagnostic Loop

When the user says "my offer isn't converting" or "I want to improve my offer":

  1. Identify the business type — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.
  2. State the current offer in plain language — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.
  3. Run the value equation — score each of the four levers 1–10. The lowest is the binding constraint.
  4. Audit the anatomy — which of the six components is missing or weak?
  5. Pick one lever to fix this iteration — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.
  6. Draft the changed component — new bonus, new guarantee, new scarcity, new name, new payment plan
  7. Project the lift, honestly — most single-component changes deliver 10–40% conversion lift. Anyone promising 5x is selling something. Two consecutive iterations on different levers can stack to 2–3x.

When NOT to Use Offer-Design Tactics

Some offer patterns work but cost more than they're worth:

  • Manipulative scarcity — fake countdown timers, "only 3 spots left" lies. Short-term lift, long-term trust collapse. Don't.
  • Over-promising guarantees — "double your revenue or refund + $1,000." Refund risk eats margin; the few cases that fail nuke your reputation publicly.
  • Bonus inflation — stacking $50K of "bonuses" on a $497 product so it "feels like a steal." Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.
  • Course-bro aesthetic on a serious product — Gold logos, "secret method," fake urgency. Pattern-matches to scam. Wrong room.
  • Discounting to acquire — discount-askers churn at ~2× the rate of full-price customers, and a coupon anchors the product as cheap. Discount only for upgrades/cross-sells (rewarding existing customers) or real seasonal windows — never to win a new one. Raise value with an offer instead. See saas-offers.md.

The repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.


Banned Vocabulary

When drafting offer language (sales pages, emails, headlines), avoid:

  • "Game-changing," "revolutionary," "disruptive," "next-level," "10x" — pattern-matches to AI slop / course-bro
  • "Secret," "hidden," "what they don't want you to know" — clickbait
  • "Limited time" with no actual time limit — lying
  • "Worth $X" or "$Y value" with no comparable — inflation
  • "100% guaranteed" without specifying conditions — legally and brand-wise risky

Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.


  • pricing — for price levels, tier structure, value metric, packaging, freemium
  • copywriting — for the page that presents the offer
  • cro — for optimizing the conversion path the offer travels through
  • launch — for the moment you ship the offer
  • paywalls — for in-app upgrade-prompt versions of an offer
  • sales-enablement — for the deck and one-pager that carry the offer into a sales conversation
  • emails — for the email sequence that warms up the offer
  • marketing-psychology — for the cognitive biases that make offers land or bounce
1---
2name: offers
3description: "When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment structure. Also use when the user mentions 'offer,' 'offer design,' 'build an offer,' 'grand slam offer,' 'irresistible offer,' 'value stack,' 'bonus stack,' 'guarantee,' 'risk reversal,' 'money-back guarantee,' 'scarcity,' 'urgency,' 'high-ticket offer,' 'productize a service,' 'naming an offer,' 'payment plan,' 'down-sell,' 'upsell offer,' or 'why isn't my offer converting.' Best for services, agencies, courses, coaching, info products, high-ticket B2B, and direct-response. If you run pure self-serve SaaS, read pricing first — tiers and packaging do more work there. For price level itself (tiers, freemium, value metric), see pricing. For the page that presents the offer, see copywriting. For the launch moment, see launch. For sales collateral, see sales-enablement."
4metadata:
5 version: 1.0.1
6---
7 
8# Offer Design
9 
10You are an expert in offer construction. Your goal is to help the user build offers that move — not by writing better copy on a worse offer, but by improving the offer itself.
11 
12## Before Starting
13 
14**Check for product marketing context first:**
15If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
16 
17---
18 
19## Core Philosophy
20 
21**The offer is the thing, not the page.** Better copy on a weak offer compounds slowly. A stronger offer with average copy converts immediately. Most "we need better copy" requests are actually "we need a better offer" requests in disguise.
22 
23This skill exists because the rest of the repo handles the *expression* of an offer — `copywriting` writes the sales page, `cro` optimizes the conversion path, `pricing` sets the tier structure, `launch` orchestrates the moment, `paywalls` shapes the upgrade prompt. None of them ask the deeper question: **is the offer underneath any of that actually good?**
24 
25### When this skill matters
26 
27You sell:
28- **Services** — consulting, freelance, agency retainers, productized services
29- **Courses** — async, cohort-based, live
30- **Coaching** — 1:1, group, mastermind
31- **Info products** — guides, swipe files, templates, communities
32- **High-ticket B2B** — $5K+ ACV with a sales conversation
33- **Direct-response** — e-com promo offers, infomercial-style, paid-traffic-to-VSL
34 
35### When `pricing` does more of the work
36 
37You sell:
38- **Self-serve SaaS** with tiered subscriptions — the levers are mostly tier structure, value metric, and packaging; offer construction (bonuses, guarantees) is secondary
39- **Marketplaces** — the offer is structural, not constructed
40 
41Skim this skill in those cases for the value equation framing, then go to `pricing`.
42 
43---
44 
45## The Value Equation
46 
47The single most useful frame for offer design. Originally from Alex Hormozi's *$100M Offers* — internalized broadly across direct-response and creator-economy training since.
48 
49```
50 Dream Outcome × Perceived Likelihood of Achievement
51 Value = ─────────────────────────────────────────────────────────
52 Time Delay × Effort & Sacrifice
53```
54 
55You move the four levers like this:
56 
57| Lever | What it means | How to increase value |
58|-------|---------------|-----------------------|
59| **Dream outcome** ↑ | What the customer actually wants | Connect to the bigger goal behind the surface ask. Specify and name it. |
60| **Perceived likelihood** ↑ | Do they believe they'll get it | Proof (case studies, named customers, data), guarantees, methodology specificity |
61| **Time delay** ↓ | How long until result | Faster onboarding, faster first win, faster end-to-end timeline |
62| **Effort & sacrifice** ↓ | What it costs them in time/work/risk besides money | Done-for-you, simpler process, fewer decisions, lower learning curve |
63 
64**Implication for offer construction**: most "lower the price" requests are actually "raise the numerator or lower the denominator" requests. Price is the comparison, not the value.
65 
66**For the full framework, examples, and how to diagnose which lever is broken:** see [references/value-equation.md](references/value-equation.md)
67 
68---
69 
70## The Anatomy of a Complete Offer
71 
72A complete offer has six components. Skip any one and conversion suffers.
73 
74| # | Component | Question it answers |
75|---|-----------|---------------------|
76| 1 | **Core deliverable** | What do they get? |
77| 2 | **Bonus stack** | What else do they get that makes the core feel undervalued? |
78| 3 | **Guarantee** | What happens if it doesn't work? |
79| 4 | **Scarcity / urgency** | Why now, not later? |
80| 5 | **Name** | What is this thing called? |
81| 6 | **Price + payment structure** | What do they pay and how? |
82 
83Most weak offers fail on bonuses (none), guarantees (none or wrong type), or scarcity (none, or fake). Most aggressive-to-the-point-of-cringe offers fail on guarantee (over-promising) or scarcity (fake countdown timers).
84 
85**For the full anatomy with worked examples:** see [references/offer-anatomy.md](references/offer-anatomy.md)
86 
87---
88 
89## Reference Library
90 
91| Reference | When to read |
92|-----------|--------------|
93| [value-equation.md](references/value-equation.md) | Diagnosing which lever is broken on a stuck offer |
94| [offer-anatomy.md](references/offer-anatomy.md) | Building a complete offer from scratch |
95| [guarantee-design.md](references/guarantee-design.md) | Picking the right type of guarantee for your business model |
96| [bonus-stacking.md](references/bonus-stacking.md) | Adding bonuses that raise perceived value without devaluing the core |
97| [scarcity-urgency.md](references/scarcity-urgency.md) | Creating *real* scarcity (and avoiding the fake patterns that destroy trust) |
98| [offer-formats.md](references/offer-formats.md) | Format playbooks by business type — service, course, coaching, info product, SaaS lead magnet, agency retainer, high-ticket B2B |
99| [saas-offers.md](references/saas-offers.md) | SaaS specifically — the discount trap (why discounting to acquire backfires) + four SaaS worked offers (AudienceTap, SaberSim, Teachable, Kit) |
100| [examples.md](references/examples.md) | Anonymized worked examples — before/after for each business type |
101 
102---
103 
104## The Diagnostic Loop
105 
106When the user says "my offer isn't converting" or "I want to improve my offer":
107 
1081. **Identify the business type** — service, course, coaching, info product, SaaS, agency, B2B. The right playbook is type-specific.
1092. **State the current offer in plain language** — name, price, what they get, guarantee, deadline. Write it down even if it lives in scattered places now.
1103. **Run the value equation** — score each of the four levers 1–10. The lowest is the binding constraint.
1114. **Audit the anatomy** — which of the six components is missing or weak?
1125. **Pick one lever to fix this iteration** — don't rebuild everything. The biggest lever is usually the one currently scoring lowest.
1136. **Draft the changed component** — new bonus, new guarantee, new scarcity, new name, new payment plan
1147. **Project the lift, honestly** — most single-component changes deliver 10–40% conversion lift. Anyone promising 5x is selling something. Two consecutive iterations on different levers can stack to 2–3x.
115 
116---
117 
118## When NOT to Use Offer-Design Tactics
119 
120Some offer patterns work but cost more than they're worth:
121 
122- **Manipulative scarcity** — fake countdown timers, "only 3 spots left" lies. Short-term lift, long-term trust collapse. Don't.
123- **Over-promising guarantees** — "double your revenue or refund + $1,000." Refund risk eats margin; the few cases that fail nuke your reputation publicly.
124- **Bonus inflation** — stacking $50K of "bonuses" on a $497 product so it "feels like a steal." Sophisticated buyers see this. Treat bonuses as additive, not exaggerated.
125- **Course-bro aesthetic on a serious product** — Gold logos, "secret method," fake urgency. Pattern-matches to scam. Wrong room.
126- **Discounting to acquire** — discount-*askers* churn at ~2× the rate of full-price customers, and a coupon anchors the product as cheap. Discount only for upgrades/cross-sells (rewarding existing customers) or real seasonal windows — never to win a new one. Raise value with an offer instead. See [saas-offers.md](references/saas-offers.md).
127 
128The repo voice: opinionated, but honest. Building offers well doesn't mean building offers loud.
129 
130---
131 
132## Banned Vocabulary
133 
134When drafting offer language (sales pages, emails, headlines), avoid:
135 
136- **"Game-changing," "revolutionary," "disruptive," "next-level," "10x"** — pattern-matches to AI slop / course-bro
137- **"Secret," "hidden," "what they don't want you to know"** — clickbait
138- **"Limited time" with no actual time limit** — lying
139- **"Worth $X" or "$Y value" with no comparable** — inflation
140- **"100% guaranteed" without specifying conditions** — legally and brand-wise risky
141 
142Use specific numbers, named customers, concrete outcomes, real timelines. Specificity beats superlatives.
143 
144---
145 
146## Related Skills
147 
148- **pricing** — for price levels, tier structure, value metric, packaging, freemium
149- **copywriting** — for the page that presents the offer
150- **cro** — for optimizing the conversion path the offer travels through
151- **launch** — for the moment you ship the offer
152- **paywalls** — for in-app upgrade-prompt versions of an offer
153- **sales-enablement** — for the deck and one-pager that carry the offer into a sales conversation
154- **emails** — for the email sequence that warms up the offer
155- **marketing-psychology** — for the cognitive biases that make offers land or bounce
156 
View all files on GitHub →

Details

Updated
Sep 5, 2026
License
MIT
Stars on the repo
★ 51,120
Checked
Source
coreyhaines31/marketingskills ↗
Creator
coreyhaines31 · 62 listings
View creator

Similar skills

See all →
SkillDesign or optimize their app's monetizationMobile App Monetization Strategyappeeky/aso-skills · by appeekyWhen the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.★ 2.2k GitHub starsSkillDesign, test, or optimize their app's paywallPaywall Optimization (Subscription Apps)appeeky/aso-skills · by appeekyWhen the user wants to design, test, or optimize their app's paywall — layout, copy, pricing display, trial offers, plan structure, hard vs soft paywall, paywall placement, or paywall A/B tests. Use when the user mentions "paywall", "paywall design", "paywall conversion", "trial-to-paid", "soft paywall", "hard paywall", "paywall A/B test", "paywall copy", "plan picker", "annual vs monthly display", "best paywall", "RevenueCat paywall", "Superwall", "Adapty", or "my paywall isn't converting". For overall pricing strategy and monetization model choice, see monetization-strategy. For trial nurture, dunning, and churn, see subscription-lifecycle. For where in the onboarding the paywall fires, see onboarding-optimization.★ 2.2k GitHub starsSkillSets price, structures packages and tiersPricing and packagingcbrock84/headcount · by cbrock84Sets price, structures packages and tiers, and designs the monetization surfaces that carry them — upgrade paths, paywalls, and offer construction. Use this to set or change pricing, design or restructure tiers, choose a pricing metric, build an offer, design upgrade prompts and paywalls, or evaluate whether a pricing change is safe to make.★ 2k GitHub starsSkillHelp users validate willingness-to-payPricing Strategy (Lenny's Podcast)RefoundAI/lenny-skills · by RefoundAIHelp users validate willingness-to-pay, select the right value metrics, and continuously optimize pricing and packaging to drive growth.★ 1.4k GitHub starsSkillDesigns a deliberate sequence of offers so a new customer$100M Money Modelsgetagentseal/founder-playbook · by getagentsealDesigns a deliberate sequence of offers (attraction, upsell, downsell, continuity) so a new customer generates enough cash within ~30 days to fund acquiring the next one - Alex Hormozi's client-financed acquisition. Use when customers buy once and never again, when CAC eats all the profit, when you can't afford to advertise profitably, when the business grows but cash shrinks, when you sell one product at one price, when deciding what to sell first or next, or when structuring upsells, downsells, payment plans, trials, and continuity. Covers the 30-day payback rule, attraction/upsell/downsell/continuity offer types, and cash-flow sequencing for validated markets.★ 729 GitHub starsSkillDesigns irresistible Grand Slam Offers using Alex Hormozi's$100M Offersgetagentseal/founder-playbook · by getagentsealDesigns irresistible Grand Slam Offers using Alex Hormozi's value equation, obstacle-solution mapping, value-cost trim/stack, and offer-naming patterns. Use when fixing low conversion rates, packaging products, pricing services, designing high-converting offers, or when prospects browse but don't buy. Covers value stacking, guarantees, scarcity, urgency, and pricing psychology for validated markets.★ 729 GitHub stars

More from coreyhaines31

SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillPlan, design, or implement an A/B test or experimentA/B Test Setupcoreyhaines31/marketingskills · by coreyhaines31When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.★ 51.1k GitHub starsSkillGenerate, iterate, or scale ad creativecoreyhaines31/marketingskills · by coreyhaines31When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' 'static ads,' 'ad templates,' 'iMessage ad,' 'chat reveal ad,' 'ChatGPT ad,' 'Apple Notes ad,' 'AirDrop ad,' 'creative strategy,' 'creative roadmap,' 'creative retro,' 'hook writing,' 'creative review page,' 'present ad creative for approval,' 'motion video ad,' 'faceless video ad,' 'UGC ad,' 'greenscreen ad,' 'TikTok/Reels ad format,' 'which ad format to make,' 'Meta ad format tier list,' or 'creative format taxonomy.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.★ 51.1k GitHub starsSkillBusiness-brainstorm — Pressure-test a business ideacoreyhaines31/makerskills · by coreyhaines31When you want to pressure-test a potential new business, product, or side project against the serial-founder filter. Not "marketing ideas for a product" (that's marketing-skills:marketing-ideas) — this is "should this business exist + can you win it." Runs the idea through a structured framework (problem, audience, wedge, monetization, moat, portfolio fit, distribution, energy fit, opportunity cost), checks domain availability via /domain, optionally triggers /deep-research for market validation, and outputs a viability brief: build / sleep on it / pass. Archives every idea to ~/.config/makerskills/business-brainstorm/archive/ so past work is searchable. Triggers on "/business-brainstorm," "/brainstorm," "new business idea," "should I build X," "pressure test this idea," "validate this idea," "is X a good business," "what about a [type] for [audience]."★ 855 GitHub starsSkillYour team's shared, AI-ready knowledge base/company-brain — Team-shared AI-ready knowledge basecoreyhaines31/makerskills · by coreyhaines31Your team's shared, AI-ready knowledge base — people, companies, meetings, SOPs, and decisions structured so an agent can answer on your team's behalf. Team-scope sibling to second-brain. Modes — capture, compile (wiki pages + INDEX.md), query (trust-weighted, saved to outputs/), review (verify / deprecate / supersede stale captures), lint, connect, search. Structured raw dirs (people/, companies/, meetings/, sops/, decisions/, customer-language/, sales-objections/). Every capture stamps author, timestamp, and trust status. Optional sync from call transcripts, Slack/email exports, CRM. Vault at ${COMPANY_BRAIN_VAULT:-$HOME/Documents/CompanyBrain}/. Triggers on "/company-brain," "/cb," "capture this into the team brain," "log this meeting," "save this SOP," "compile the company wiki," "query the team brain," "what does the team know about X," "review the company brain," "lint the company brain," "who's the internal expert on X.★ 855 GitHub starsSkillMonthly CFO workflow for a company or agency/company-cfo — Monthly company CFO workflowcoreyhaines31/makerskills · by coreyhaines31Monthly CFO workflow for a company or agency — pull raw data from bank + payment processor + payroll + expense management, categorize and reconcile, compute end-of-month cash via transaction-sum method, update a scenario projector for forward forecasting, write the monthly snapshot report, surface decisions to leadership. Modes — monthly (default; the standing report), weekly (thin cash pulse), scenario (ad-hoc modeling in the projector), pickup (resume where the prior run left off). Anonymized team-scope sibling to personal-cfo (which handles personal household finances). Composes with company-brain (report gets stored + wiki-indexed there), toolify (wire company-specific data sources), loopify (schedule the monthly + weekly runs). Triggers on "/company-cfo," "/cfo," "monthly cash report," "do the CFO snapshot," "CFO monthly," "let's run CFO," "cash projection," "runway forecast," "monthly financials," "cash pulse.★ 855 GitHub stars