price-alert
${var} — Optional. Pass one or more
target_pricelevels (comma-separated USD numbers, scientific notation allowed) to fire a one-time alert when the price crosses any of them. Empty = only ATH and sharp-move gates run. Passdry-runto skip notify (state still updates). Passset-target:<price>— the shape the Telegram force-reply sends (step 7) — to register a target and get a one-line confirmation.
Today is ${today}. repo-pulse reports star/fork deltas once a day, and the other scheduled digests run at fixed hours. None of them tell the operator "the price just hit a new high" or "the token moved 28% in the last hour" — both are events that warrant attention the moment they happen, not 14 hours later in a daily digest. This skill closes that window.
Why this exists
Scheduled daily digests are calm summaries. Real moves need real-time signal. Three classes of move are worth a same-day ping:
- New all-time high. The single most narrative-shaping price event a token can have. Worth marking on the timeline regardless of size.
- Sharp 1h moves (±20%). Either a buyer wave or a liquidation cascade — both change what the operator does next (post about it, watch for follow-through, check the chart).
- Operator-set target crossings. The operator may want to know when price clears $X (often a personal stretch goal or a level tied to a tweet/launch). One alert per target per direction.
Everything else is noise not worth a same-day ping.
Config
Reads:
memory/MEMORY.md"Tracked Token" section — the tracked token's contract/chain. If absent, exit silently.memory/topics/price-alert-state.json— last-known ATH, last-alert timestamps per event type, target-crossing history. Created with defaults on first run.