Onboards CRO

Onboarding CRO

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

Onboarding CRO cover

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value.

---
name: onboarding
description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
metadata:
  version: 2.0.1
---

# Onboarding CRO

You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.

## 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 providing recommendations, understand:

Overview

You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.

Manual install (npx, ZIP)
Claude Codenpx skills add coreyhaines31/marketingskills --skill onboarding -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/onboarding
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/4131253e771327d72353/onboarding.zip" -OutFile "$env:TEMP\onboarding.zip"; Expand-Archive "$env:TEMP\onboarding.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.md10.0 KB
  • evals/1 file · 7.8 KB
  • references/3 files · 13.9 KB
Read the files here
coreyhaines31/5b2c0005 files
SKILL.md
Show the full text262 lines

Onboarding CRO

You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.

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 providing recommendations, understand:

  1. Product Context - What type of product? B2B or B2C? Core value proposition?
  2. Activation Definition - What's the "aha moment"? What action indicates a user "gets it"?
  3. Current State - What happens after signup? Where do users drop off?

Core Principles

1. Time-to-Value Is Everything

Remove every step between signup and experiencing core value. Design the Minimum Path to Value (MPTV) — the least number of steps to experience enough value to make a confident decision (see references/minimum-path-to-value.md).

2. One Goal Per Session

Focus first session on one successful outcome. Save advanced features for later.

3. Do, Don't Show

Interactive > Tutorial. Doing the thing > Learning about the thing.

4. Progress Creates Motivation

Show advancement. Celebrate completions. Make the path visible. (See onboarding psychology below for the mechanisms.)


Onboarding Psychology

The principles that make progress mechanics, checklists, and prompts actually work:

  • Endowed Progress Effect — people finish faster when progress is already started for them. A checklist that opens at "20% done" (a step pre-completed on their behalf) drives roughly +40% completion vs. starting at 0%. Give users a head start, don't make them start from nothing.
  • Peak-End Rule — users remember an experience by its most intense moment (the peak) and its end, not the average. Engineer a clear high point (a win, a wow, a celebration) and end each session on a positive note.
  • Goldilocks Rule — motivation peaks when a task is neither too easy nor too hard, but just right on the edge of ability. Tune early steps so they're achievable but not trivial.
  • BJ Fogg Behavior Model — a behavior happens only when Motivation × Ability × Prompt converge at the same moment. If a step isn't happening, one of the three is missing: raise motivation, make it easier (Ability), or add a better-timed Prompt.
  • Mario Kart boosters & blockers (Ramli John) — treat onboarding like a race track. Add boosters (accelerants: pre-filled data, templates, quick wins, celebrations) and remove blockers (friction: required fields, dead ends, confusing empty states). Speed users toward value and clear obstacles from the lane.

Onboarding Toolkit (10 Components)

The components you assemble an onboarding experience from. Use the fewest that reach value:

Component Purpose
Welcome forms Capture role/goal to personalize the path (keep short — Hick's Law)
Initial screens First-run screens that orient and point to one clear action
Drip emails Multi-touch nurture — one concept per email, don't overload
Skippable tutorials Optional guidance users can bypass — never trap them
Videos Show complex workflows visually
Docs / help center Self-serve reference for when users get stuck
Onboarding calls Human touch for complex or high-value accounts
Data inputs Getting the user's real data in so value feels "real"
Checklists Ordered, value-first steps with visible progress (see below)
Empty states Guided first-action opportunities, not dead ends (see below)

Defining Activation

Judge activation by lead→customer conversion + 90-day retention, not lead volume. More signups mean nothing if they don't convert and stick.

Choose an activation model (freemium, free trial, paid trial, money-back, consultation) before designing the flow — the model shapes the whole onboarding path. See references/activation-models.md for the 5 models, the credit-card tradeoff, Model-Market Fit, and the Evernote-vs-Notion parable.

Find Your Aha Moment

The action that correlates most strongly with retention:

  • What do retained users do that churned users don't?
  • What's the earliest indicator of future engagement?

Examples by product type:

  • Project management: Create first project + add team member
  • Analytics: Install tracking + see first report
  • Design tool: Create first design + export/share
  • Marketplace: Complete first transaction
Activation Metrics
  • % of signups who reach activation
  • Time to activation
  • Steps to activation
  • Activation by cohort/source

Onboarding Flow Design

Immediate Post-Signup (First 30 Seconds)
Approach Best For Risk
Product-first Simple products, B2C, mobile Blank slate overwhelm
Guided setup Products needing personalization Adds friction before value
Value-first Products with demo data May not feel "real"

Whatever you choose:

  • Clear single next action
  • No dead ends
  • Progress indication if multi-step
Onboarding Checklist Pattern

When to use:

  • Multiple setup steps required
  • Product has several features to discover
  • Self-serve B2B products

Best practices:

  • 3-7 items (not overwhelming)
  • Order by value (most impactful first)
  • Start with quick wins
  • Progress bar/completion %
  • Celebration on completion
  • Dismiss option (don't trap users)
Empty States

Empty states are onboarding opportunities, not dead ends.

Good empty state:

  • Explains what this area is for
  • Shows what it looks like with data
  • Clear primary action to add first item
  • Optional: Pre-populate with example data
Tooltips and Guided Tours

When to use: Complex UI, features that aren't self-evident, power features users might miss

Best practices:

  • Max 3-5 steps per tour
  • Dismissable at any time
  • Don't repeat for returning users

Multi-Channel Onboarding

Email + In-App Coordination

Trigger-based emails:

  • Welcome email (immediate)
  • Incomplete onboarding (24h, 72h)
  • Activation achieved (celebration + next step)
  • Feature discovery (days 3, 7, 14)

Email should:

  • Reinforce in-app actions, not duplicate them
  • Drive back to product with specific CTA
  • Be personalized based on actions taken

Handling Stalled Users

Detection

Define "stalled" criteria (X days inactive, incomplete setup)

Re-engagement Tactics
  1. Email sequence - Reminder of value, address blockers, offer help
  2. In-app recovery - Welcome back, pick up where left off
  3. Human touch - For high-value accounts, personal outreach

Measurement

Key Metrics
Metric Description
Activation rate % reaching activation event
Time to activation How long to first value
Onboarding completion % completing setup
Day 1/7/30 retention Return rate by timeframe
Funnel Analysis

Track drop-off at each step:

Signup → Step 1 → Step 2 → Activation → Retention
100%      80%       60%       40%         25%

Identify biggest drops and focus there.


Output Format

Onboarding Audit

For each issue: Finding → Impact → Recommendation → Priority

Onboarding Flow Design
  • Activation goal
  • Step-by-step flow
  • Checklist items (if applicable)
  • Empty state copy
  • Email sequence triggers
  • Metrics plan

Common Patterns by Product Type

Product Type Key Steps
B2B SaaS Setup wizard → First value action → Team invite → Deep setup
Marketplace Complete profile → Browse → First transaction → Repeat loop
Mobile App Permissions → Quick win → Push setup → Habit loop
Content Platform Follow/customize → Consume → Create → Engage

Experiment Ideas

When recommending experiments, consider tests for:

  • Flow simplification (step count, ordering)
  • Progress and motivation mechanics
  • Personalization by role or goal
  • Support and help availability

For comprehensive experiment ideas: See references/experiments.md


References


Task-Specific Questions

  1. What action most correlates with retention?
  2. What happens immediately after signup?
  3. Where do users currently drop off?
  4. What's your activation rate target?
  5. Do you have cohort analysis on successful vs. churned users?

  • signup: For optimizing the signup before onboarding
  • emails: For onboarding email series
  • paywalls: For converting to paid during/after onboarding
  • ab-testing: For testing onboarding changes
1---
2name: onboarding
3description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.
4metadata:
5 version: 2.0.1
6---
7 
8# Onboarding CRO
9 
10You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention.
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 providing recommendations, understand:
18 
191. **Product Context** - What type of product? B2B or B2C? Core value proposition?
202. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"?
213. **Current State** - What happens after signup? Where do users drop off?
22 
23---
24 
25## Core Principles
26 
27### 1. Time-to-Value Is Everything
28Remove every step between signup and experiencing core value. Design the **Minimum Path to Value (MPTV)** — the least number of steps to experience enough value to make a confident decision (see [references/minimum-path-to-value.md](references/minimum-path-to-value.md)).
29 
30### 2. One Goal Per Session
31Focus first session on one successful outcome. Save advanced features for later.
32 
33### 3. Do, Don't Show
34Interactive > Tutorial. Doing the thing > Learning about the thing.
35 
36### 4. Progress Creates Motivation
37Show advancement. Celebrate completions. Make the path visible. (See onboarding psychology below for the mechanisms.)
38 
39---
40 
41## Onboarding Psychology
42 
43The principles that make progress mechanics, checklists, and prompts actually work:
44 
45- **Endowed Progress Effect** — people finish faster when progress is already started for them. A checklist that opens at "20% done" (a step pre-completed on their behalf) drives roughly **+40% completion** vs. starting at 0%. Give users a head start, don't make them start from nothing.
46- **Peak-End Rule** — users remember an experience by its most intense moment (the *peak*) and its *end*, not the average. Engineer a clear high point (a win, a wow, a celebration) and end each session on a positive note.
47- **Goldilocks Rule** — motivation peaks when a task is neither too easy nor too hard, but *just right* on the edge of ability. Tune early steps so they're achievable but not trivial.
48- **BJ Fogg Behavior Model** — a behavior happens only when **Motivation × Ability × Prompt** converge at the same moment. If a step isn't happening, one of the three is missing: raise motivation, make it easier (Ability), or add a better-timed Prompt.
49- **Mario Kart boosters & blockers** (Ramli John) — treat onboarding like a race track. Add **boosters** (accelerants: pre-filled data, templates, quick wins, celebrations) and remove **blockers** (friction: required fields, dead ends, confusing empty states). Speed users toward value and clear obstacles from the lane.
50 
51## Onboarding Toolkit (10 Components)
52 
53The components you assemble an onboarding experience from. Use the fewest that reach value:
54 
55| Component | Purpose |
56|-----------|---------|
57| Welcome forms | Capture role/goal to personalize the path (keep short — Hick's Law) |
58| Initial screens | First-run screens that orient and point to one clear action |
59| Drip emails | Multi-touch nurture — **one concept per email**, don't overload |
60| Skippable tutorials | Optional guidance users can bypass — never trap them |
61| Videos | Show complex workflows visually |
62| Docs / help center | Self-serve reference for when users get stuck |
63| Onboarding calls | Human touch for complex or high-value accounts |
64| Data inputs | Getting the user's real data in so value feels "real" |
65| Checklists | Ordered, value-first steps with visible progress (see below) |
66| Empty states | Guided first-action opportunities, not dead ends (see below) |
67 
68---
69 
70## Defining Activation
71 
72**Judge activation by lead→customer conversion + 90-day retention, not lead volume.** More signups mean nothing if they don't convert and stick.
73 
74Choose an **activation model** (freemium, free trial, paid trial, money-back, consultation) before designing the flow — the model shapes the whole onboarding path. See [references/activation-models.md](references/activation-models.md) for the 5 models, the credit-card tradeoff, Model-Market Fit, and the Evernote-vs-Notion parable.
75 
76### Find Your Aha Moment
77 
78The action that correlates most strongly with retention:
79- What do retained users do that churned users don't?
80- What's the earliest indicator of future engagement?
81 
82**Examples by product type:**
83- Project management: Create first project + add team member
84- Analytics: Install tracking + see first report
85- Design tool: Create first design + export/share
86- Marketplace: Complete first transaction
87 
88### Activation Metrics
89- % of signups who reach activation
90- Time to activation
91- Steps to activation
92- Activation by cohort/source
93 
94---
95 
96## Onboarding Flow Design
97 
98### Immediate Post-Signup (First 30 Seconds)
99 
100| Approach | Best For | Risk |
101|----------|----------|------|
102| Product-first | Simple products, B2C, mobile | Blank slate overwhelm |
103| Guided setup | Products needing personalization | Adds friction before value |
104| Value-first | Products with demo data | May not feel "real" |
105 
106**Whatever you choose:**
107- Clear single next action
108- No dead ends
109- Progress indication if multi-step
110 
111### Onboarding Checklist Pattern
112 
113**When to use:**
114- Multiple setup steps required
115- Product has several features to discover
116- Self-serve B2B products
117 
118**Best practices:**
119- 3-7 items (not overwhelming)
120- Order by value (most impactful first)
121- Start with quick wins
122- Progress bar/completion %
123- Celebration on completion
124- Dismiss option (don't trap users)
125 
126### Empty States
127 
128Empty states are onboarding opportunities, not dead ends.
129 
130**Good empty state:**
131- Explains what this area is for
132- Shows what it looks like with data
133- Clear primary action to add first item
134- Optional: Pre-populate with example data
135 
136### Tooltips and Guided Tours
137 
138**When to use:** Complex UI, features that aren't self-evident, power features users might miss
139 
140**Best practices:**
141- Max 3-5 steps per tour
142- Dismissable at any time
143- Don't repeat for returning users
144 
145---
146 
147## Multi-Channel Onboarding
148 
149### Email + In-App Coordination
150 
151**Trigger-based emails:**
152- Welcome email (immediate)
153- Incomplete onboarding (24h, 72h)
154- Activation achieved (celebration + next step)
155- Feature discovery (days 3, 7, 14)
156 
157**Email should:**
158- Reinforce in-app actions, not duplicate them
159- Drive back to product with specific CTA
160- Be personalized based on actions taken
161 
162---
163 
164## Handling Stalled Users
165 
166### Detection
167Define "stalled" criteria (X days inactive, incomplete setup)
168 
169### Re-engagement Tactics
170 
1711. **Email sequence** - Reminder of value, address blockers, offer help
1722. **In-app recovery** - Welcome back, pick up where left off
1733. **Human touch** - For high-value accounts, personal outreach
174 
175---
176 
177## Measurement
178 
179### Key Metrics
180 
181| Metric | Description |
182|--------|-------------|
183| Activation rate | % reaching activation event |
184| Time to activation | How long to first value |
185| Onboarding completion | % completing setup |
186| Day 1/7/30 retention | Return rate by timeframe |
187 
188### Funnel Analysis
189 
190Track drop-off at each step:
191```
192Signup → Step 1 → Step 2 → Activation → Retention
193100% 80% 60% 40% 25%
194```
195 
196Identify biggest drops and focus there.
197 
198---
199 
200## Output Format
201 
202### Onboarding Audit
203For each issue: Finding → Impact → Recommendation → Priority
204 
205### Onboarding Flow Design
206- Activation goal
207- Step-by-step flow
208- Checklist items (if applicable)
209- Empty state copy
210- Email sequence triggers
211- Metrics plan
212 
213---
214 
215## Common Patterns by Product Type
216 
217| Product Type | Key Steps |
218|--------------|-----------|
219| B2B SaaS | Setup wizard → First value action → Team invite → Deep setup |
220| Marketplace | Complete profile → Browse → First transaction → Repeat loop |
221| Mobile App | Permissions → Quick win → Push setup → Habit loop |
222| Content Platform | Follow/customize → Consume → Create → Engage |
223 
224---
225 
226## Experiment Ideas
227 
228When recommending experiments, consider tests for:
229- Flow simplification (step count, ordering)
230- Progress and motivation mechanics
231- Personalization by role or goal
232- Support and help availability
233 
234**For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md)
235 
236---
237 
238## References
239 
240- **[references/minimum-path-to-value.md](references/minimum-path-to-value.md)** — MPTV, Hick's Law, the inventory→remove→reconstruct process, abandonment benchmarks (40–60% after one session; 75–80% within day one), and patterns (Stripe, Calendly, Notion).
241- **[references/activation-models.md](references/activation-models.md)** — the 5 activation models, credit-card tradeoff, Model-Market Fit, Evernote vs. Notion.
242- **[references/experiments.md](references/experiments.md)** — comprehensive A/B test and experiment ideas.
243 
244---
245 
246## Task-Specific Questions
247 
2481. What action most correlates with retention?
2492. What happens immediately after signup?
2503. Where do users currently drop off?
2514. What's your activation rate target?
2525. Do you have cohort analysis on successful vs. churned users?
253 
254---
255 
256## Related Skills
257 
258- **signup**: For optimizing the signup before onboarding
259- **emails**: For onboarding email series
260- **paywalls**: For converting to paid during/after onboarding
261- **ab-testing**: For testing onboarding changes
262 
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 →
SkillOnboards CROOnboarding CROdavila7/claude-code-templates · by davila7When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.★ 32.3k GitHub starsSkillOnboards CROOnboarding CROalirezarezvani/claude-skills · by alirezarezvaniWhen the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.★ 26.3k GitHub starsMCPYou need to assess customer healthCustomer success managerVoltAgent/awesome-claude-code-subagents · by VoltAgentUse this agent when you need to assess customer health, develop retention strategies, identify upsell opportunities, or maximize customer lifetime value. Invoke this agent for account health analysis, churn prevention, product adoption optimization, and customer success planning.★ 25.2k GitHub starsSkillUnderstanding buyer psychology is the single most importantBuyer segments in the technology adoption lifecyclewondelai/skills · by wondelaiUnderstanding buyer psychology is the single most important factor in technology marketing. Each segment in the adoption lifecycle has…★ 2.2k GitHub starsSkillBuild a joint customer success plan for a specific accountCustomer Success Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a joint customer success plan for a specific account. Use when asked to create a success plan, joint success plan, mutual action plan, or customer onboarding plan. Produces a structured success plan with business goals, milestones, success metrics, ownership, and a 90-180 day roadmap.★ 1.4k GitHub starsSkillGoals vs actuals, wins, root causes, ROI, next-quarter plan/digital-marketing-pro:qbr-planindranilbanerjee/digital-marketing-pro · by indranilbanerjeePrepare a QBR package: goals vs actuals, wins, root causes, ROI, next-quarter plan. "prepare the QBR"★ 866 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