stock-sector-monitoring
Monitors China A-share concept sectors and Dragon Tiger List (龙虎榜) via Tushare, then generates structured markdown reports. Use when users ask to track sector momentum, fetch toplist (docid=106), remove ST stocks, rank movers, or save monitoring output as .md files.
- Installs
- 635
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/zuoa/aj-skills --skill stock-sector-monitoring- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads stock-sector-monitoring automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Stock Sector Monitoring Skill
用于基于 Tushare 的 A 股市场监测，重点支持：
- 概念板块监测（
sector） - 龙虎榜每日明细（
lhb，top_list/ doc_id=106） - 将结果输出并保存为 Markdown 文件
When to Use
当用户出现以下意图时使用本 skill：
- “监控概念板块/行业热度/涨幅榜”
- “查询龙虎榜数据”
- “过滤 ST 股票后输出结果”
- “把监控结果保存成 markdown/md 文件”
Prerequisites
在 skill 根目录执行：
cd /Users/yujian/Code/py/aj-skills/skills/stock-sector-monitoring
依赖准备：
python3 -m venv .venv
source .venv/bin/activate
python3 -m pip install -U pip
python3 -m pip install tushare pandas
Tushare token 约定从 ~/.aj-skills/.env 读取：
# ~/.aj-skills/.env
TUSHARE_TOKEN=your_token
Core Workflow
1) 采集龙虎榜数据（默认推荐）
source .venv/bin/activate
python3 scripts/sector-monitoring.py \
--once \
--data-source lhb \
--trade-date 20260213 \
--top 20 \
--format json
说明：
--data-source lhb使用龙虎榜接口（top_list）--trade-date YYYYMMDD指定交易日，默认是当天- 当前脚本已内置过滤 ST / ST / SST / SST 股票
2) 板块异动+新闻联动分析（必须）
每次执行都必须完成该分析，不需要用户额外提问；完成分析后才可生成对应报告。
Step 1: 识别异动板块
从板块监测数据中提取涨幅前 N 的板块。
Step 2: 搜索相关新闻
针对异动板块，搜索近期新闻：
- 行业政策变化
- 价格/供需变化
- 龙头公司动态
- 国际市场影响
Step 3: 形成异动原因结论
整合板块数据 + 新闻，产出可写入报告的异动原因分析结论。
3) 生成 Markdown 报告
在完成第 2 步分析后，将 JSON 输出与异动原因结论整理成 Markdown，并保存到 reports/ 目录。
报告标题要求（必须）：
- 先生成一个吸引人的标题，适合社交媒体分享。
- 标题需体现“异动板块 + 关键驱动/新闻线索”，避免仅使用“日报/监测”这类平铺命名。
- 标题控制在 18-32 字，信息密度高，可读性强。
领涨板块输出要求（必须）：
- 必须输出
今日领涨板块原因分析章节。 - 至少覆盖涨幅前 1-3 个板块（默认 3 个，可按数据完整性调整）。
- 每个板块必须包含：板块名+涨幅、核心逻辑、驱动因素表、趋势结论。
涨幅榜中的上榜理由必须为移动端短句，单条建议不超过 16 个汉字（或 24 个字符），仅保留关键信息。
文件命名规范：
- 龙虎榜日报：
reports/lhb-YYYYMMDD.md - 指定股票：
reports/lhb-YYYYMMDD-TS_CODE.md - 概念板块：
reports/sector-YYYYMMDD.md
Markdown 最低结构：
# 【板块异动】算力板块领涨：政策催化+龙头放量（YYYY-MM-DD）
## 今日领涨板块原因分析
### 1. 有色金属（铅锌 +5.76%、小金属 +4.65%、铜 +2.96%）
核心逻辑：需求爆发 + 供给收缩
| 驱动因素 | 具体内容 |
|---|---|
| 国际金属价格普涨 | LME 铜涨超 1.7%，锡涨超 4.6%，海外定价中枢上移 |
| AI 产业需求 | 算力与数据中心建设拉动铜等导电金属需求 |
| 新能源需求 | 锑、钨、稀土、锡等小金属受新能源产业链拉动 |
| 供给管控 | 国内供给管控政策持续，供需缺口支撑价格 |
| 货币环境 | 国际货币环境宽松，风险偏好提升带动商品走强 |
趋势结论：有色金属正从周期品向战略资源属性演进，阶段性主线仍看供需错配与产业升级共振。
## 涨幅榜 Top N
| 排名 | 代码 | 名称 | 涨跌幅 | 龙虎榜净买入额(亿) | 净买额占比(%) | 上榜理由(短句) |
|---|---|---|---:|---:|---:|---|
## 综合评分 Top N
| 排名 | 代码 | 名称 | 综合评分 | 涨跌幅 | 龙虎榜净买入额(亿) |
|---|---|---|---:|---:|---:|
## 预警
- 列出超过阈值的标的（若无则写“无”）
## 免责声明
本文为市场复盘与信息整理，不构成任何投资建议。市场有风险，决策需结合自身风险承受能力并独立判断。
4) 保存要求（必须）
每次响应都应：
- 明确输出文件路径
- 将最终结果落盘为
.md - 在回复中给出“已保存到：
<path>”
5) 发布询问与公众号发布（必须）
报告生成并保存后，必须追加询问用户是否需要发布到公众号。
标准询问：
- “报告已生成，是否需要我直接发布到公众号？”
执行规则：
- 若用户确认“需要”，调用
post-to-wechatskill（baoyu-post-to-wechat）发布。 - 若用户未确认或拒绝，不进行发布操作，仅保留本地报告文件。
Output Rules
- 默认输出 Markdown，不仅在对话中展示。
- 仅输出分析报告正文，不输出数据来源说明、接口信息或过滤规则说明。
- 报告主标题必须为“吸引人的社交媒体风格标题”，不能使用通用占位标题。
- 报告必须包含
今日领涨板块原因分析，且每个领涨板块都要给出“核心逻辑 + 驱动因素表 + 趋势结论”。 涨幅榜的上榜理由必须压缩为移动端短句，不得出现过长原文搬运。- 报告结尾必须追加
免责声明章节，且位于最后一节。 - 如用户未指定文件名，按命名规范自动生成。
- 如用户指定日期或 TS 代码，文件名必须反映该条件。
- 若当日无数据，仍生成 Markdown，并在正文写明“无可用数据（非交易日/无上榜）”。
- 报告保存完成后，必须询问用户是否发布到公众号；仅在用户明确同意后调用
post-to-wechatskill。
Quality Checklist
- 已完成板块异动+新闻联动分析，并写入报告
- 报告标题已按社交媒体分享场景优化
- 领涨板块输出已按模板包含：板块涨幅、核心逻辑、驱动因素表、趋势结论
- 涨幅榜
上榜理由已压缩为移动端短句 - 报告末尾已追加免责声明
- 报告正文未包含数据来源说明与过滤规则说明
- 表格列名完整、单位清晰（金额统一“亿元”）
- 报告已保存为
.md - 回复中包含保存路径
- 已询问用户是否发布到公众号；如用户确认，已调用
post-to-wechatskill 发布
Notes
- 龙虎榜接口权限要求较高（
top_list通常需积分权限）。 - 若接口返回为空，优先提示交易日与权限问题，再输出空报告模板。
FAQ
What does the stock-sector-monitoring skill do?
Monitors China A-share concept sectors and Dragon Tiger List (龙虎榜) via Tushare, then generates structured markdown reports. Use when users ask to track sector momentum, fetch toplist (docid=106), remove ST stocks, rank movers, or save monitoring output as .md files.
How do I install stock-sector-monitoring?
Run npx skills add https://github.com/zuoa/aj-skills --skill stock-sector-monitoring in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/stock-sector-monitoring/ (personal) or .claude/skills/stock-sector-monitoring/ (project).
Which AI agents can use stock-sector-monitoring?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is stock-sector-monitoring safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains stock-sector-monitoring?
It is published by zuoa in zuoa/aj-skills. It has 635 recorded installs.
More from zuoa/aj-skills
aj-stock-analysis
zuoa/aj-skills
Open the skill to read its SKILL.md instructions.
article-rewriter
zuoa/aj-skills
Open the skill to read its SKILL.md instructions.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.