BD 030复盘
A股每日短线复盘完整框架（030体系）。提供七阶段复盘流程：昨日交易回顾→盘前环境扫描（消息面三级分类+预期差判断）→竞价分级分析（必做🔴/选做🟡）→开盘验证（量能结构+跷跷板）→盘中动态博弈（分歧哨兵+资金卡位+下午确认）→收盘数据汇总（流动性结构分析+市场健康度1-10量化评分）→隔日概率化推演（情景+概率权重+仓位矩阵+交易计划）。含仓位管理量化标准、信号冲突裁决规则、典型场景推演、每日复盘日志模板。核心原则：风险第一（致命风险→无条件清仓）。适用于A股短线复盘、情绪周期判断、题材轮动分析、制定交易计划。
A股每日短线复盘完整框架（030体系）。提供七阶段复盘流程：昨日交易回顾→盘前环境扫描（消息面三级分类+预期差判断）→竞价分级分析（必做🔴/选做🟡）→开盘验证（量能结构+跷跷板）→盘中动态博弈（分歧哨兵+资金卡位+下午确认）→收盘数据汇总（流动性结构分析+市场健康度1-10量化评分）→隔日概率化推演（情景+概率权…
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 49/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (030复盘) differs from the folder (030-review)
- 100Tools and files. No external tools needed
- 100Steps. 61 steps
- 100Execution cost. Instruction body is 1950 tokens
- 100Running it twice. No mutating operations
- low 16 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 260: enough signal without eating the budget
- +4Structure: 60 headings
- +3Step-by-step instructions: 61 items
- +4Has examples (4 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.