AF alphagbm-alert
Set price, IV, or activity-based alerts with contextual notifications. Alert types include IV rank threshold crossing, price support/resistance breaks, unusual activity detection, earnings approaching, and VRP signal changes. Triggers: "alert me when AAPL IV rank above 80", "notify if NVDA drops below 850", "earnings alert for TSLA", "VRP alert", "set price alert", "alert when IV spikes", "notify on unusual activity", "my alerts", "delete alert"
Set price, IV, or activity-based alerts with contextual notifications.
As a process F 33/100 · Will not run — References files that are not bundled: ../alphagbm-watchlist/, ../alphagbm-iv-rank/, ../alphagbm-unusual-activity/
How to improve
- 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
missing-refreference to a missing file: ../alphagbm-watchlist/ - warning
missing-refreference to a missing file: ../alphagbm-iv-rank/ - warning
missing-refreference to a missing file: ../alphagbm-unusual-activity/ - note
frontmatter-keyunknown frontmatter key "globs"
Process rating: all ten parameters 33/100
- 0Tools and files. 3 referenced file(s) missing: ../alphagbm-watchlist/, ../alphagbm-iv-rank/, ../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. 5 mutating operations with no state check
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 690 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 9 example trigger phrases
- +3Description length 449: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.