| name | sector-overview |
| description | Create comprehensive industry and sector landscape reports covering market dynamics, competitive positioning, key players, and thematic trends. Use for client requests, sector initiations, thematic research pieces, or internal knowledge building. Triggers on "sector overview", "industry report", "market landscape", "sector analysis", "industry deep dive", or "thematic research". The subject is the **industry**; a deep dive on one company carrying a target price and a rating is `research-report`, which calls this skill for its industry section. |
Sector Overview
0. Data Sourcing & Provenance — NEVER FABRICATE
This section is the one to get right before any other. Market research lives or dies on credible numbers. A market-size, share, growth, or multiple figure with no traceable source is worse than no figure. A blank with a note beats an invented number.
Provenance has two mechanisms, and they divide the work. The clickable numbered source marker [n] on the figure, jumping to ## 来源 at the end, is the primary one: in flowing sector prose whose claims are all externally sourced, a [n] entry that names the firm, the date, and the basis already tells the reader the number is [披露] or [预期], so those two chips are not required in the narrative. But a citation cannot tell a reader that a number is ours or that a report is unconfirmed, so three tags are chipped inline even in prose:
[测算] — anything we computed or assumed (a CAGR we derived, an implied share, a range midpoint).
[推断] — our analytical read with no corresponding record ("this likely reads across to peers").
[媒体] — reported by media and not corroborated by a disclosed record.
Chips ARE required throughout any table, KPI strip, or valuation summary, where disclosed actuals, our computations, and third-party forecasts sit side by side and the reader cannot otherwise tell them apart. The Chinese forms in a Chinese deliverable, the English aliases in an English one; never mixed, and never a paraphrase such as or . always names its provider inline.