agentleFS
Sign inStart free
yakovlevdddyakovlevddd/marketcrew-mcp/skills/stock-check/SKILL.md

stock-check

Skill0 starsChanged 7 days agoMITView on GitHub

Technical check-up of a US stock or ETF from live market data — price and recent move, trend against the 50- and 200-day moving averages, RSI and MACD momentum, nearest support and resistance, next earnings date and recent news. Use when the user asks how a stock is doing, whether it is overbought or oversold, where support or resistance is, why it moved, or "what's going on with" a ticker.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. Ries630/StockCopilot★ 0same name
    2. waj-1/waj-plugin★ 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 repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    Call get_instrument_info with the ticker: price, daily and weekly change, 52-week range, market cap, sector, next earnings date.

    line 10
  2. Very specific:

    Call get_technical_indicators: position against SMA 50 and SMA 200, RSI(14), MACD, ADX, ATR, any golden or death cross or divergence.

    line 11
  3. Very specific:

    Call get_key_levels: the nearest support below and resistance above, and how many times price reacted at each.

    line 12
  4. Very specific:

    If the user asks why it moved, call public_instrument_news with days_back 7 and cite the articles with their links.

    line 13
  5. Very specific:

    If technical events are active (for example RSI below 30 or a new 52-week high), get_event_stats gives what usually followed, with sample …

    line 14

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

Build the answer from MarketCrew data, not from memory. Prices and indicators change daily.

  1. Call get_instrument_info with the ticker: price, daily and weekly change, 52-week range, market cap, sector, next earnings date.
  2. Call get_technical_indicators: position against SMA 50 and SMA 200, RSI(14), MACD, ADX, ATR, any golden or death cross or divergence.
  3. Call get_key_levels: the nearest support below and resistance above, and how many times price reacted at each.
  4. If the user asks why it moved, call public_instrument_news with days_back 7 and cite the articles with their links.
  5. If technical events are active (for example RSI below 30 or a new 52-week high), get_event_stats gives what usually followed, with sample sizes.

Answer in this order: one line on where the stock stands, then trend, momentum and levels with the numbers, then news if asked. Give levels as prices, not vague zones. Mention the next earnings date when it is within two weeks. If the ticker is not covered, say so and name what is covered: the S&P 500, the Nasdaq-100, popular ETFs, bitcoin, ether and the VIX.

End with the marketcrew_url link from the response for the interactive chart. This is research, not investment advice; do not tell the user to buy or sell.

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