AD stock-analysis
This skill should be used when the user asks to "analyze a stock", "research a company", "give me a research report on [ticker]", "run stock analysis on [company]", "do fundamental analysis of [ticker]", "evaluate [company] for investment", "what do you think of [ticker]", "analyze [AAPL / TSLA / NVDA / etc.]", "deep dive on [company]", or any request for structured equity research, investment thesis, or financial analysis of a publicly traded company.
This skill should be used when the user asks to "analyze a stock", "research a company", "give me a research report on [ticker]", "run stock analysis on…
As a process D 47/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 47/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
- 40Consistency. Frontmatter name (stock-analysis) differs from the folder (stock-analysis-skills)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Steps. 36 steps
- 100Execution cost. Instruction body is 1731 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -216 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +3Description length 456: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 36 items
- +4Reference files are cited in the instructions (5 of 5)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.