A股市场深度/订单簿分析。当用户说"市场深度"、"market depth"、"订单簿"、"order book"、"盘口深度"、"挂单量"、"委托深度"时触发。基于 cn-stock-data 获取数据,分析市场深度与订单簿结构。支持 formal/brief 两种输出风格。
Scanned 9/7/2026
Install to Claude Code
npx -y skills add aifinlab/FinClaw --skill a-share-market-depth --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of A Share Market Depth?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aifinlab-a-share-market-depth)More formats (shields.io, HTML) on the badges page.
---
name: a-share-market-depth
description: A股市场深度/订单簿分析。当用户说"市场深度"、"market depth"、"订单簿"、"order book"、"盘口深度"、"挂单量"、"委托深度"时触发。基于 cn-stock-data 获取数据,分析市场深度与订单簿结构。支持 formal/brief 两种输出风格。
---
# 市场深度/订单簿分析助手
## 数据获取
通过 cn-stock-data skill 获取数据:
- **盘口数据**: 5/10档买卖报价与挂单量
- **逐笔委托**: 委托挂单与撤单
- **实时行情**: 最新价格与成交量
## 分析工作流
### Step 1: 深度度量
- 报价深度:最优买卖价各自的挂单量
- 累计深度:前N档的累计挂单量
- 深度不平衡 = (Bid_Depth - Ask_Depth) / Total_Depth
- 加权深度:按距离中间价的远近加权
### Step 2: 订单簿形态
- 对称型:买卖两侧深度均衡
- 买厚型:买方深度远大于卖方(支撑强)
- 卖厚型:卖方深度远大于买方(压力大)
- 稀疏型:两侧深度都薄(流动性差)
### Step 3: 深度动态分析
- 深度的日内变化模式
- 大单挂撤对深度的冲击
- 深度恢复速度(resilience):冲击后多快恢复
- 深度与价格变动的领先滞后关系
### Step 4: 交易应用
- 深度不平衡→短期价格方向预测
- 深度薄弱价位→潜在突破/支撑位
- 深度充足时下单→冲击成本低
- 深度异常变化→可能预示大单进出
### Step 5: 输出报告
## 输出格式
### formal 风格(研报级)
```
# [标的] 市场深度分析报告
## 一、深度概览
| 档位 | 买方(万股) | 卖方(万股) | 不平衡 |
|------|-----------|-----------|--------|
## 二、订单簿形态
[形态判断与含义]
## 三、深度动态
[恢复速度、异常事件]
## 四、交易建议
```
### brief 风格(快速分析)
```
## [标的] 深度速览
- 买方5档累计 12万股,卖方 8万股
- 深度不平衡 +0.20,买方占优
- 订单簿形态:买厚型,支撑较强
- 建议:25.20有强支撑(大单挂买)
```
参考 `references/market-depth-guide.md` 获取详细方法论与 A股实证研究。
## 使用示例
### 示例 1: 基本使用
```python
# 调用 skill
result = run_skill({
"param1": "value1",
"param2": "value2"
})
```
### 示例 2: 命令行使用
```bash
python scripts/run_skill.py --input data.json
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Create Mermaid diagrams for flowcharts, sequences, ERDs, and
Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.
Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.
Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".