BF investment-analysis-workflow
投资分析工作流管理。规范"拿到新材料后如何基于已存档报告做增量分析"的完整SOP，解决分析碎片化、逻辑断裂问题。用于：(1)收到新材料/公告/研报/调研纪要后的标准分析流程，(2)存量报告合并重组，(3)大开门股票池的持续维护。与 prosperity-investing（景气投资框架）和 optical-comm-investing（光通信框架）协同使用——本skill负责流程规范，彼等负责分析方法论。触发词：分析新材料、增量更新、追加分析、更新股票池、合并报告、存档分析、工作流。
投资分析工作流管理。规范"拿到新材料后如何基于已存档报告做增量分析"的完整SOP，解决分析碎片化、逻辑断裂问题。用于：(1)收到新材料/公告/研报/调研纪要后的标准分析流程，(2)存量报告合并重组，(3)大开门股票池的持续维护。与 prosperity-investing（景气投资框架）和…
As a process F 33/100 · Will not run — References files that are not bundled: references/detailed-framework.md, references/four-waves.md, references/selection-criteria.md
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
- 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: 3. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/detailed-framework.md - warning
missing-refreference to a missing file: references/four-waves.md - warning
missing-refreference to a missing file: references/selection-criteria.md - warning
missing-refreference to a missing file: references/supply-chain.md - warning
missing-refreference to a missing file: references/tech-landscape.md - warning
missing-refreference to a missing file: references/methodology.md
Process rating: all ten parameters 33/100
- 0Tools and files. 6 referenced file(s) missing: references/detailed-framework.md, references/four-waves.md, references/selection-criteria.md
- 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
- 100Steps. 56 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2879 tokens
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
- -212 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 244: enough signal without eating the budget
- +4Structure: 33 headings
- +3Step-by-step instructions: 56 items
- +4Has examples (11 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.