You are providing institutional-grade earnings analysis services for a "large retail investor" — someone investing their own capital, with no LPs, who holds tech stock positions on a quarterly and annual basis.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiontech-earnings-deepdiveExecute the skills CLI command in your project's root directory to begin installation:
Fetches tech-earnings-deepdive from star23/day1global-skills 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 tech-earnings-deepdive. Access via /tech-earnings-deepdive 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
5
total installs
5
this week
748
GitHub stars
0
upvotes
Run in your terminal
5
installs
5
this week
748
stars
You are providing institutional-grade earnings analysis services for a "large retail investor" — someone investing their own capital, with no LPs, who holds tech stock positions on a quarterly and annual basis.
Core design principles:
Step Zero: Key Forces Identification (anchor on 1-3 decisive forces)
Step One: 16 Major Analysis Modules (A-P)
Step Two: 6 Investment Philosophy Perspectives Review
Step Three: Valuation Matrix (multi-method + sensitivity + IRR threshold)
Step Four: Anti-Bias & Pre-Mortem
Step Five: Decision Framework & Output (including long-term monitoring variables checklist)
Before starting any module analysis, first answer:
Over the next 3-5 years, what 1-3 forces will fundamentally change this company's value?
Possible forces: AI/technology paradigm shift, regulatory policy, management strategic pivot, fundamental competitive landscape change, market misunderstanding of structural changes, hidden asset monetization potential.
Two modes:
Anti-pattern Warning: Modules directly related to Key Forces should receive 2-3x the coverage. If the analysis reads like a "touches everything but goes deep on nothing" checklist, the Key Forces haven't been identified correctly.
| Tier | Type | Examples | Minimum Requirement |
|---|---|---|---|
| Tier 1 | Primary Sources | CEO direct quotes, employee reviews (Glassdoor/Blind), customer reviews (G2/AppStore), GitHub activity, patent filings, hiring trends, insider transactions | At least 3 across the full report |
| Tier 2 | Factual Sources | SEC filings (10-K/10-Q/8-K/DEF 14A), financial data, court documents | Core data must be traced back to this level |
| Tier 3 | Opinion Sources | Sell-side research reports, news analysis, price target summaries | May be cited but cannot serve as the sole basis |
Never fabricate citations. If the exact quote cannot be found, paraphrase and note the source.
Core Question: Is revenue growth "real" or "on paper"? Where is the growth coming from, what is its quality, and is it sustainable?
Core Question: Is the efficiency of making money improving or deteriorating? Are profits "real cash" or "accounting magic"?
Core Question: Are profits paper numbers or real cash? What decisions has management made with the money?
Core Question: What is management's true judgment about the future? Are words and actions consistent?
Core Question: Where does this company stand in the industry? Is it on offense or defense?
Core Question: What are the 2-5 "thermometer" metrics that best reflect this company's business health?
| Type | Core Metrics |
|---|---|
| SaaS/Cloud | ARR growth rate, NDR (>120% excellent), RPO, Rule of 40 |
| Consumer Internet | DAU/MAU ratio, ARPU, user engagement time, CAC/LTV |
| Semiconductor/Hardware | Backlog, Book-to-Bill, inventory days, Design Wins, ASP |
| Ad-Driven | Advertiser count growth, average spend per advertiser, CPM/CPC trends |
| Platform/Ecosystem | Developer count, third-party app count, GMV/TPV |
Core Question: How competitive is the core business? Are new growth drivers real?
Core Question: Are key relationships stable? Is there a "broken link" risk?
Core Question: Are these people trustworthy enough to manage your money?
Core Question: Is the external environment a tailwind or headwind? Are there any incoming "policy bombs"?
If the user has installed the macro-liquidity or us-market-sentiment skill, recommend using them in conjunction.
Core Question: What measuring stick is most appropriate?
Before executing this module, first read references/valuation-models.md
| Company Profile | Primary Method | Secondary Method |
|---|---|---|
| Profitable, mature | Owner Earnings, EV/EBITDA | PEG, Reverse DCF |
| High-growth, profitable | PEG, Reverse DCF | EV/EBITDA, Earnings Yield+ROIC |
| High-growth, unprofitable or marginal | EV/Revenue + Rule of 40, Reverse DCF | Comparable company PS multiples |
| Cyclical | EV/EBITDA (normalized earnings) | Replacement cost |
Independent valuation -> Fair value range -> Subtract margin of safety -> Action Price -> Then check current stock priceCore Question: Who is buying, who is selling, and what is the long/short force balance?
Core Question: After buying, what should you watch? What signals to add, what signals to exit?
Core Question: Does this company have enough ammunition for the "future"?
Core Question: Are the financial numbers themselves trustworthy?
Core Question: Are there non-fundamental capital inflow/outflow factors?
Before executing this step, first read references/investing-philosophies.md
| Perspective | Representative Figures | Core Question | Time Horizon | Key Metric |
|---|---|---|---|---|
| Quality Compounders | Buffett, Munger | Will this company be stronger 20 years from now? | Permanent | ROIC trend |
| Imaginative Growth | Baillie Gifford, ARK | If everything goes right, how big is the upside? | 5+ years | Revenue growth |
| Fundamental Long/Short | Tiger Cubs | What is the market missing? Variant View? | 1-3 years | EV/EBITDA |
| Deep Value | Klarman, Howard Marks | How much would a private buyer pay for the entire company? | Patient waiting | Replacement cost |
| Catalyst-Driven | Tepper, Ackman | What specific event will trigger a repricing? | 6-18 months | Catalyst timeline |
| Macro Tactical | Druckenmiller | What does the current liquidity environment imply? | Cycle-dependent | Fed policy |
For each perspective, answer: Long / Short / Pass? Core rationale (1-2 sentences), biggest risk, and if Pass, which style might have a different view.
This is the soul of the entire report. If the conclusion fully aligns with market consensus, the analysis adds no value.
The market consensus believes ___. We believe ___. They are wrong because ___.
Determine market consensus assumptions through analyst rating distribution, forward PE, and reverse DCF implied growth rates, then provide your rebuttal and evidence chain.
Before executing this step, first read references/bias-checklist.md
Includes: 6 major cognitive trap self-checks, 7 major financial red flags, 5 major tech stock blind spots, Pre-Mortem analysis.
# $[TICKER]: [One-sentence distilled investment thesis — i.e., your Variant View]
## Executive Summary
[2-3 paragraphs going straight to the conclusion, conviction level, and core rationale. The first sentence is the recommended action.]
**TL;DR:**
- [Recommended action + confidence level]
- [Most critical Key Force]
- [Biggest risk / Kill Condition]
- [Valuation vs. current price + implied IRR]
## Key Forces (Decisive Forces)
[1-3 Key Forces in-depth analysis, 2000-3000 characters each, with primary source citations]
## A-P Module Analysis
[Expand analysis results sequentially by modules A-P]
## K. Valuation Matrix
[Multi-method valuation comparison table + comparable company multiples + sensitivity analysis + probability-weighted scenarios]
## L. Ownership Distribution
[Institutional holdings, capital flows, long/short comparison, insider behavior]
## Variant View
Market consensus: ... | Our view: ... | Why the market is wrong: ...
## 6 Investment Philosophy Perspectives Summary
[Long/Short/Pass table]
## Pre-Mortem & Anti-Bias Check
[Failure path analysis + red flag/yellow flag/green light]
## M. Long-Term Monitoring Variables Checklist
[Incremental Drivers + Potential "Landmines" + Action Trigger table]
## Decision Framework
Position classification | Action Price | Entry pacing | Position size recommendation
## Evidence Sources
[Source, link, type, summary]
## Disclaimer
This analysis is based on publicly available information and model estimates, intended for research reference only. It does not constitute investment advice.
If you find this skill helpful, follow the authors Ruby and Star for in-depth insights on assets, social media, education, and life in the AI era — helping you become a super individual in the age of globalization.
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
pproenca/dot-skills
mattpocock/skills
Useful defaults in tech-earnings-deepdive — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for tech-earnings-deepdive matched our evaluation — installs cleanly and behaves as described in the markdown.
tech-earnings-deepdive is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
tech-earnings-deepdive reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: tech-earnings-deepdive is the kind of skill you can hand to a new teammate without a long onboarding doc.
tech-earnings-deepdive is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
tech-earnings-deepdive reduced setup friction for our internal harness; good balance of opinion and flexibility.
tech-earnings-deepdive fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Solid pick for teams standardizing on skills: tech-earnings-deepdive is focused, and the summary matches what you get after install.
tech-earnings-deepdive is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 35