agentleFS
makeevmakeev/alphai-claude-skills/skills/stock-brief/SKILL.md

stock-brief

Skill1 starsChanged 36 days agoMITView on GitHub

Produce a situational brief on a single stock/ticker — its recent high-relevance news, earnings reads, insider activity, and what to watch next — using the AlphAI MCP. Use when the user asks to "brief me on <ticker>", "what's going on with <company>", "catch me up on NVDA", or wants a quick read on one name.

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. Ries630/StockCopilot★ 0same 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

8 rules. About 0 are common, 2 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Resolve the ticker: If the user gave a company name, not a symbol, call alphai_tickers(q=...) to find it.

    line 15
  2. Very specific:

    Pull the ticker feed: Call alphai_ticker_news(ticker, collapse_stories=true).

    line 18
  3. Very specific:

    Earnings read: Call alphai_earnings(ticker) for AlphAI's own filing-verified reads (8-K item 2.02 / 6-K earnings release, every figure …

    line 22
  4. Very specific:

    Optional context: If the user wants the wider tape, call alphai_trending(limit=5) and note any market-level story that touches this name or …

    line 30
  5. Very specific:

    Deep-dive on demand: If one story clearly drives the brief and the user wants detail, fetch it with alphai_article(uid) for the full …

    line 33
  6. Distinctive:

    Keep it to a screen. Structure:

    line 40
  7. Very specific:

    Every story carries a 1–10 relevance_score.

    line 56
  8. Distinctive:

    If the feed is thin, say so plainly rather than padding.

    line 60

≈ “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

Stock brief

Give a tight, decision-useful read on one ticker from AlphAI's enriched feed. Not a price quote — a news brief: what's been happening, what the last earnings filing actually said, who's buying or selling, and what to keep an eye on.

Steps

  1. Resolve the ticker. If the user gave a company name, not a symbol, call alphai_tickers(q=...) to find it. If alphai_ticker_news returns unknown_ticker=true, tell the user and stop — don't invent coverage.
  2. Pull the ticker feed. Call alphai_ticker_news(ticker, collapse_stories=true). collapse_stories folds syndicated reprints into one row each and adds a sources_count corroboration signal — prefer it for a clean brief. Insider news is included by default; keep it.
  3. Earnings read. Call alphai_earnings(ticker) for AlphAI's own filing-verified reads (8-K item 2.02 / 6-K earnings release, every figure checked against the filing). The feed tools return articles about a quarter; this returns the filing's numbers. An empty reports list is a normal answer, not an error. If non-empty, lead from the newest read — fiscal_period, verdict (strong/solid/mixed/weak), a headline analysis.key_metrics, guidance; next_report_date is company-confirmed (never an estimate) and null means none held.
  4. Optional context. If the user wants the wider tape, call alphai_trending(limit=5) and note any market-level story that touches this name or its sector.
  5. Deep-dive on demand. If one story clearly drives the brief and the user wants detail, fetch it with alphai_article(uid) for the full enrichment (ticker analysis, key entities). The article body is not served — work from the enrichment and summary.

Output

Keep it to a screen. Structure:

  • One-line read — the single most important thing about this name right now.
  • Top stories — 3–5 bullets, each: headline · relevance score · one-clause "why it matters". Lead with the highest relevance_score.
  • Earnings — the newest alphai_earnings read if there is one: period · verdict · 1–2 metrics · guidance line. Otherwise one line ("no published AlphAI earnings read yet").
  • Insider activity — any SEC Form 4 rows from the feed: who, buy or sell, size, and whether a sale ran under a 10b5-1 plan (insider.is_10b5_1). "No notable insider activity in the window" is a valid line.
  • Watch next — 1–2 concrete things that would change the picture, incl. the next_report_date when set.

Guardrails

  • Every story carries a 1–10 relevance_score; lead with the high ones and say the score so the user can calibrate.
  • This is news, not advice. Don't issue buy/sell calls or price targets — summarize what the reporting says and let the user decide.
  • If the feed is thin, say so plainly rather than padding. A short honest brief beats a long speculative one.

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.