agentleFS
Sign inStart free
makeevmakeev/alphai-claude-skills/skills/manage-alerts/SKILL.md

manage-alerts

Skill1 starsChanged 36 days agoMITView on GitHub

List, add, or remove the user's ticker news-alert subscriptions through the AlphAI MCP. Use when the user asks to "alert me on <ticker>", "subscribe me to <ticker> earnings news", "what alerts do I have?", "stop alerts for <ticker>", or to manage their AlphAI alert inventory. Requires a paid (Basic/Pro) AlphAI plan.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. elastic/example-mcp-app-observability★ 17same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a change, restate the resulting subscription in one line: ticker, which categories trigger it, and the minimum relevance — so the …

    line 38
  2. Distinctive:

    Confirm before mutating: Read back what you're about to subscribe to or remove before calling the write tool, especially for bulk changes.

    line 46
  3. Distinctive:

    Never subscribe to tickers the user didn't ask for.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Manage alerts

Let the user manage their own AlphAI ticker news-alert subscriptions from the chat. Identity comes from the OAuth login — these tools act on the caller's own account.

Tier-gated. alphai_alerts_* require a Basic or Pro plan. On the Free tier they return tier_not_paid — relay that and point to https://alphai.io/pricing instead of retrying.

Steps

  1. Show current state first. For any add/remove, call alphai_alerts_list() up front so you (and the user) can see existing subscriptions, the per-alert filters, and the tier limit (current / limit).
  2. Subscribe / update. alphai_alerts_subscribe(ticker, category_filter?, min_relevance_score?).
    • This is a partial update: omitting a field on an existing subscription preserves its current value. A brand-new subscription defaults min_relevance_score to 7. The threshold applies to email and Telegram delivery; a Pro webhook receives every matched story and filters on its own.
    • Crypto alerts use the <SYM>-USD ticker (BTC-USD); bare BTC is a stock/ETF symbol, and the response's note says so.
    • category_filter is an optional whitelist from the 14 categories (e.g. ["earnings", "insider"]) — only those categories trigger the alert.
    • Confirm the ticker is real first if unsure (alphai_tickers); the tool raises unknown_ticker / limit_reached otherwise.
  3. Unsubscribe. alphai_alerts_unsubscribe(ticker) — idempotent; returns {removed: false} if it was already inactive.

Output

  • After a change, restate the resulting subscription in one line: ticker, which categories trigger it, and the minimum relevance — so the user sees exactly what they'll be alerted on.
  • For a list request, render the subscriptions as a short table (ticker · categories · min relevance · delivery mode) and note current/limit.

Guardrails

  • Confirm before mutating. Read back what you're about to subscribe to or remove before calling the write tool, especially for bulk changes.
  • Handle errors plainly: tier_not_paid → suggest upgrading; limit_reached → list current alerts so the user can free a slot; unknown_ticker → don't guess a substitute.
  • Never subscribe to tickers the user didn't ask for.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free