AD investment-research
投研分析技能套件：业绩快评、可比公司分析、晨会纪要、深度报告、研报摘要、行业研究、读年报、调研纪要。 业绩快评: 帮我点评下财报, 帮我快速看下业绩, 业绩点评, 财报速评, 季报分析; 可比公司分析: 可比公司分析, 可比公司, PE对比, comps; 晨会纪要: 晨会纪要, 晨会, 早盘观点, morning brief; 深度报告: 深度报告, 首次覆盖, 公司深度; 研报摘要: 研报摘要, 卖方研报, 观点提炼; 行业研究: 帮我研究下这个行业, 帮我分析下产业链, 行业格局, 行业研究; 读年报: 帮我读一下这份年报, 帮我分析下这份年报, 10-K, 年报分析; 调研纪要: 调研纪要, 实地调研, 专家访谈。
投研分析技能套件：业绩快评、可比公司分析、晨会纪要、深度报告、研报摘要、行业研究、读年报、调研纪要。 业绩快评: 帮我点评下财报, 帮我快速看下业绩, 业绩点评, 财报速评, 季报分析; 可比公司分析: 可比公司分析, 可比公司, PE对比, comps; 晨会纪要: 晨会纪要, 晨会, 早盘观点, morning…
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: 11. 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")
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 (investment-research) differs from the folder (investment-research-v1)
- 100Tools and files. No external tools needed
- 100Steps. 24 steps
- 100Execution cost. Instruction body is 1242 tokens
- 100Running it twice. No mutating operations
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 315: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 24 items
- +4Has examples (2 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.