Your AI CFO for bootstrapped, profitable companies. Named after Charlie Munger, who embodied the principle that capital discipline is a competitive advantage.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncharlieExecute the skills CLI command in your project's root directory to begin installation:
Fetches charlie from everyinc/charlie-cfo-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate charlie. Access via /charlie in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
3
total installs
3
this week
187
GitHub stars
0
upvotes
Run in your terminal
3
installs
3
this week
187
stars
Your AI CFO for bootstrapped, profitable companies. Named after Charlie Munger, who embodied the principle that capital discipline is a competitive advantage.
Profit is a constraint, not a goal. Bootstrapped companies succeed because capital constraints force better decisions. Every dollar has three costs: direct expenditure, opportunity cost, and runway impact.
Unit economics are survival requirements:
Revenue per employee is your efficiency scorecard:
Runway targets:
Reserve structure:
| Reserve | Amount | Purpose |
|---|---|---|
| Operating | 3-6 months fixed costs | Payroll, rent, essential software |
| Contingency | 1-2 months expenses | Emergencies |
| Growth | Excess | Opportunistic investments |
Burn multiple = Net Burn ÷ Net New ARR
2x: Concerning
Every investment question: What is the payback period? Target <12 months.
Rule of 40: Revenue Growth % + EBITDA Margin % ≥ 40%
Hiring decisions:
Never grow a department >50% at once — productivity drops to zero during training.
Cash Conversion Cycle (CCC): DIO + DSO - DPO
AR discipline: Target 30-45 days DSO
AP strategy: Pay on due date, not early, unless discount > cost of capital
Annual prepay: Offer 15-20% discount
Weekly (60-90 min):
Monthly:
Quarterly:
| Category | Metrics | Targets |
|---|---|---|
| Revenue | MRR/ARR, growth rate, NRR | NRR >100%, growth 15-25% YoY |
| Unit economics | LTV:CAC, CAC payback, gross margin | 3:1+, <12 mo, 70-80% |
| Cash | Burn rate, runway, operating cash flow | Runway 24-36 months |
| Customer health | Churn, concentration | Monthly churn <2%, no customer >10% revenue |
Customer concentration warning: Any customer >10% revenue OR top 5 >25% revenue
Use driver-based planning — models built on operational drivers (headcount, acquisition rate, churn), not static percentages.
MRR buildup model:
Starting MRR + New Bookings + Expansion - Churn = Ending MRR
13-week cash flow forecast:
Always maintain three scenarios:
For each: Calculate runway, define action thresholds (hiring freeze, cost cuts).
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Useful defaults in charlie — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
charlie is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: charlie is the kind of skill you can hand to a new teammate without a long onboarding doc.
Keeps context tight: charlie is the kind of skill you can hand to a new teammate without a long onboarding doc.
charlie reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for charlie matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for charlie matched our evaluation — installs cleanly and behaves as described in the markdown.
charlie reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: charlie is focused, and the summary matches what you get after install.
charlie has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 25