A股滑点分析/执行成本分析。当用户说"滑点"、"slippage"、"执行成本"、"成交偏差"、"滑点分析"、"实际成交价偏差"时触发。基于 cn-stock-data 获取数据,分析交易滑点与执行成本。支持 formal/brief 两种输出风格。
Scanned 9/7/2026
Install to Claude Code
npx -y skills add aifinlab/FinClaw --skill a-share-slippage-analysis --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of A Share Slippage Analysis?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/aifinlab-a-share-slippage-analysis)More formats (shields.io, HTML) on the badges page.
---
name: a-share-slippage-analysis
description: A股滑点分析/执行成本分析。当用户说"滑点"、"slippage"、"执行成本"、"成交偏差"、"滑点分析"、"实际成交价偏差"时触发。基于 cn-stock-data 获取数据,分析交易滑点与执行成本。支持 formal/brief 两种输出风格。
---
# 滑点分析/执行成本分析助手
## 数据获取
通过 cn-stock-data skill 获取数据:
- **成交记录**: 实际成交价格与数量
- **行情数据**: 下单时的市场价格
- **盘口数据**: 买卖盘口深度
## 分析工作流
### Step 1: 滑点计算
- 滑点 = 实际成交价 - 预期成交价(信号价)
- 买入滑点:通常为正(成交价高于预期)
- 卖出滑点:通常为负(成交价低于预期)
- 百分比滑点 = 滑点 / 预期价格 × 100%
### Step 2: 滑点分解
- 市场冲击滑点:订单本身推动价格
- 延迟滑点:从信号到执行的时间延迟
- 价差滑点:买卖价差导致的成本
- 部分成交滑点:未完全成交的机会成本
### Step 3: 滑点统计分析
- 平均滑点:所有交易的滑点均值
- 滑点分布:正态/偏态/厚尾特征
- 滑点与订单特征的关系:大小/方向/时段
- 滑点的时间模式:开盘/盘中/尾盘差异
### Step 4: 滑点优化
- 限价单vs市价单:限价单降低滑点但增加未成交风险
- 执行时段优化:选择流动性最好的时段
- 订单拆分:大单拆小降低冲击滑点
- 算法执行:使用VWAP/TWAP算法控制滑点
### Step 5: 输出报告
## 输出格式
### formal 风格(研报级)
```
# 滑点分析报告
## 一、滑点统计
| 指标 | 数值 |
|------|------|
| 平均滑点 | 0.08% |
## 二、滑点分解
[冲击/延迟/价差各占比]
## 三、滑点模式
[时段/订单大小的影响]
## 四、优化建议
```
### brief 风格(快速分析)
```
## 滑点分析速览
- 平均滑点 0.08%
- 主要来源:市场冲击(60%)+价差(30%)
- 开盘时段滑点最大(0.15%)
- 建议:避开开盘15分钟,使用限价单
```
参考 `references/slippage-analysis-guide.md` 获取详细方法论与 A股实证研究。
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".