BF x-investment-strategy-analyzer
完整复刻 @jukan05（GF Securities 半导体分析师/150K粉丝 X KOL）的投资分析体系。 以「快速成长趋势识别」为核心分析框架，对任意个股、行业或市场生成「就像 Jukan05 本人撰写」的分析报告。 支持任意标的：若 Jukan 曾分析过，自动引用其历史观点；若未分析过，用其方法论推导。
完整复刻 @jukan05（GF Securities 半导体分析师/150K粉丝 X KOL）的投资分析体系。 以「快速成长趋势识别」为核心分析框架，对任意个股、行业或市场生成「就像 Jukan05 本人撰写」的分析报告。 支持任意标的：若 Jukan 曾分析过，自动引用其历史观点；若未分析过，用其方法论推导。
As a process F 31/100 · Will not run — References files that are not bundled: references/jukan_views/
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: 0. 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/jukan_views/
Process rating: all ten parameters 31/100
- 0Tools and files. 1 referenced file(s) missing: references/jukan_views/
- 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 (x-investment-strategy-analyzer) differs from the folder (jukan-investment-strategy)
- 100Steps. 51 steps
- 100Execution cost. Instruction body is 1187 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
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 157: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 51 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.