startup-analysis
Analyze a startup from three perspectives — VC investor, job applicant, and CEO/founder — covering market, traction, unit economics, team, defensibility, runway, equity value, culture, and competitive position, with a verdict for each. Use this skill whenever the user wants to evaluate a startup or private tech company: due diligence, whether to invest in it or join it, weighing a startup job offer, company health, outlook, or competitive position, or open-ended asks such as "what do you think of [company]" or "research [company] for me".
- Installs
- 3K
- Last 24h
- +54
- Trending rank
- #3199
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/himself65/finance-skills --skill startup-analysis- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads startup-analysis automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Startup Analysis
Produces a multi-perspective analysis of a startup, examining it through three lenses that each reveal different aspects of company health and potential:
- VC Investor Lens — Is this a good investment? Market size, unit economics, growth trajectory, team quality, defensibility
- Job Applicant Lens — Should I work here? Equity value, runway risk, culture signals, career growth, compensation fairness
- CEO/Founder Lens — How healthy is this company? Product-market fit, burn efficiency, competitive moat, organizational health
Each perspective surfaces insights the others miss. A company can be a great investment but a terrible place to work (or vice versa). The goal is to give the user a 360-degree view so they can make informed decisions.
Step 1: Gather Information
Before analyzing, collect as much public information as possible about the startup. Use web search, the company's website, Crunchbase data, press coverage, and any other available sources.
Key data to gather:
| Category | What to find |
|---|---|
| Basics | Founded year, HQ location, employee count, what the product does |
| Funding | Total raised, last round (size, date, valuation if known), key investors |
| Product | What they sell, who buys it, pricing model, key competitors |
| Traction | Users, revenue (if public), growth signals, notable customers |
| Team | Founders' backgrounds, key hires, LinkedIn headcount trends |
| Market | Industry, market size estimates, tailwinds/headwinds |
| News | Recent press, product launches, partnerships, layoffs, pivots |
If certain data isn't publicly available (e.g., revenue for private companies), note the gap and infer what you can from indirect signals (hiring pace, customer logos, web traffic proxies, job postings).
When information is insufficient
Many startups — especially early-stage or niche ones — have limited public presence. If web search does not return enough information to produce a meaningful analysis (e.g., you can't determine what the company does, who founded it, or how it's funded), ask the user to provide the company's website URL before proceeding. The company website is often the single most information-dense source, and reading it directly (about page, pricing page, team page, blog) can fill most gaps.
You can also ask the user for:
- The company's website or landing page URL
- A Crunchbase, LinkedIn, or PitchBook link
- Any pitch deck, job listing, or press article they have
- Specific context they already know (e.g., "they just raised a Series A from Sequoia")
It is better to ask for a URL and produce an accurate analysis than to guess and produce a misleading one.
Step 2: Determine Which Perspectives to Cover
By default, produce all three perspectives. If the user specifies a particular angle (e.g., "I'm considering joining them" or "should I invest"), emphasize that perspective but still include the others as context — they often reveal relevant information.
| User's situation | Primary perspective | Still include |
|---|---|---|
| Considering investing | VC Investor | Job Applicant (talent signal), CEO (operational health) |
| Considering a job offer | Job Applicant | VC Investor (funding runway), CEO (strategic direction) |
| Running the company / advisory | CEO/Founder | VC Investor (how investors see you), Job Applicant (talent attractiveness) |
| General curiosity / research | All equally | — |
Step 3: Analyze from Each Perspective
Read the relevant reference files for the detailed framework for each perspective. These contain the specific criteria, metrics, and red/green flags to evaluate.
VC Investor Analysis
Read references/vc-framework.md for the full evaluation framework.
Core areas to assess:
- Market opportunity — TAM/SAM/SOM, market timing, secular trends
- Product & traction — Product-market fit signals, growth metrics, retention
- Unit economics — CAC, LTV, margins, burn multiple, path to profitability
- Team — Founder-market fit, technical depth, hiring ability
- Defensibility — Moats (network effects, switching costs, data, brand, regulatory)
- Deal terms context — Stage-appropriate valuation, comparable exits
Produce a clear Investment Thesis (bull case) and Key Risks (bear case). End with a verdict: Strong Pass / Lean Pass / Lean Invest / Strong Invest, with reasoning.
Job Applicant Analysis
Read references/job-applicant-framework.md for the full evaluation framework.
Core areas to assess:
- Financial stability — Runway, burn rate, funding trajectory, revenue health
- Equity value — Option/equity package analysis, dilution risk, liquidation preferences, realistic exit scenarios
- Career growth — Role scope, learning opportunity, resume value, mentorship
- Culture & work-life — Glassdoor signals, employee tenure data, leadership style
- Product & market risk — Is PMF real? What happens if the startup fails?
- Red flags — High turnover, constant pivots, vague metrics, founders cashing out
Produce a clear Why Join (pros) and Watch Out For (risks). End with a verdict: Strong Pass / Lean Pass / Lean Join / Strong Join, with reasoning.
CEO/Founder Analysis
Read references/ceo-framework.md for the full evaluation framework.
Core areas to assess:
- Product-market fit — Retention curves, organic growth, Sean Ellis test proxy
- Growth efficiency — Burn multiple, CAC payback, magic number
- Competitive position — Moat strength, competitive dynamics, market share trajectory
- Organizational health — Hiring pipeline, attrition, team capability gaps
- Fundraising readiness — Metrics vs. benchmarks for next round, investor narrative
- Strategic risks — Platform dependency, customer concentration, regulatory exposure
Produce a clear Strengths to Double Down On and Urgent Areas to Address. End with a health grade: Critical / Struggling / Stable / Strong / Exceptional, with reasoning.
Step 4: Synthesize Cross-Perspective Insights
After the three analyses, add a synthesis section that highlights:
- Where perspectives agree — If all three lenses flag the same strength or weakness, it's probably real
- Where perspectives diverge — A company can be VC-attractive (huge market) but employee-risky (high burn, low runway). Call these out.
- The bottom line — One paragraph summary: what kind of company is this, what's its most likely trajectory, and what should the user do based on their stated (or implied) situation
Step 5: Present the Report
Write it as a scannable report titled [Company Name] — Startup Analysis:
- Summary — a short overview that states the three verdicts up front.
- One section per perspective, in the order that fits the user's situation from Step 2. Each covers the core areas from Step 3 with the evidence behind every judgment, and ends with its verdict on the scale defined there — Investment Verdict (Strong Pass / Lean Pass / Lean Invest / Strong Invest), Employment Verdict (Strong Pass / Lean Pass / Lean Join / Strong Join), or Health Grade (Critical / Struggling / Stable / Strong / Exceptional) — followed by the reasoning.
- Cross-perspective synthesis — where the lenses agree, where they diverge, and the bottom line.
Scale each section to the evidence: where financials or other areas are opaque, say so in a line and spend the space on what's observable, rather than filling a heading for its own sake. Don't fabricate metrics; make informed inferences and state your confidence level.
Reference Files
references/vc-framework.md— VC due diligence checklist with metrics, benchmarks, and red/green flagsreferences/job-applicant-framework.md— Job seeker evaluation framework with equity analysis and culture assessmentreferences/ceo-framework.md— CEO self-assessment framework with operational metrics and strategic analysis
Read these when you need the detailed criteria and benchmarks for each perspective.
FAQ
What does the startup-analysis skill do?
Analyze a startup from three perspectives — VC investor, job applicant, and CEO/founder — covering market, traction, unit economics, team, defensibility, runway, equity value, culture, and competitive position, with a verdict for each. Use this skill whenever the user wants to evaluate a startup or private tech company: due diligence, whether to invest in it or join it, weighing a startup job offer, company health, outlook, or competitive position, or open-ended asks such as "what do you think of [company]" or "research [company] for me".
How do I install startup-analysis?
Run npx skills add https://github.com/himself65/finance-skills --skill startup-analysis in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/startup-analysis/ (personal) or .claude/skills/startup-analysis/ (project).
Which AI agents can use startup-analysis?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is startup-analysis safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains startup-analysis?
It is published by himself65 in himself65/finance-skills. It has 3,011 recorded installs.
More from himself65/finance-skills
yfinance-data
himself65/finance-skills
Fetch financial and market data with the yfinance Python library (Yahoo Finance). Use this skill whenever the user wants stock data: current quotes and price history, financial statements (income statement, balance sheet, cash flow), options chains, dividends and splits, earnings and analyst estimates, price targets and ratings, institutional and insider holdings, news, multi-ticker comparisons, stock screens, or sector and industry data. Use it even when the user gives only a ticker symbol (AAPL, MSFT, TSLA) and the intent has to be inferred. For earnings previews or recaps, estimate revisions, valuation, correlation, liquidity, or ETF premium analysis, prefer the dedicated skill.
stock-correlation
himself65/finance-skills
Analyze how stocks move together using Yahoo Finance price history (yfinance): find correlated peers for a ticker, measure correlation, beta, and spread between specific tickers, cluster a group into a correlation matrix, and track rolling or regime-dependent correlation. Use this skill whenever the user asks what moves with a stock, what else drops when it drops, related tickers or sympathy plays, sector or supply-chain peers, pair trading or hedging pairs, beta or relative performance, correlation matrices, co-movement, or rolling/realized correlation — including well-known pairs like AMD/NVDA, GOOGL/AVGO, or LITE/COHR. With a single ticker, assume the user wants its correlated peers.
options-payoff
himself65/finance-skills
Render an interactive options payoff chart — expiry P&L plus Black-Scholes theoretical value — with sliders for strikes, premium, IV, DTE, and spot. Use this skill whenever the user describes or shares an options position or strategy and wants to see how it makes or loses money: vertical, calendar, diagonal, or ratio spreads, butterflies, condors and iron condors, straddles, strangles, covered calls, protective or naked puts, or any multi-leg structure. This includes pasted strikes, premiums, and expiries, requests like "show me the payoff" or "draw the P&L curve", and broker screenshots (IBKR, TastyTrade, Robinhood). Use it even when details are partial — defaults fill the gaps.
earnings-preview
himself65/finance-skills
Build a pre-earnings briefing for a stock from Yahoo Finance data (yfinance): the upcoming report date and timing, consensus EPS and revenue estimates with their range, the beat/miss track record, analyst ratings and price targets, and what to watch in the print. Use this skill whenever the user is preparing for an upcoming earnings report or asks what the street expects — consensus or whisper numbers, EPS expectations, whether a company will beat, an earnings setup, or an earnings-season preview — and whenever a ticker comes up in the context of upcoming earnings, even without the word "preview". For results that are already out, use earnings-recap.
earnings-recap
himself65/finance-skills
Analyze a company's most recent (or a specified past) earnings report from Yahoo Finance data (yfinance): actual vs estimated EPS, surprise size, revenue and margin trends, and the stock's price reaction. Use this skill whenever the user asks how earnings went — beat or miss, earnings surprise, quarterly results, the post-earnings move, or an earnings call recap — including casual references to a past report such as "AMZN reported last night" or "how did they do". For an upcoming report, use earnings-preview.
generative-ui
himself65/finance-skills
Design system and templates for interactive HTML/SVG visuals in Claude and Codex, using an available inline renderer or a standalone HTML file. Use this skill whenever the user wants visual or interactive output rather than plain text or markdown: charts and dashboards, diagrams, flowcharts and architecture drawings, mockups, comparison grids, illustrations, interactive explainers ("explain how X works" with a visual), or tools with sliders, toggles, and live-updating displays — including financial data shown visually and requests phrased as "show me", "visualize", "draw", or "chart this".
Popular business & finance skills
sales-enablement
coreyhaines31/marketingskills
When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure),
revops
coreyhaines31/marketingskills
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.
sales-funnel-blueprint
autonnel/autonnel-skills
Turn an offer into a concrete multi-step sales funnel spec - page-by-page structure, price ladder, copy outline and the metrics each step must hit. Use when asked to build a sales funnel, marketing funnel, landing page flow, lead magnet funnel, webinar funnel, tripwire or VSL funnel, when planning a product launch page flow, or when someone asks "what pages do I need" for selling something online.
pricing
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' 'should I offer a free plan,' 'pricing page teardown,' 'pricing page audit,' 'is my pricing page AI-readable,' or 'can AI read my pricing.' Use this whenever someone is figuring out what to charge, how to structure their plans, or wants to audit a pricing page (for humans and for the AI agents that shortlist tools). For in-app upgrade screens, see paywalls. For offer construction (bonuses, guarantees, value framing, naming) on services/courses/coaching/high-ticket B2B, see offers.
cross-border-ecommerce
nexscope-ai/ecommerce-skills
Cross-border e-commerce expansion advisor. Scores target markets on 8 weighted dimensions (market size, ecommerce penetration, competition, regulatory complexity, logistics infrastructure, payment ecosystem, cultural distance, IP protection), compares 5 fulfillment models with cost and transit data, provides country-by-country tax/duty compliance guides (EU VAT/IOSS, UK VAT, US sales tax, CA GST, AU GST, JP consumption tax), maps local payment preferences by market, and builds a phased expansion roadmap. No API key required.
pricing-strategy
coreyhaines31/marketingskills
When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.