BF alphagbm-watchlist
Monitor a list of tickers for key changes in price, IV rank, unusual activity, earnings dates, and score changes. Supports custom watchlists and a default "hot options" list. Triggers: "add AAPL to watchlist", "my watchlist", "watch NVDA TSLA META", "watchlist alerts", "remove SPY from watchlist", "hot options", "what's on my watchlist", "watchlist summary", "daily watchlist"
Monitor a list of tickers for key changes in price, IV rank, unusual activity, earnings dates, and score changes.
As a process F 30/100 · Will not run — References files that are not bundled: ../alphagbm-stock-analysis/, ../alphagbm-alert/, ../alphagbm-unusual-activity/
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: ../alphagbm-stock-analysis/ - warning
missing-refreference to a missing file: ../alphagbm-alert/ - warning
missing-refreference to a missing file: ../alphagbm-unusual-activity/ - note
frontmatter-keyunknown frontmatter key "globs"
Process rating: all ten parameters 30/100
- 0Tools and files. 3 referenced file(s) missing: ../alphagbm-stock-analysis/, ../alphagbm-alert/, ../alphagbm-unusual-activity/
- 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. 3 mutating operations with no state check
- 85Steps. 13 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 686 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
- +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
- +5Description quotes 10 example trigger phrases
- +3Description length 378: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.