AD aggressive_growth_strategy
激进成长选股与交易分析执行框架——将"周期性成长"方法论转化为可操作的选股筛选、个股深度分析和市场季节判断工具。 当用户需要：按七标准筛选小盘成长股、对个股进行八步体系化分析（赛道→市值→成长→位置→指数→排除→建仓→卖出）、 判断当前市场季节（春夏秋冬）与仓位策略、制定"小偷式"建仓与倒金字塔卖出计划时，加载此技能。 与 aggressive-growth-investing 技能的关系：后者是"心法"（理论体系），本技能是"剑法"（执行工具）。 核心数据源：四层降级架构（Tushare MCP > akshare > baostock > 东方财富API），通过共享模块 data_source.py 统一管理。
激进成长选股与交易分析执行框架——将"周期性成长"方法论转化为可操作的选股筛选、个股深度分析和市场季节判断工具。 当用户需要：按七标准筛选小盘成长股、对个股进行八步体系化分析（赛道→市值→成长→位置→指数→排除→建仓→卖出）、…
As a process D 39/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: 8. 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")
Process rating: all ten parameters 39/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
- 30Running it twice. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (aggressive_growth_strategy) differs from the folder (aggressive-growth-strategy)
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 131 steps
- 100Execution cost. Instruction body is 2904 tokens
- low 12 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 311: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 131 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.