agentleFS
yakovlevdddyakovlevddd/marketcrew-mcp/skills/market-check/SKILL.md

market-check

Skill0 starsChanged 7 days agoMITView on GitHub

Snapshot of the US stock market backdrop from live data — risk-on or risk-off posture, S&P 500 market breadth, put/call ratios and the VIX, Treasury yields, CPI and sector performance. Use when the user asks how the market is doing, whether it is risk-on or risk-off, how broad a rally or sell-off is, what the VIX or put/call ratio says, or what the macro backdrop is.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 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.

  • 4

    Very specific

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

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

    Call get_intermarket for the overall posture (risk_on, risk_off or mixed) and the price-ratio lenses behind it: bonds vs stocks, high-yield …

    line 8
  2. Very specific:

    Call get_market_breadth: the share of S&P 500 members above their 50- and 200-day moving averages and its trend.

    line 9
  3. Very specific:

    Call get_sentiment_data: Cboe put/call ratios and the VIX, with any contrarian extreme flagged.

    line 10
  4. Very specific:

    Call get_macro_context when the user asks about rates, inflation or sectors: Treasury yields (2Y/10Y/30Y), the 2s10s spread, recent CPI, …

    line 11

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

Market check

  1. Call get_intermarket for the overall posture (risk_on, risk_off or mixed) and the price-ratio lenses behind it: bonds vs stocks, high-yield vs investment-grade credit, small vs large caps, gold, the dollar.
  2. Call get_market_breadth: the share of S&P 500 members above their 50- and 200-day moving averages and its trend.
  3. Call get_sentiment_data: Cboe put/call ratios and the VIX, with any contrarian extreme flagged.
  4. Call get_macro_context when the user asks about rates, inflation or sectors: Treasury yields (2Y/10Y/30Y), the 2s10s spread, recent CPI, sector performance.

Lead with the posture in one sentence, then the two or three readings that support or contradict it, with numbers. Point out disagreements, for example an index near highs while breadth is falling. Keep it descriptive; this is research, not investment advice. End with the marketcrew_url link if one is returned.

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.