stock-deep-dive

Name: stock-deep-dive
Author: kansoku-trade

226stars19forks

How to install stock-deep-dive?

kansoku-trade/kansoku/stock-deep-dive

$npx -y skills add kansoku-trade/kansoku --skill stock-deep-dive

Installs into the current project.

Summary

Use when the user asks for an end-to-end orientation on a listed company they don't yet understand, especially when the request combines two or more dimensions in one ask. Triggers on "X 是干什么的", "帮我了解 X", "X 主营 + 同行", "盘前为什么涨", "本周趋势 + 阻力支撑", "X 和其他公司的关系", "first time looking at

Files · 1

View on GitHub

SKILL.md

1	# Stock Deep Dive
2
3	## Overview
4
5	A six-lens onboarding workflow for getting up to speed on one listed company in a single pass. Built from a live session where the author repeatedly failed by quoting community-post numbers as if they were company guidance, by trusting GAAP EPS fields when the market quoted non-GAAP, and by reading YoY % deceleration as business slowdown without checking the base.
6
7	Core principle: anchor every numeric claim on a primary source. Press release, 8-K, real OHLCV are primary. Community topic titles, truncated news headlines, and aggregated provider fields are _leads_, not sources. Verify before quoting.
8
9	## When to use
10
11	- User names a ticker they don't know and asks for orientation
12	- Request combines two or more of {business, fundamentals, technicals, catalyst, peers}
13	- "盘前 / 今日为什么涨跌" question — runs lenses 1, 4, partially 6
14	- Request to "explain how X relates to other listed companies" — emphasizes lens 5
15
16	If the user wants only one lens (e.g., just real-time price), do NOT load this skill — go directly to the corresponding `longbridge-*` sub-skill.
17
18	## The six lenses
19
20	Lenses 1–5 are independent. Dispatch their Longbridge calls in parallel. Lens 6 (audit) runs last, against all collected data.
21
22	\| # \| Lens \| Sub-skills \| Output anchor \|
23	\| --- \| -------------------- \| ------------------------------------------------------------- \| ----------------------------------------------------------------------------------------- \|
24	\| 1 \| Business identity \| `longbridge-company-profile` + `longbridge-business-query` \| 1-line "what" + segment revenue mix table \|
25	\| 2 \| Fundamentals \| `longbridge-fundamental` \| Quarterly revenue series (YoY _and_ QoQ) + OpInc trajectory + reconciled EPS \|
26	\| 3 \| Technicals \| `longbridge-technical` + `longbridge-kline` \| Last-5-day OHLCV + week summary + pivot S/R + indicator vote + ATR14 \|
27	\| 4 \| Catalysts \| `longbridge-news` + `trump-truth-monitor` (if policy-exposed) \| Classified news/filings + community sentiment skew + pre-market range + Trump-policy hits \|
28	\| 5 \| Supply chain & peers \| `longbridge-supply-chain` + `longbridge-competitive-analysis` \| Upstream → company → downstream flow + peer valuation table + paired-trade logic \|
29	\| 6 \| Narrative audit \| (this skill, see below) \| Reconciliation: official vs community, GAAP vs non-GAAP, YoY vs QoQ, mix vs aggregate \|
30
31	## Mandatory verification — the recurring traps
32
33	These six errors occur repeatedly when synthesizing a stock brief. The skill exists primarily to prevent them. Self-audit before sending output:
34
35	### Trap 1 — Community topic ≠ company guidance
36
37	Longbridge `news <SYMBOL>` returns mixed feeds. Items with URL pattern `longbridge.com/topics/` are user-posted community threads, not company-issued. Any "FY guide $X" figure sourced from a community-topic title must be verified against the actual press release (`longbridge.com/news/` with reputable `source_name`, or the SEC 8-K) before quoting. Never restate a community-topic number as guidance.
38
39	### Trap 2 — Truncated headline ≠ official statement
40
41	News titles end in "…" when truncated by the feed. Pull the article body (`<url>.md` variant on Longbridge) or the 8-K text before quoting a CEO percentage. If you can't pull the body, attribute as "per news headline — unverified".
42
43	### Trap 3 — Longbridge `financial-report --kind IS` EPS field = GAAP
44
45	US companies report non-GAAP EPS on earnings calls; analyst consensus is also non-GAAP. The Longbridge `IS` EPS field is GAAP diluted. If the value looks absurd (e.g., 0.04 when consensus was 0.80), it's GAAP, not a beat/miss. Always state which basis you're quoting. For non-GAAP, pull from news / press release excerpt.
46
47	### Trap 4 — YoY % deceleration ≠ business slowdown
48
49	Compute QoQ alongside YoY every time. If the base year was itself accelerating off a low, YoY % naturally compresses even as absolute revenue accelerates. Look at the sequential QoQ trend before claiming "growth is slowing". Show implied forward YoY from next-quarter guidance — it often reveals a V-shape that aggregate YoY hides.
50
51	### Trap 5 — Mix shift hides under aggregate growth
52
53	If the company has on

People who liked this also viewed

6 picks

Type

stock-deep-dive

226stars19forks

View on GitHub

How to install stock-deep-dive?

kansoku-trade/kansoku/stock-deep-dive

$npx -y skills add kansoku-trade/kansoku --skill stock-deep-dive

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Stock Deep Dive
2
3	## Overview
4
5	A six-lens onboarding workflow for getting up to speed on one listed company in a single pass. Built from a live session where the author repeatedly failed by quoting community-post numbers as if they were company guidance, by trusting GAAP EPS fields when the market quoted non-GAAP, and by reading YoY % deceleration as business slowdown without checking the base.
6
7	Core principle: anchor every numeric claim on a primary source. Press release, 8-K, real OHLCV are primary. Community topic titles, truncated news headlines, and aggregated provider fields are _leads_, not sources. Verify before quoting.
8
9	## When to use
10
11	- User names a ticker they don't know and asks for orientation
12	- Request combines two or more of {business, fundamentals, technicals, catalyst, peers}
13	- "盘前 / 今日为什么涨跌" question — runs lenses 1, 4, partially 6
14	- Request to "explain how X relates to other listed companies" — emphasizes lens 5
15
16	If the user wants only one lens (e.g., just real-time price), do NOT load this skill — go directly to the corresponding `longbridge-*` sub-skill.
17
18	## The six lenses
19
20	Lenses 1–5 are independent. Dispatch their Longbridge calls in parallel. Lens 6 (audit) runs last, against all collected data.
21
22	\| # \| Lens \| Sub-skills \| Output anchor \|
23	\| --- \| -------------------- \| ------------------------------------------------------------- \| ----------------------------------------------------------------------------------------- \|
24	\| 1 \| Business identity \| `longbridge-company-profile` + `longbridge-business-query` \| 1-line "what" + segment revenue mix table \|
25	\| 2 \| Fundamentals \| `longbridge-fundamental` \| Quarterly revenue series (YoY _and_ QoQ) + OpInc trajectory + reconciled EPS \|
26	\| 3 \| Technicals \| `longbridge-technical` + `longbridge-kline` \| Last-5-day OHLCV + week summary + pivot S/R + indicator vote + ATR14 \|
27	\| 4 \| Catalysts \| `longbridge-news` + `trump-truth-monitor` (if policy-exposed) \| Classified news/filings + community sentiment skew + pre-market range + Trump-policy hits \|
28	\| 5 \| Supply chain & peers \| `longbridge-supply-chain` + `longbridge-competitive-analysis` \| Upstream → company → downstream flow + peer valuation table + paired-trade logic \|
29	\| 6 \| Narrative audit \| (this skill, see below) \| Reconciliation: official vs community, GAAP vs non-GAAP, YoY vs QoQ, mix vs aggregate \|
30
31	## Mandatory verification — the recurring traps
32
33	These six errors occur repeatedly when synthesizing a stock brief. The skill exists primarily to prevent them. Self-audit before sending output:
34
35	### Trap 1 — Community topic ≠ company guidance
36
37	Longbridge `news <SYMBOL>` returns mixed feeds. Items with URL pattern `longbridge.com/topics/` are user-posted community threads, not company-issued. Any "FY guide $X" figure sourced from a community-topic title must be verified against the actual press release (`longbridge.com/news/` with reputable `source_name`, or the SEC 8-K) before quoting. Never restate a community-topic number as guidance.
38
39	### Trap 2 — Truncated headline ≠ official statement
40
41	News titles end in "…" when truncated by the feed. Pull the article body (`<url>.md` variant on Longbridge) or the 8-K text before quoting a CEO percentage. If you can't pull the body, attribute as "per news headline — unverified".
42
43	### Trap 3 — Longbridge `financial-report --kind IS` EPS field = GAAP
44
45	US companies report non-GAAP EPS on earnings calls; analyst consensus is also non-GAAP. The Longbridge `IS` EPS field is GAAP diluted. If the value looks absurd (e.g., 0.04 when consensus was 0.80), it's GAAP, not a beat/miss. Always state which basis you're quoting. For non-GAAP, pull from news / press release excerpt.
46
47	### Trap 4 — YoY % deceleration ≠ business slowdown
48
49	Compute QoQ alongside YoY every time. If the base year was itself accelerating off a low, YoY % naturally compresses even as absolute revenue accelerates. Look at the sequential QoQ trend before claiming "growth is slowing". Show implied forward YoY from next-quarter guidance — it often reveals a V-shape that aggregate YoY hides.
50
51	### Trap 5 — Mix shift hides under aggregate growth
52
53	If the company has on

People who liked this also viewed

6 picks

Type