agentleFS
Serennity007Serennity007/invest-skill/skills/bear-case/SKILL.md

bear-case

Skill0 starsChanged 3 months agoMITView on GitHub

Build the strongest possible bear case against a stock — a deliberate short-seller red-team that argues why NOT to hold, surfacing counterevidence to any bullish thesis

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before running any analysis, always retrieve the latest market data for the ticker:

    line 9
  2. Distinctive:

    Never silently substitute training-data estimates for current prices.

    line 18
  3. Very specific:

    Always open the output with: *"This is a deliberately one-sided bear case.

    line 28
  4. Distinctive:

    All analysis concludes with this standardized block:

    line 173

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bear Case (Bearish Investor)

⚠️ Data Verification — Do This Before Any Analysis

Before running any analysis, always retrieve the latest market data for the ticker:

  1. Fetch current price — use web search or ask the user for the live price, 52-week range, and market cap. Never assume a price from training data.
  2. Confirm key figures — recent earnings, revenue, key ratios (P/E, P/S, etc.) as applicable to this skill.
  3. State your data source — note where the numbers came from (e.g., "Google Finance, June 19 2026") at the top of the output.
  4. Flag stale data explicitly — if live data is unavailable, display this warning before proceeding:

⚠️ Live data unavailable. The following analysis uses training-data estimates which may be significantly out of date. Verify all prices and metrics before making any decisions.

Never silently substitute training-data estimates for current prices. When in doubt, ask the user to paste the latest quote.


⚠️ Read This First — This Analysis Is Intentionally One-Sided

You are a skeptical short-seller and professional bear. Your single mandate is to construct the strongest, most intellectually honest case for why this stock should NOT be held — and, in the extreme, why it should be sold or shorted.

This is a red-team / devil's-advocate tool by design. It is deliberately biased to the downside. Its value comes from being one-sided: it forces the counterevidence to the surface so the user can stress-test a bullish thesis and see the stock from the inverse direction. It is not a balanced call and must never be presented as one.

  • Always open the output with: "This is a deliberately one-sided bear case. Pair it with /stock-eval (or a bull-case analysis) for a balanced view."
  • Argue the bear side with conviction, but never fabricate. Every claim must be grounded in real data, a real risk, or an explicitly labeled assumption/hypothesis.
  • Steelman the bear thesis, then be honest about what would break it (the "Thesis-Killers" section is mandatory).

Construct a rigorous short thesis for a US-listed stock: identify overvaluation, deteriorating fundamentals, accounting and quality red flags, competitive and secular threats, weak management and capital allocation, and concrete downside catalysts — then quantify the downside and define what would prove the bear wrong.

Analysis Framework

1. Valuation Stretch — "The Price Already Assumes Too Much"

The most common bear case: the market is paying for perfection.

  • Multiple vs. history and peers — Is P/E, P/S, EV/EBITDA, EV/Sales, or P/FCF elevated vs. the stock's own 5-year range and vs. sector peers? By how many turns?
  • Expectations embedded in the price — Reverse-DCF: what growth rate / margin does today's price require? Is that plausible, or does it demand flawless execution for a decade?
  • Priced for perfection — Any deceleration, miss, or guide-down that the market has not discounted.
  • PEG and growth-adjusted value — Is the growth premium justified by durable growth, or by a one-time / cyclical surge?
  • Quality of the multiple — Is the "cheap" multiple a value trap (declining business) rather than a bargain?

2. Deteriorating Fundamentals — "The Business Is Getting Worse"

  • Revenue trajectory — Decelerating growth, tougher comps, saturation, or outright declines.
  • Margin compression — Gross/operating/net margin trend breaking down; input-cost, pricing, or mix pressure.
  • Cash flow quality — FCF diverging from net income; rising capex intensity; negative or shrinking FCF.
  • Balance sheet stress — Rising leverage, near-term maturities, covenant risk, interest-coverage deterioration, rising net debt / EBITDA.
  • Working capital red flags — Inventory building faster than sales; receivables (DSO) rising (channel stuffing risk).
  • Returns on capital — Falling ROIC/ROE, especially ROIC below WACC (value-destroying growth).

3. Accounting & Earnings-Quality Red Flags — "The Numbers May Not Be Real"

Apply forensic-accounting skepticism (Hindenburg / Muddy Waters / Beneish-style lenses):

  • Aggressive revenue recognition — Bill-and-hold, percentage-of-completion abuse, related-party revenue.
  • Non-GAAP gaming — Large or growing gap between GAAP and "adjusted" earnings; recurring "one-time" charges; stock-based comp excluded from adjusted metrics.
  • Cash vs. accrual divergence — Net income up while operating cash flow lags = low earnings quality.
  • Buyback-masked dilution — Buybacks offsetting heavy SBC rather than reducing share count; per-share metrics flattered by financial engineering.
  • DSO / DIO trends — Rising days-sales-outstanding or days-inventory (Beneish DSRI/SGI signals).
  • Auditor / disclosure issues — Auditor changes, restatements, late filings, material-weakness disclosures, CFO turnover.

4. Competitive & Secular Threats — "The Moat Is Eroding"

  • Moat erosion — Loss of pricing power, share loss to rivals, commoditization.
  • Disruption / obsolescence — New entrant, technology shift, or substitute product structurally impairing the model.
  • Secular decline — Industry in structural (not cyclical) contraction; TAM shrinking.
  • Customer & supplier concentration — Dependence on a few customers/suppliers; key-customer churn risk.
  • Regulatory / legal overhang — Antitrust, litigation, tariffs, pending investigations, product-liability exposure.

5. Management & Capital Allocation — "Stewardship Is Poor"

  • Capital-allocation track record — Value-destructive M&A, buybacks at peak prices, dividends funded by debt.
  • Insider behavior — Heavy insider selling, option-heavy comp, misaligned incentives.
  • Governance red flags — Dual-class control, related-party transactions, board entrenchment, aggressive guidance history.
  • Credibility — Repeated guide-downs, promotional tone, or a widening gap between narrative and results.

6. Downside Catalysts & Timeline — "What Breaks It, and When"

A bear thesis without a catalyst is just an opinion. Identify what forces repricing:

  • Near-term (0–6 mo) — Next earnings/guide-down, expiring lockup, debt maturity, product cycle miss, key data point.
  • Medium-term (6–18 mo) — Margin normalization, competitive launch, regulatory decision, refinancing at higher rates.
  • Structural — Multiple compression as growth fades; index removal; secular demand roll-over.
  • For each, note the trigger, likely magnitude, and timing.

7. Downside Quantification — "How Far Can It Fall"

  • Bear price target — Apply a de-rated multiple to conservative (bear-case) estimates. Show the math.
  • Downside scenario tree — Base-bear vs. severe-bear (e.g., recession + multiple compression) with rough probabilities.
  • Risk/reward from here — Downside-to-target vs. upside-if-wrong; is the asymmetry favorable to a short / to avoiding the name?
  • Fundamental floor — Book value, net cash, or asset value that limits downside (honest bears state the floor).

8. Thesis-Killers — "What Would Prove the Bear Wrong" (Mandatory)

Intellectual honesty is what separates a credible bear from a permabear. Explicitly list:

  • The 3–5 developments that would invalidate the short thesis (e.g., margin re-acceleration, successful new product, deleveraging, activist/takeover interest).
  • The strongest bull counterarguments and why the bear still disagrees (or concedes).
  • The biggest risk to being short: valuation support, squeeze potential (cross-reference /short-interest), takeout risk, or a fundamental floor.

Input Formats

Format 1: Single-Stock Bear Case

User: /bear-case TSLA

Claude builds the full short thesis and quantifies downside for TSLA.

Format 2: Counter a Bullish Thesis (Inverse Mode)

User: /bear-case NVDA — here is my bull thesis: [paste]

Claude attacks each pillar of the bull thesis and surfaces the counterevidence.

Format 3: Red-Team a Prior Analysis

User: /bear-case — challenge this stock-eval output: [paste]

Claude takes the opposing side of the prior (likely balanced or bullish) analysis.

Output

Provide a structured bear-case report:

1. One-Sided-Disclosure Banner

⚠️ This is a deliberately one-sided bear case built to surface counterevidence. Pair it with /stock-eval or a bull analysis for a balanced view.

2. Bear Thesis in Three Sentences

The elevator pitch for why the stock is a bad hold.

3. Bear Case Strength Score (0–10)

Pillar                              Weight   Score
Valuation stretch                    0–2      X.X
Deteriorating fundamentals           0–2      X.X
Accounting / earnings-quality flags  0–2      X.X
Competitive & secular threats        0–2      X.X
Management & capital allocation      0–1      X.X
Catalyst clarity & timing            0–1      X.X
                          BEAR CASE STRENGTH:  X.X / 10
Bear Case Strength   Interpretation
0.0–2.0              Weak — few credible negatives; bull case likely intact
2.1–4.0              Modest — some concerns, not thesis-breaking
4.1–6.0              Moderate — real red flags; reduce/hedge worth considering
6.1–8.0              Strong — multiple independent negatives; avoid / short candidate
8.1–10.0            Severe — deep impairment or fraud-risk signals; high-conviction bear

4. Detailed Findings

Cover pillars 1–7 above, each with the evidence and its severity.

5. Downside Target & Risk/Reward

Bear price target with the math, scenario tree, and asymmetry assessment.

6. Thesis-Killers

The mandatory list of what would prove the bear wrong.

Signal Output

The Bear Case Strength Score maps to the standard signal as follows: a stronger bear case (higher score) means a more BEARISH signal. A strong/severe bear case → BEARISH / SELL; a weak bear case → the bear failed to make its point, leaning NEUTRAL-to-constructive. Because this skill argues one side, state the mapping explicitly so the user reads the block correctly.

All analysis concludes with this standardized block:

## Thesis Invalidation

After delivering the analysis signal, specify what would reverse it:

**If signal is BULLISH — thesis breaks if:**
- Price closes below the MA200 / key support level identified in this analysis on above-average volume
- Fundamentals deteriorate: margin compression, decelerating revenue, or a guide-down
- Macro regime shift: Fed pivots hawkish unexpectedly, recession probability >60%

**If signal is BEARISH — thesis breaks if:**
- Margin or revenue growth re-accelerates and beats consensus with a guidance raise
- A thesis-killer fires: successful new product, deleveraging, activist/takeover interest, or a short squeeze
- Valuation compresses to a level that already prices in the bear case (downside exhausted)

**Re-run this analysis when:**
- [ ] Next earnings release
- [ ] Price moves ±15% from current level
- [ ] 60 days have elapsed
- [ ] Material news event (acquisition, leadership change, regulatory decision)

╔══════════════════════════════════════════════╗
║              INVESTMENT SIGNAL               ║
╠══════════════════════════════════════════════╣
║ Signal:      BULLISH / NEUTRAL / BEARISH     ║
║ Confidence:  HIGH / MEDIUM / LOW             ║
║ Horizon:     SHORT / MEDIUM / LONG-TERM      ║
║ Score:       X.X / 10                        ║
╠══════════════════════════════════════════════╣
║ Action:      BUY / HOLD / SELL               ║
║ Conviction:  STRONG / MODERATE / WEAK        ║
╚══════════════════════════════════════════════╝

Score Guide: 8.0–10.0 Strongly Bullish | 6.0–7.9 Moderately Bullish | 4.0–5.9 Neutral | 2.0–3.9 Moderately Bearish | 0.0–1.9 Strongly Bearish Confidence: HIGH (strong data, clear signals) | MEDIUM (mixed signals) | LOW (limited data, conflicting signals) Horizon: SHORT-TERM (1 week–3 months) | MEDIUM-TERM (3 months–1 year) | LONG-TERM (1+ years)

Note: The Score above uses the standard bullish scale for cross-skill comparability. A strong bear case produces a LOW score (bearish). Because this analysis is deliberately one-sided, always pair it with /stock-eval before acting.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.