sector-overview

sector-overview is a skill for Claude Code from yuping322/financial-services-plugins-new. It costs 0 tokens per session (878 once invoked), scanned A, original, Apache-2.0.

A workflow for creating reports about an industry or market sector, including its size, trends, competitors, business models, risks, and valuation. A market sector is a group of related businesses or products.

In plain words
What is it for?
Use it for client reports, sector research, market landscapes, competitive analysis, thematic studies, and internal knowledge building.
Why use it?
It gives research a defined scope and structure instead of producing an incomplete collection of company notes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the equity-research plugin — 9 skills, 9 commands shipped together

Good fit Use it for client reports, sector research, market landscapes, competitive analysis, thematic studies, and internal knowledge building.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/yuping322/financial-services-plugins-new/sector-overview
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add yuping322/financial-services-plugins-new --skill sector-overview
Clone the repo
git clone --depth 1 https://github.com/yuping322/financial-services-plugins-new

Made for: Claude Code.

Or install equity-research, the plugin that ships this one along with the rest of its 9 skills, 9 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for sector-overview

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuping322/financial-services-plugins-new/sector-overview/github.svg)](https://agentmods.dev/skills/yuping322/financial-services-plugins-new/sector-overview)
Your own site
<a href="https://agentmods.dev/skills/yuping322/financial-services-plugins-new/sector-overview"><img src="https://agentmods.dev/badge/skills/yuping322/financial-services-plugins-new/sector-overview/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for sector-overview

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuping322/financial-services-plugins-new/sector-overview"><img src="https://agentmods.dev/badge/skills/yuping322/financial-services-plugins-new/sector-overview.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 878 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00878
Opus 5 $0.00000 $0.00439
Sonnet 5 $0.00000 $0.00176
Haiku 4.5 $0.00000 $0.00088

Measured 11d ago against content hash 2942a63810b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

sector-overview scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

equity-research/skills/sector-overview/SKILL.md · 86 lines

What it actually says

部门概览

描述:创建全面的行业和部门景观报告,涵盖市场动态、竞争定位、关键参与者和主题趋势。用于客户请求、部门启动、主题研究或内部知识构建。触发条件:"部门概览"、"行业报告"、"市场景观"、"部门分析"、"行业深度分析"或"主题研究"。

工作流程

第 1 步:定义范围

  • 部门/子部门:什么行业以及如何明确定义?
  • 目的:客户报告、内部研究、推介材料、创意生成
  • 深度:高级概览(5-10 页)或深度分析(20-30 页)
  • 角度:中立景观vs主题论文(例如,"AI 基础设施建设")
  • 范围:仅公开公司还是包括私人公司?

第 2 步:市场概览

市场规模和增长

  • 总可寻址市场(TAM)及来源
  • 历史增长率(5 年复合增长率)
  • 预测增长率和关键假设
  • 市场细分(按产品、地理、最终市场、客户类型)

行业结构

  • 分散vs整合 — 前 5 大市场份额
  • 价值链图 — 价值在哪里累积?
  • 业务模型类型(订阅、交易、许可、服务)
  • 进入壁垒(资本、监管、技术、网络效应)

关键趋势和驱动因素

  • 长期增长趋势(3-5 个主要趋势)
  • 逆风和风险
  • 技术中断向量
  • 监管发展
  • M&A 活动和整合趋势

第 3 步:竞争景观

公司概况(前 5-10 大参与者):

公司 收入 增长 EBITDA 利润率 市场份额 关键差异

对于每家公司,简要概况:

  • 业务描述(2-3 句)
  • 战略定位和护城河
  • 最近发展(盈利、M&A、产品发布)
  • 估值快照(P/E、EV/EBITDA、EV/收入)

竞争动态

  • 公司如何竞争?(价格、产品、服务、分销)
  • 谁在获得/失去市场份额及其原因?
  • 来自新进入者或相邻参与者的破坏风险

第 4 步:估值背景

  • 部门交易倍数(当前和历史范围)
  • 溢价/折扣驱动因素(增长、利润率、市场定位)
  • 最近 M&A 交易倍数
  • 部门与更广泛市场的比较?

第 5 步:投资影响

  • 最佳风险/收益机会在哪里?
  • 什么主题赌注可以通过这个部门表达?
  • 部门内的关键辩论(牛市vs熊市论证)
  • 可能改变部门叙述的催化剂

第 6 步:输出

  • Word 文档或 PowerPoint,包含:
    • 市场概览和规模
    • 竞争景观图
    • 公司比较表
    • 估值总结
    • 关键图表:市场增长、份额趋势、估值历史
  • 详细公司数据的 Excel 附录

重要说明

  • 所有市场规模数据的来源 — 引用研究公司或方法
  • 区分 TAM 炒作和现实可寻址市场
  • 部门概览老化很快 — 注明日期并标记可能过时的数据
  • 图表很必要 — 市场规模瀑布图、竞争定位矩阵、估值散点图
  • 如果用于客户,将"那又怎样"调整到他们的具体情况(M&A 目标识别、竞争定位、市场进入)
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 86 lines · 0 tokens per session scan A 2942a63810b8

Subscribe to this mod's changes

sector-overview is a skill published in the GitHub repository yuping322/financial-services-plugins-new (17 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 878 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens