Converting Headline Writer

Headline Copywriting — Hero Sections That Convert

by oathdriven · MIT license · ★ 28 on GitHub

Headline Copywriting — Hero Sections That Convert cover

Write and rewrite landing-page headlines, hero sections, and their CTAs using a pain + dream-outcome formula, awareness-stage diagnosis, and a curated SaaS swipe file. Use when the user asks to "write a headline", "rewrite the hero",…

---
name: rymac-headline-copywriting
description: Write and rewrite landing-page headlines, hero sections, and their CTAs using a pain + dream-outcome formula, awareness-stage diagnosis, and a curated SaaS swipe file. Use when the user asks to "write a headline", "rewrite the hero", "fix the landing page headline", "give me headline options", "punch up the hero", or works on above-the-fold copy for allodra.ai, sierra6ai.com, or any writing-room landing page. Make sure to use this skill whenever a headline, hero section, subheadline, or CTA button copy is being written or critiqued.
argument-hint: [brand/page + task, e.g. "allodra.ai hero rewrite"]
---

# Headline Copywriting — Hero Sections That Convert

Write headlines that name a felt pain and promise the dream outcome, then carry that promise through the subheadline into the CTA. The headline is the highest-leverage text on the page; treat it as the product of a process, not a first draft.

Read these supporting files on demand:
- `${CLAUDE_SKILL_DIR}/references/headline-formulas.md` — the full formula library (Hormozi value equation, PAS, enemy positioning, Schwartz awareness stages, Copyhackers, Harry Dry, Julian Shapiro, StoryBrand) and the 20 headline rules
- `${CLAUDE_SKILL_DIR}/references/hero-and-cta.md` — hero-section anatomy (job of each element) and CTA/click-trigger patterns with conversion evidence
- `${CLAUDE_SKILL_DIR}/references/swipe-file.md` — 38 real SaaS headlines tagged by pattern, before→after rewrites, and stealable sentence structures

## Load first — brand context

| Brand | Load | Hard rules |

Overview

Write headlines that name a felt pain and promise the dream outcome, then carry that promise through the subheadline into the CTA. The headline is the highest-leverage text on the page; treat it as the product of a process, not a first draft.

Manual install (npx, ZIP)
Claude Codenpx skills add oathdriven/rymac-skills --skill rymac-headline-copywriting -g -a claude-code
Claude Code (degit)npx degit oathdriven/rymac-skills/skills/rymac-headline-copywriting#main ~/.claude/skills/rymac-headline-copywriting
Claude.ai / desktopZip the folder 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.md8.7 KB
Read SKILL.md here
oathdriven/main1 file shown
SKILL.md
Show the full text112 lines

Headline Copywriting — Hero Sections That Convert

Write headlines that name a felt pain and promise the dream outcome, then carry that promise through the subheadline into the CTA. The headline is the highest-leverage text on the page; treat it as the product of a process, not a first draft.

Read these supporting files on demand:

  • ${CLAUDE_SKILL_DIR}/references/headline-formulas.md — the full formula library (Hormozi value equation, PAS, enemy positioning, Schwartz awareness stages, Copyhackers, Harry Dry, Julian Shapiro, StoryBrand) and the 20 headline rules
  • ${CLAUDE_SKILL_DIR}/references/hero-and-cta.md — hero-section anatomy (job of each element) and CTA/click-trigger patterns with conversion evidence
  • ${CLAUDE_SKILL_DIR}/references/swipe-file.md — 38 real SaaS headlines tagged by pattern, before→after rewrites, and stealable sentence structures

Load first — brand context

Brand Load Hard rules
Allodra writing-room/docs/voice-allodra.md Honesty guardrail (see below); use the approved vocabulary
Sierra-6 writing-room/docs/voice-sierra6.md (if built) Never sell leads; veteran-operator tone
Other The brand's voice doc, or ask for positioning —

Paths are relative to the workspace root — Glob for **/voice-allodra.md if the session starts in a subfolder. The voice doc supplies the enemy, the metaphor, the approved words, and the claims that are safe to make (guardrails can change — the voice doc is always the source of truth). Never write a headline before reading it.

Standalone use (no voice docs / this skill was shared with you): if no voice doc exists, check ${CLAUDE_SKILL_DIR}/my-brand-voice.md. If that's missing too, interview the user briefly before writing anything: (1) what do you sell and to whom, (2) the enemy (the tool/practice/incumbent the reader blames — never the reader), (3) the dream outcome in the customer's words, (4) proven pains — real lines from replies, reviews, or calls, (5) approved and banned vocabulary, (6) claim guardrails (what's safe to promise publicly). Save the answers to ${CLAUDE_SKILL_DIR}/my-brand-voice.md so the user answers once; load it in place of the voice doc from then on. The "Allodra defaults" section at the bottom shows what a filled-in profile looks like.

The core formula

HEADLINE  = PAIN (villain named or implied) × DREAM OUTCOME (specific, visualizable)
SUBHEAD   = the mechanism — what it is and why the promise is believable
CTA       = hand them the outcome, first person, risk killed beside the button

Run every candidate through the Hormozi value lens: raise the dream outcome and its perceived likelihood (proof beside the claim); cut time delay ("in 7 days", "instantly") and effort/sacrifice ("without X"). A headline that only states pain agitates; a headline that only states outcome floats. The strongest pair both: "Stop paying a penalty for growth" = pain (growth tax) with the outcome (penalty-free scaling) implied in the same breath.

The villain is always a tool, category, incumbent, or practice — never the reader's own failure.

Workflow

Copy this checklist and tick it off:

  • 1. Load the brand voice doc. Note the enemy, approved vocabulary, and any claim guardrails.
  • 2. Diagnose the awareness stage of the page's traffic (table in references/headline-formulas.md). Homepage traffic is usually solution-aware → lead with pain + differentiated outcome. Cold-ad traffic skews problem-aware → lead harder on pain.
  • 3. Mine the pain and dream outcome in customer language. Sources in priority order: proven hooks that already got replies (cold-email sequences, VSL hooks), actual reply/call language, the voice doc. Steal the customer's sentence; don't invent one.
  • 4. Bleed the tap — write 20+ headlines minimum across at least 4 pattern categories (enemy/"Stop X", dream-outcome, specificity-number, metaphor, clarity). The first dozen are always predictable; gold shows up late. Use the stealable structures in the swipe file.
  • 5. Score with the five tests (below). Shortlist the top 3.
  • 6. Assemble the full hero for the winner: eyebrow → H1 → subhead → CTA + click trigger → proof line (element jobs in references/hero-and-cta.md).
  • 7. Honesty check against the brand guardrail. A headline you can't ship is a failed headline, no matter how good.
  • 8. Deliver in the output format below and save to writing-room/drafts/[brand]-[slug]-draft.md (standalone: wherever the user keeps drafts, or beside the page being edited).

The five tests (scoring gate)

Every shortlisted headline must pass all five:

  1. Grunt test — a stranger glancing for 3 seconds knows what you sell, how it helps, and what to do next.
  2. Visualizable — the reader can see it ("1,000 songs in your pocket"). Abstractions evaporate.
  3. Falsifiable — a specific claim that could be proven wrong ("30 minutes or it's free") gets believed. Vague claims get ignored.
  4. Un-copyable — if a competitor could run the same line word-for-word, it's a category label, not a headline.
  5. One big idea — one reader, one pain, one promise. Two ideas = half the strength of each.

Mechanics: ~6–12 words, roughly 7th-grade reading level, no hype stacking, concrete numbers over adjectives (odd/precise numbers read as counted, not invented).

The CTA segue

The button is the actionable next step to the headline's promise — a continuation of the story, never a generic verb.

  • Call to value: [verb] + [the thing they actually want]. "See the 3-year math" beats "Learn more".
  • First person converts: "Start my free trial" beat "your" by +90% CTR in the canonical test. Default to first person.
  • Kill risk at the click: microcopy beside the button — "No credit card", "Takes 30 seconds", "One-time, own it forever" (+19% signups documented for a single click trigger).
  • Match CTA weight to awareness: most-aware → hard CTA ("Buy it once"); earlier stages → soft first CTA ("See how it works") with the hard CTA repeated lower.

Full patterns and evidence: ${CLAUDE_SKILL_DIR}/references/hero-and-cta.md.

Output format

Deliver exactly this shape:

## Shortlist (from N variants)
| # | Headline | Pattern | Why it wins |
|---|---|---|---|
| 1 | ... | enemy / pain-led | ... |
| 2 | ... | dream-outcome | ... |
| 3 | ... | specificity | ... |

## Recommended hero (option 1)
**Eyebrow:** ...
**H1:** ...
**Subhead:** ...
**CTA:** [button] + [click-trigger microcopy]
**Proof line:** ...

## Why this beats the current hero
(1–3 sentences against the incumbent headline)

## Full variant list
(all 20+, grouped by pattern — the user picks differently than you'd predict)

Allodra defaults (worked example)

  • Current hero (the incumbent to beat): "Stop renting your CRM. Own it outright." — leads with the mechanism (CRM ownership). Weakness: "CRM" makes the reader think software category, not their own pain.
  • Target energy: "Stop paying a penalty for growth." — leads with the felt pain (you're taxed for succeeding) and implies the dream outcome (scale free and clear).
  • The enemy: the digital landlord — rent, seat creep, the growth tax. Attack the incumbent practice (renting), never the reader.
  • Approved vocabulary: landlord · rent · growth tax · seat creep · take title · own it · allodial · digital real estate · free and clear · one-time · stop renting.
  • ⚠️ Honesty guardrail (hard rule): safe to claim "buy it once, own the license, no monthly rent, no growth tax." Do NOT claim "deployed to your own cloud / nobody can ever lock you out" in public copy until reseller rights are live. The honesty is the edge — never trade it for a bigger number.
  • Proven pains that already got replies (mine these first): the growth tax / taxed for succeeding · renting vs owning · the 3-year number ($18k GHL / $43k HubSpot) · "you're a digital tenant" · "why I fired GoHighLevel".

Read $ARGUMENTS for the brand, page, and task. If no brand is named, ask which brand — the voice doc changes everything.

1---
2name: rymac-headline-copywriting
3description: Write and rewrite landing-page headlines, hero sections, and their CTAs using a pain + dream-outcome formula, awareness-stage diagnosis, and a curated SaaS swipe file. Use when the user asks to "write a headline", "rewrite the hero", "fix the landing page headline", "give me headline options", "punch up the hero", or works on above-the-fold copy for allodra.ai, sierra6ai.com, or any writing-room landing page. Make sure to use this skill whenever a headline, hero section, subheadline, or CTA button copy is being written or critiqued.
4argument-hint: [brand/page + task, e.g. "allodra.ai hero rewrite"]
5---
6 
7# Headline Copywriting — Hero Sections That Convert
8 
9Write headlines that name a felt pain and promise the dream outcome, then carry that promise through the subheadline into the CTA. The headline is the highest-leverage text on the page; treat it as the product of a process, not a first draft.
10 
11Read these supporting files on demand:
12- `${CLAUDE_SKILL_DIR}/references/headline-formulas.md` — the full formula library (Hormozi value equation, PAS, enemy positioning, Schwartz awareness stages, Copyhackers, Harry Dry, Julian Shapiro, StoryBrand) and the 20 headline rules
13- `${CLAUDE_SKILL_DIR}/references/hero-and-cta.md` — hero-section anatomy (job of each element) and CTA/click-trigger patterns with conversion evidence
14- `${CLAUDE_SKILL_DIR}/references/swipe-file.md` — 38 real SaaS headlines tagged by pattern, before→after rewrites, and stealable sentence structures
15 
16## Load first — brand context
17 
18| Brand | Load | Hard rules |
19|---|---|---|
20| Allodra | `writing-room/docs/voice-allodra.md` | Honesty guardrail (see below); use the approved vocabulary |
21| Sierra-6 | `writing-room/docs/voice-sierra6.md` (if built) | Never sell leads; veteran-operator tone |
22| Other | The brand's voice doc, or ask for positioning | — |
23 
24Paths are relative to the workspace root — Glob for `**/voice-allodra.md` if the session starts in a subfolder. The voice doc supplies the enemy, the metaphor, the approved words, and the claims that are safe to make (guardrails can change — the voice doc is always the source of truth). Never write a headline before reading it.
25 
26**Standalone use (no voice docs / this skill was shared with you):** if no voice doc exists, check `${CLAUDE_SKILL_DIR}/my-brand-voice.md`. If that's missing too, interview the user briefly before writing anything: (1) what do you sell and to whom, (2) the enemy (the tool/practice/incumbent the reader blames — never the reader), (3) the dream outcome in the customer's words, (4) proven pains — real lines from replies, reviews, or calls, (5) approved and banned vocabulary, (6) claim guardrails (what's safe to promise publicly). Save the answers to `${CLAUDE_SKILL_DIR}/my-brand-voice.md` so the user answers once; load it in place of the voice doc from then on. The "Allodra defaults" section at the bottom shows what a filled-in profile looks like.
27 
28## The core formula
29 
30```
31HEADLINE = PAIN (villain named or implied) × DREAM OUTCOME (specific, visualizable)
32SUBHEAD = the mechanism — what it is and why the promise is believable
33CTA = hand them the outcome, first person, risk killed beside the button
34```
35 
36Run every candidate through the Hormozi value lens: raise the **dream outcome** and its **perceived likelihood** (proof beside the claim); cut **time delay** ("in 7 days", "instantly") and **effort/sacrifice** ("without X"). A headline that only states pain agitates; a headline that only states outcome floats. The strongest pair both: *"Stop paying a penalty for growth"* = pain (growth tax) with the outcome (penalty-free scaling) implied in the same breath.
37 
38The villain is always a tool, category, incumbent, or practice — **never the reader's own failure.**
39 
40## Workflow
41 
42Copy this checklist and tick it off:
43 
44- [ ] 1. **Load the brand voice doc.** Note the enemy, approved vocabulary, and any claim guardrails.
45- [ ] 2. **Diagnose the awareness stage** of the page's traffic (table in `references/headline-formulas.md`). Homepage traffic is usually solution-aware → lead with pain + differentiated outcome. Cold-ad traffic skews problem-aware → lead harder on pain.
46- [ ] 3. **Mine the pain and dream outcome in customer language.** Sources in priority order: proven hooks that already got replies (cold-email sequences, VSL hooks), actual reply/call language, the voice doc. Steal the customer's sentence; don't invent one.
47- [ ] 4. **Bleed the tap — write 20+ headlines minimum** across at least 4 pattern categories (enemy/"Stop X", dream-outcome, specificity-number, metaphor, clarity). The first dozen are always predictable; gold shows up late. Use the stealable structures in the swipe file.
48- [ ] 5. **Score with the five tests** (below). Shortlist the top 3.
49- [ ] 6. **Assemble the full hero for the winner:** eyebrow → H1 → subhead → CTA + click trigger → proof line (element jobs in `references/hero-and-cta.md`).
50- [ ] 7. **Honesty check** against the brand guardrail. A headline you can't ship is a failed headline, no matter how good.
51- [ ] 8. **Deliver** in the output format below and save to `writing-room/drafts/[brand]-[slug]-draft.md` (standalone: wherever the user keeps drafts, or beside the page being edited).
52 
53## The five tests (scoring gate)
54 
55Every shortlisted headline must pass all five:
56 
571. **Grunt test** — a stranger glancing for 3 seconds knows what you sell, how it helps, and what to do next.
582. **Visualizable** — the reader can see it ("1,000 songs in your pocket"). Abstractions evaporate.
593. **Falsifiable** — a specific claim that could be proven wrong ("30 minutes or it's free") gets believed. Vague claims get ignored.
604. **Un-copyable** — if a competitor could run the same line word-for-word, it's a category label, not a headline.
615. **One big idea** — one reader, one pain, one promise. Two ideas = half the strength of each.
62 
63Mechanics: ~6–12 words, roughly 7th-grade reading level, no hype stacking, concrete numbers over adjectives (odd/precise numbers read as counted, not invented).
64 
65## The CTA segue
66 
67The button is the actionable next step to the headline's promise — a continuation of the story, never a generic verb.
68 
69- **Call to value:** `[verb] + [the thing they actually want]`. "See the 3-year math" beats "Learn more".
70- **First person converts:** "Start **my** free trial" beat "your" by +90% CTR in the canonical test. Default to first person.
71- **Kill risk at the click:** microcopy beside the button — "No credit card", "Takes 30 seconds", "One-time, own it forever" (+19% signups documented for a single click trigger).
72- **Match CTA weight to awareness:** most-aware → hard CTA ("Buy it once"); earlier stages → soft first CTA ("See how it works") with the hard CTA repeated lower.
73 
74Full patterns and evidence: `${CLAUDE_SKILL_DIR}/references/hero-and-cta.md`.
75 
76## Output format
77 
78Deliver exactly this shape:
79 
80```markdown
81## Shortlist (from N variants)
82| # | Headline | Pattern | Why it wins |
83|---|---|---|---|
84| 1 | ... | enemy / pain-led | ... |
85| 2 | ... | dream-outcome | ... |
86| 3 | ... | specificity | ... |
87 
88## Recommended hero (option 1)
89**Eyebrow:** ...
90**H1:** ...
91**Subhead:** ...
92**CTA:** [button] + [click-trigger microcopy]
93**Proof line:** ...
94 
95## Why this beats the current hero
96(1–3 sentences against the incumbent headline)
97 
98## Full variant list
99(all 20+, grouped by pattern — the user picks differently than you'd predict)
100```
101 
102## Allodra defaults (worked example)
103 
104- **Current hero (the incumbent to beat):** "Stop renting your CRM. Own it outright." — leads with the *mechanism* (CRM ownership). Weakness: "CRM" makes the reader think software category, not their own pain.
105- **Target energy:** "Stop paying a penalty for growth." — leads with the *felt pain* (you're taxed for succeeding) and implies the dream outcome (scale free and clear).
106- **The enemy:** the digital landlord — rent, seat creep, the growth tax. Attack the incumbent practice (renting), never the reader.
107- **Approved vocabulary:** landlord · rent · growth tax · seat creep · take title · own it · allodial · digital real estate · free and clear · one-time · stop renting.
108- **⚠️ Honesty guardrail (hard rule):** safe to claim **"buy it once, own the license, no monthly rent, no growth tax."** Do NOT claim "deployed to your own cloud / nobody can ever lock you out" in public copy until reseller rights are live. The honesty is the edge — never trade it for a bigger number.
109- **Proven pains that already got replies** (mine these first): the growth tax / taxed for succeeding · renting vs owning · the 3-year number ($18k GHL / $43k HubSpot) · "you're a digital tenant" · "why I fired GoHighLevel".
110 
111Read `$ARGUMENTS` for the brand, page, and task. If no brand is named, ask which brand — the voice doc changes everything.
112 
View all files on GitHub →

Details

License
MIT
Stars on the repo
★ 28
Checked
Source
oathdriven/rymac-skills ↗
Creator
oathdriven · 12 listings
View creator

Similar skills

See all →
SkillCompetitor Ad AnalyzerScrapeCreators/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 starsSkillProduct Listing Visual Creatorfeichanggege/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 starsSkillPricing Page Builderboraoztunc/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 starsSkillArticle Opening 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 starsSkillEcommerce Landing Page Designerkgelster/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 starsSkillDirect Response CopywriterDeupaxx/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 oathdriven

SkillAEO Blog Writeroathdriven/rymac-skills · by oathdrivenWrites SEO + AEO (Answer Engine Optimized) blog posts built to rank on Google AND get cited by AI answer engines (Google AI Overviews, ChatGPT, Perplexity). Runs live SERP recon, writes answer-first, and wires internal + external authority links. Use when someone wants a blog post that ranks and gets quoted by AI, says "write an AEO post", "answer-engine optimization", "get cited by AI Overviews", "rank AND get quoted", or wants the pro version of an SEO article. For quick keyword blog posts use rymac-seo-writer instead.★ 28 GitHub starsSkillPaid Traffic Landing Pageoathdriven/rymac-skills · by oathdrivenResearches a niche's pains and builds a single-screen, one-decision landing page for paid ad traffic (Meta/Google/YouTube) — headline-first, message-matched to the ad, with one CTA and a risk-reversal/trust element, nothing else. Use when the user asks to "make a landing page for ads", "build a page for this campaign", "squeeze page", "lead capture page", "opt-in page", or wants to convert paid traffic for a niche. Make sure to use this skill for any ad-destination page; for multi-section marketing websites use website-builder or build-premium-website instead.★ 28 GitHub starsSkillCall Scheduling Funneloathdriven/rymac-skills · by oathdrivenBuilds the conversion plumbing that turns site traffic into scheduled calls: chat scheduler, AI voice agent, emergency escalation that pings a live on-call human, non-emergency booking into one shared calendar engine, and after-hours handling. Use when the user asks to "wire up the call funnel", "add the chat scheduler", "set up the voice agent", "convert traffic into scheduled calls", "handle after-hours calls", or builds any page whose goal is booked calls. Make sure to use this skill whenever call-booking, voice-agent, or emergency-routing plumbing is being designed or built.★ 28 GitHub starsSkillDirect Response Letteroathdriven/rymac-skills · by oathdrivenWrites direct-response P.A.S. (Problem-Agitate-Solution) sales letters in the RyMac voice, in the Dan Kennedy direct-letter tradition, modeled on the proven Sierra-6 letter. A personal letter to one reader with self-identification pain bullets, "you're not alone" normalization, cinematic agitation, an I-was-you origin story, a named-mechanism reveal, imagine future-pacing, and a P.S. close, formatted for skimmers (bold/underline paths). Use when the user asks to "write a sales letter", "write the letter", "P.A.S. letter", "direct sales letter", "Dan Kennedy letter", "pain-agitate-solution copy", says "set up my sales letter voice profile", or needs the letter section of a sales page. Make sure to use this skill whenever long-form persuasive letter copy is being written, rewritten, or critiqued.★ 28 GitHub starsSkillExit Intent Popupoathdriven/rymac-skills · by oathdrivenBuilds RyMac's exit-intent popup pattern on any landing or sales page: desktop mouse-leave plus the mobile fast-scroll-up trigger, offering a supportive asset that is deliberately NEVER promised on the page itself. Use when the user asks to "add an exit pop", "build an exit popup", "exit intent", "catch people leaving the page", or when finishing any sales/landing page build. Make sure to use this skill whenever an exit-intent popup or leave-catcher is being designed, built, or critiqued.★ 28 GitHub starsSkillNiche Offer Validatoroathdriven/rymac-skills · by oathdrivenRuns RyMac's offer-validation research method. Fans out parallel subagents to map a niche's pain points in their own words, the psychology of why the pain persists, a competitor matrix, demand proof with a lead-pool count, the niche's unit economics (revenue bands, net margin range, where the margin comes from, the P&L split, average ticket), and a response-behavior audit scoring the niche against your mechanism, then delivers a build/pivot/skip verdict with the underserved wedge, the USP, an affordability call on what the niche can actually pay, a delivery-economics check that YOUR own margin clears a 65% floor (with the lowest price you could charge and the owned-vs-rented cost of your stack), the profit left on the table, and ROI hooks written in their own numbers. Use when the user asks to "research a niche", "validate an offer", "find the pain points", "run niche research", "should I build this", "who else sells this", "what are the margins in X", "can they afford my offer", "what should I price this at", or has an idea or observation about a market. Make sure to use this skill whenever the user is deciding what to build, sell, price, or make content about next.★ 28 GitHub stars