agentleFS
krzysukrzysu/market-skills/skills/market-overview/SKILL.md

market-overview

Skill3 starsChanged 4 months agoMITView on GitHub

Unified market scan: runs trend-analysis + squeeze + RSI on multiple tickers in parallel, scores them 0-100, and ranks them with actions (BUY/SELL/WATCH). Use for a full market landscape, screening, or daily brief. Supports any yfinance tickers.

3 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    When you need conviction-ranked trade ideas — l3-conviction-scan / run-all-l3 are the right layers.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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-overview

High-level market scanner that runs all indicators on a watchlist of tickers and produces a unified, ranked overview with per-ticker actions.

When NOT to use

  • As a trade signal — it is a screening/landscape tool; the BUY/SELL/WATCH action is a score, not an entry plan. Verify individual setups with market-trend-quality and an L3 strategy (run-all-l3).
  • For deep per-ticker analysis — use the single skills (market-trend, market-squeeze, market-rsi) or run-watchlist for L2 + L3 + notes.
  • When you need conviction-ranked trade ideas — l3-conviction-scan / run-all-l3 are the right layers.

Quick Start

# Default watchlist (SPY, QQQ, AAPL, GOOGL, BTC-USD, GLD)
uv run skills/market-overview/scripts/run.py --json

# Custom tickers
uv run skills/market-overview/scripts/run.py AAPL MSFT NVDA --json

# Filter by action
uv run skills/market-overview/scripts/run.py --action BUY --json

# Top N only
uv run skills/market-overview/scripts/run.py --top 5 --json

# Custom timeframe (matches all other market-* skills)
uv run skills/market-overview/scripts/run.py AAPL MSFT --interval=4h --period=6mo --json

What it returns

  • Per-ticker: price, trend verdict, RSI, squeeze signal, unified score (0-100)
  • Action classification: STRONG_BUY (>=75), BUY (>=55), WATCH (>=35), AVOID (<35)
  • Ranked list sorted by unified score descending
  • Macro context (VIX if available)

Scoring Model

The unified score weights each component and normalizes to 0-100. For details, see references/scoring.md.

Edge Cases

  • Tickers with insufficient data are skipped and noted in errors.
  • The default watchlist is a suggestion — pass your own tickers for custom screening.
  • This is a screening tool, not a trading signal. Verify individual setups with market-trend-quality.

Output envelope (AXI)

--json output follows the canonical AXI envelope — {data, count, errors, help[]}. Default schema is the per-skill minimal fields (3-6 essentials); pass --fields=<csv> to project or --full for the full payload. count is the item count, help[] is contextual next-step command templates. Lib.py return shapes (L1Result / L2Result / L3Result / L3Idea / RegimeSignal) are unchanged — the envelope wraps them at the scripts/run.py boundary.

Home view (no-arg mode)

No-arg mode prints the home view from $XDG_DATA_HOME/market-skills/<skill>_last.json (last successful run). Errors are not cached.

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.