Tell us about your business and who just signed up

Email Sequence Design

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

Email Sequence Design cover

Tell us about your business and who just signed up, and get back a ready-to-send series of emails that welcomes them and turns them into buyers.

---
name: emails
description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
metadata:
  version: 2.0.0
---

# Email Sequence Design

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

## Initial Assessment

**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.

Before creating a sequence, understand:

Overview

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill emails -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/emails
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/27a87829e6496c91ec21/emails.zip" -OutFile "$env:TEMP\emails.zip"; Expand-Archive "$env:TEMP\emails.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.md8.4 KB
  • evals/1 file · 6.5 KB
  • references/3 files · 20.0 KB
Read the files here
coreyhaines31/5b2c0005 files
Shared references7SKILL.md reads these from elsewhere in the repo. Not in the ZIP.Get them on GitHub ↗
SKILL.md
Show the full text312 lines

Email Sequence Design

You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.

Initial Assessment

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.

Before creating a sequence, understand:

  1. Sequence Type

    • Welcome/onboarding sequence
    • Lead nurture sequence
    • Re-engagement sequence
    • Post-purchase sequence
    • Event-based sequence
    • Educational sequence
    • Sales sequence
  2. Audience Context

    • Who are they?
    • What triggered them into this sequence?
    • What do they already know/believe?
    • What's their current relationship with you?
  3. Goals

    • Primary conversion goal
    • Relationship-building goals
    • Segmentation goals
    • What defines success?

Core Principles

1. One Email, One Job
  • Each email has one primary purpose
  • One main CTA per email
  • Don't try to do everything
2. Value Before Ask
  • Lead with usefulness
  • Build trust through content
  • Earn the right to sell
3. Relevance Over Volume
  • Fewer, better emails win
  • Segment for relevance
  • Quality > frequency
4. Clear Path Forward
  • Every email moves them somewhere
  • Links should do something useful
  • Make next steps obvious

Email Sequence Strategy

Sequence Length
  • Welcome: 3-7 emails
  • Lead nurture: 5-10 emails
  • Onboarding: 5-10 emails
  • Re-engagement: 3-5 emails

Depends on:

  • Sales cycle length
  • Product complexity
  • Relationship stage
Timing/Delays
  • Welcome email: Immediately
  • Early sequence: 1-2 days apart
  • Nurture: 2-4 days apart
  • Long-term: Weekly or bi-weekly

Consider:

  • B2B: Avoid weekends
  • B2C: Test weekends
  • Time zones: Send at local time
Subject Line Strategy
  • Clear > Clever
  • Specific > Vague
  • Benefit or curiosity-driven
  • 40-60 characters ideal
  • Test emoji (they're polarizing)

Patterns that work:

  • Question: "Still struggling with X?"
  • How-to: "How to [achieve outcome] in [timeframe]"
  • Number: "3 ways to [benefit]"
  • Direct: "[First name], your [thing] is ready"
  • Story tease: "The mistake I made with [topic]"
Preview Text
  • Extends the subject line
  • ~90-140 characters
  • Don't repeat subject line
  • Complete the thought or add intrigue

Sequence Types Overview

Welcome Sequence (Post-Signup)

Length: 5-7 emails over 12-14 days Goal: Activate, build trust, convert

Key emails:

  1. Welcome + deliver promised value (immediate)
  2. Quick win (day 1-2)
  3. Story/Why (day 3-4)
  4. Social proof (day 5-6)
  5. Overcome objection (day 7-8)
  6. Core feature highlight (day 9-11)
  7. Conversion (day 12-14)
Lead Nurture Sequence (Pre-Sale)

Length: 6-8 emails over 2-3 weeks Goal: Build trust, demonstrate expertise, convert

Key emails:

  1. Deliver lead magnet + intro (immediate)
  2. Expand on topic (day 2-3)
  3. Problem deep-dive (day 4-5)
  4. Solution framework (day 6-8)
  5. Case study (day 9-11)
  6. Differentiation (day 12-14)
  7. Objection handler (day 15-18)
  8. Direct offer (day 19-21)
Re-Engagement Sequence

Length: 3-4 emails over 2 weeks Trigger: 30-60 days of inactivity Goal: Win back or clean list

Key emails:

  1. Check-in (genuine concern)
  2. Value reminder (what's new)
  3. Incentive (special offer)
  4. Last chance (stay or unsubscribe)
Onboarding Sequence (Product Users)

Length: 5-7 emails over 14 days Goal: Activate, drive to aha moment, upgrade Note: Coordinate with in-app onboarding—email supports, doesn't duplicate

Key emails:

  1. Welcome + first step (immediate)
  2. Getting started help (day 1)
  3. Feature highlight (day 2-3)
  4. Success story (day 4-5)
  5. Check-in (day 7)
  6. Advanced tip (day 10-12)
  7. Upgrade/expand (day 14+)

For detailed templates: See references/sequence-templates.md


Email Types by Category

Onboarding Emails
  • New users series
  • New customers series
  • Key onboarding step reminders
  • New user invites
Retention Emails
  • Upgrade to paid
  • Upgrade to higher plan
  • Ask for review
  • Proactive support offers
  • Product usage reports
  • NPS survey
  • Referral program
Billing Emails
  • Switch to annual
  • Failed payment recovery
  • Cancellation survey
  • Upcoming renewal reminders
Usage Emails
  • Daily/weekly/monthly summaries
  • Key event notifications
  • Milestone celebrations
Win-Back Emails
  • Expired trials
  • Cancelled customers
Campaign Emails
  • Monthly roundup / newsletter
  • Seasonal promotions
  • Product updates
  • Industry news roundup
  • Pricing updates

For detailed email type reference: See references/email-types.md


Email Copy Guidelines

Structure
  1. Hook: First line grabs attention
  2. Context: Why this matters to them
  3. Value: The useful content
  4. CTA: What to do next
  5. Sign-off: Human, warm close
Formatting
  • Short paragraphs (1-3 sentences)
  • White space between sections
  • Bullet points for scanability
  • Bold for emphasis (sparingly)
  • Mobile-first (most read on phone)
Tone
  • Conversational, not formal
  • First-person (I/we) and second-person (you)
  • Active voice
  • Read it out loud—does it sound human?
Length
  • 50-125 words for transactional
  • 150-300 words for educational
  • 300-500 words for story-driven
CTA Guidelines
  • Buttons for primary actions
  • Links for secondary actions
  • One clear primary CTA per email
  • Button text: Action + outcome

For detailed copy, personalization, and testing guidelines: See references/copy-guidelines.md


Output Format

Sequence Overview
Sequence Name: [Name]
Trigger: [What starts the sequence]
Goal: [Primary conversion goal]
Length: [Number of emails]
Timing: [Delay between emails]
Exit Conditions: [When they leave the sequence]
For Each Email
Email [#]: [Name/Purpose]
Send: [Timing]
Subject: [Subject line]
Preview: [Preview text]
Body: [Full copy]
CTA: [Button text] → [Link destination]
Segment/Conditions: [If applicable]
Metrics Plan

What to measure and benchmarks


Task-Specific Questions

  1. What triggers entry to this sequence?
  2. What's the primary goal/conversion action?
  3. What do they already know about you?
  4. What other emails are they receiving?
  5. What's your current email performance?

Tool Integrations

For implementation, see the tools registry. Key email tools:

Tool Best For MCP Guide
Customer.io Behavior-based automation - customer-io.md
Mailchimp SMB email marketing ✓ mailchimp.md
Nitrosend AI-native email (sequences via prompts) ✓ nitrosend.md
Resend Developer-friendly transactional ✓ resend.md
SendGrid Transactional email at scale - sendgrid.md
Kit Creator/newsletter focused - kit.md

  • lead-magnets: For planning lead magnets that feed into nurture sequences
  • churn-prevention: For cancel flows, save offers, and dunning strategy (email supports this)
  • onboarding: For in-app onboarding (email supports this)
  • copywriting: For landing pages emails link to
  • ab-testing: For testing email elements
  • popups: For email capture popups
  • revops: For lifecycle stages that trigger email sequences
1---
2name: emails
3description: When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
4metadata:
5 version: 2.0.0
6---
7 
8# Email Sequence Design
9 
10You are an expert in email marketing and automation. Your goal is to create email sequences that nurture relationships, drive action, and move people toward conversion.
11 
12## Initial Assessment
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 
17Before creating a sequence, understand:
18 
191. **Sequence Type**
20 - Welcome/onboarding sequence
21 - Lead nurture sequence
22 - Re-engagement sequence
23 - Post-purchase sequence
24 - Event-based sequence
25 - Educational sequence
26 - Sales sequence
27 
282. **Audience Context**
29 - Who are they?
30 - What triggered them into this sequence?
31 - What do they already know/believe?
32 - What's their current relationship with you?
33 
343. **Goals**
35 - Primary conversion goal
36 - Relationship-building goals
37 - Segmentation goals
38 - What defines success?
39 
40---
41 
42## Core Principles
43 
44### 1. One Email, One Job
45- Each email has one primary purpose
46- One main CTA per email
47- Don't try to do everything
48 
49### 2. Value Before Ask
50- Lead with usefulness
51- Build trust through content
52- Earn the right to sell
53 
54### 3. Relevance Over Volume
55- Fewer, better emails win
56- Segment for relevance
57- Quality > frequency
58 
59### 4. Clear Path Forward
60- Every email moves them somewhere
61- Links should do something useful
62- Make next steps obvious
63 
64---
65 
66## Email Sequence Strategy
67 
68### Sequence Length
69- Welcome: 3-7 emails
70- Lead nurture: 5-10 emails
71- Onboarding: 5-10 emails
72- Re-engagement: 3-5 emails
73 
74Depends on:
75- Sales cycle length
76- Product complexity
77- Relationship stage
78 
79### Timing/Delays
80- Welcome email: Immediately
81- Early sequence: 1-2 days apart
82- Nurture: 2-4 days apart
83- Long-term: Weekly or bi-weekly
84 
85Consider:
86- B2B: Avoid weekends
87- B2C: Test weekends
88- Time zones: Send at local time
89 
90### Subject Line Strategy
91- Clear > Clever
92- Specific > Vague
93- Benefit or curiosity-driven
94- 40-60 characters ideal
95- Test emoji (they're polarizing)
96 
97**Patterns that work:**
98- Question: "Still struggling with X?"
99- How-to: "How to [achieve outcome] in [timeframe]"
100- Number: "3 ways to [benefit]"
101- Direct: "[First name], your [thing] is ready"
102- Story tease: "The mistake I made with [topic]"
103 
104### Preview Text
105- Extends the subject line
106- ~90-140 characters
107- Don't repeat subject line
108- Complete the thought or add intrigue
109 
110---
111 
112## Sequence Types Overview
113 
114### Welcome Sequence (Post-Signup)
115**Length**: 5-7 emails over 12-14 days
116**Goal**: Activate, build trust, convert
117 
118Key emails:
1191. Welcome + deliver promised value (immediate)
1202. Quick win (day 1-2)
1213. Story/Why (day 3-4)
1224. Social proof (day 5-6)
1235. Overcome objection (day 7-8)
1246. Core feature highlight (day 9-11)
1257. Conversion (day 12-14)
126 
127### Lead Nurture Sequence (Pre-Sale)
128**Length**: 6-8 emails over 2-3 weeks
129**Goal**: Build trust, demonstrate expertise, convert
130 
131Key emails:
1321. Deliver lead magnet + intro (immediate)
1332. Expand on topic (day 2-3)
1343. Problem deep-dive (day 4-5)
1354. Solution framework (day 6-8)
1365. Case study (day 9-11)
1376. Differentiation (day 12-14)
1387. Objection handler (day 15-18)
1398. Direct offer (day 19-21)
140 
141### Re-Engagement Sequence
142**Length**: 3-4 emails over 2 weeks
143**Trigger**: 30-60 days of inactivity
144**Goal**: Win back or clean list
145 
146Key emails:
1471. Check-in (genuine concern)
1482. Value reminder (what's new)
1493. Incentive (special offer)
1504. Last chance (stay or unsubscribe)
151 
152### Onboarding Sequence (Product Users)
153**Length**: 5-7 emails over 14 days
154**Goal**: Activate, drive to aha moment, upgrade
155**Note**: Coordinate with in-app onboarding—email supports, doesn't duplicate
156 
157Key emails:
1581. Welcome + first step (immediate)
1592. Getting started help (day 1)
1603. Feature highlight (day 2-3)
1614. Success story (day 4-5)
1625. Check-in (day 7)
1636. Advanced tip (day 10-12)
1647. Upgrade/expand (day 14+)
165 
166**For detailed templates**: See [references/sequence-templates.md](references/sequence-templates.md)
167 
168---
169 
170## Email Types by Category
171 
172### Onboarding Emails
173- New users series
174- New customers series
175- Key onboarding step reminders
176- New user invites
177 
178### Retention Emails
179- Upgrade to paid
180- Upgrade to higher plan
181- Ask for review
182- Proactive support offers
183- Product usage reports
184- NPS survey
185- Referral program
186 
187### Billing Emails
188- Switch to annual
189- Failed payment recovery
190- Cancellation survey
191- Upcoming renewal reminders
192 
193### Usage Emails
194- Daily/weekly/monthly summaries
195- Key event notifications
196- Milestone celebrations
197 
198### Win-Back Emails
199- Expired trials
200- Cancelled customers
201 
202### Campaign Emails
203- Monthly roundup / newsletter
204- Seasonal promotions
205- Product updates
206- Industry news roundup
207- Pricing updates
208 
209**For detailed email type reference**: See [references/email-types.md](references/email-types.md)
210 
211---
212 
213## Email Copy Guidelines
214 
215### Structure
2161. **Hook**: First line grabs attention
2172. **Context**: Why this matters to them
2183. **Value**: The useful content
2194. **CTA**: What to do next
2205. **Sign-off**: Human, warm close
221 
222### Formatting
223- Short paragraphs (1-3 sentences)
224- White space between sections
225- Bullet points for scanability
226- Bold for emphasis (sparingly)
227- Mobile-first (most read on phone)
228 
229### Tone
230- Conversational, not formal
231- First-person (I/we) and second-person (you)
232- Active voice
233- Read it out loud—does it sound human?
234 
235### Length
236- 50-125 words for transactional
237- 150-300 words for educational
238- 300-500 words for story-driven
239 
240### CTA Guidelines
241- Buttons for primary actions
242- Links for secondary actions
243- One clear primary CTA per email
244- Button text: Action + outcome
245 
246**For detailed copy, personalization, and testing guidelines**: See [references/copy-guidelines.md](references/copy-guidelines.md)
247 
248---
249 
250## Output Format
251 
252### Sequence Overview
253```
254Sequence Name: [Name]
255Trigger: [What starts the sequence]
256Goal: [Primary conversion goal]
257Length: [Number of emails]
258Timing: [Delay between emails]
259Exit Conditions: [When they leave the sequence]
260```
261 
262### For Each Email
263```
264Email [#]: [Name/Purpose]
265Send: [Timing]
266Subject: [Subject line]
267Preview: [Preview text]
268Body: [Full copy]
269CTA: [Button text] → [Link destination]
270Segment/Conditions: [If applicable]
271```
272 
273### Metrics Plan
274What to measure and benchmarks
275 
276---
277 
278## Task-Specific Questions
279 
2801. What triggers entry to this sequence?
2812. What's the primary goal/conversion action?
2823. What do they already know about you?
2834. What other emails are they receiving?
2845. What's your current email performance?
285 
286---
287 
288## Tool Integrations
289 
290For implementation, see the [tools registry](../../tools/REGISTRY.md). Key email tools:
291 
292| Tool | Best For | MCP | Guide |
293|------|----------|:---:|-------|
294| **Customer.io** | Behavior-based automation | - | [customer-io.md](../../tools/integrations/customer-io.md) |
295| **Mailchimp** | SMB email marketing | ✓ | [mailchimp.md](../../tools/integrations/mailchimp.md) |
296| **Nitrosend** | AI-native email (sequences via prompts) | ✓ | [nitrosend.md](../../tools/integrations/nitrosend.md) |
297| **Resend** | Developer-friendly transactional | ✓ | [resend.md](../../tools/integrations/resend.md) |
298| **SendGrid** | Transactional email at scale | - | [sendgrid.md](../../tools/integrations/sendgrid.md) |
299| **Kit** | Creator/newsletter focused | - | [kit.md](../../tools/integrations/kit.md) |
300 
301---
302 
303## Related Skills
304 
305- **lead-magnets**: For planning lead magnets that feed into nurture sequences
306- **churn-prevention**: For cancel flows, save offers, and dunning strategy (email supports this)
307- **onboarding**: For in-app onboarding (email supports this)
308- **copywriting**: For landing pages emails link to
309- **ab-testing**: For testing email elements
310- **popups**: For email capture popups
311- **revops**: For lifecycle stages that trigger email sequences
312 
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 →
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 starsSkillSays 'newsletter', 'email newsletter', 'weekly digest'Newsletter: Writing email newsletter edition...cwinvestments/memstack · by cwinvestmentsUse this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.★ 423 GitHub starsSkillWrite a signal-based cold outreach email that earns a replySignal-Based Cold Email (2026 benchmarks)kami-community/kami · by kami-communityWrite a signal-based cold outreach email that earns a reply. Use when drafting outbound/SDR email to a prospect with a known recent signal (funding, hiring, exec hire, launch, community post).★ 64 GitHub starsSkillHostinger Reach API for contact management, segmentationHostinger Reach (Email Marketing)hostinger/hostinger-agent-skills · by hostingerHostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.★ 23 GitHub starsMCPExpert email marketing strategist for CRM-driven campaignsmsitarzewski/agency-agents · by msitarzewskiExpert email marketing strategist for CRM-driven campaigns, lifecycle automation, segmentation architecture, and deliverability. Designs sequences (welcome, nurture, reactivation, win-back, review, referral) grounded in 2025-2026 benchmarks, AI-driven personalization, and post-Apple MPP measurement.★ 154k GitHub starsSkillWrite B2B cold emails and follow-up sequences that getCold Email Writingcoreyhaines31/marketingskills · by coreyhaines31Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.★ 51.1k 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