us-stock-radar
Skill0 starsChanged 5 months agoMITView on GitHub
Professional US stock radar for screening, deep dives, and watchlist alerts using public market data. Use when the user wants ranked stock candidates, A/B/C/D signal grading, timestamped evidence, confidence-aware summaries, and cleaner pro or beginner explanations for US equities.
In this repository17 other files it gives its agents.
- community-marketingSkill
- copywritingSkill
- social-contentSkill
- memory-dreamSkill
- memory-triageSkill
- search-budget-policySkill
- skill-vetterSkill
- apple_mail_salesSkill
- company_brainSkill
- lead_handoffSkill
- scrapling-lead-searchSkill
- market-environment-analysisSkill
- stock-analysisSkill
- Agent BrowserSkill
- find-skillsSkill
- githubSkill
- summarizeSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 9 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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
- Distinctive: line 8
Run a practical US stock workflow in 3 modes:
- Very specific: line 20
Run scripts/us_stock_radar.py with the appropriate mode.
- Distinctive: line 21
Read JSON output first; treat it as the source of truth.
- Distinctive: line 23
Avoid deterministic predictions.
- Distinctive: line 24
If some endpoints fail, continue with degraded coverage and expose the reduction in confidence.
- Very specific: line 33
Verify that availability, data_gaps, and degraded_mode are exposed when coverage is partial.
- Distinctive: line 49
Read-only skill: query public market endpoints only.
- Distinctive: line 50
Use no authentication, cookies, brokerage accounts, or private APIs.
- Distinctive: line 51
Place no orders, execute no trades, and mutate no portfolio state.
- Distinctive: line 52
Write no files and send no outbound messages as part of normal use.
- Distinctive: line 55
Do not connect a brokerage account unless the user explicitly asks for broker integration in a separate request.
- Very specific: line 66
Default language behavior: auto.
- Very specific: line 67
If --lang auto and the prompt contains Chinese, switch final narrative to Chinese.
- Very specific: line 68
If --lang auto and no Chinese is detected, use English.
- Very specific: line 111
If availability.sec_fundamentals is true, reported fundamentals were filled from SEC Company Facts.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
US Stock Radar
Run a practical US stock workflow in 3 modes:
screener: rank a ticker universe by multi-factor signal scoredeep-dive: analyze one ticker with fundamentals + technical proxieswatchlist: monitor custom tickers and output alert candidatesdaily purchase review: run the OpenClaw wrapper that combines screening, market context, runtime checks, and a user-confirmation prompt
This skill is a read-only heuristic market workflow, not a full institutional research terminal. Public free endpoints may be partial, delayed, or rate-limited; surface those gaps explicitly.
Reported fundamentals are filled from SEC EDGAR Company Facts when Yahoo quote/summary endpoints are intentionally disabled. The SEC fallback uses local caching and serial throttling; it is suitable for PE/PB/ROE/revenue-growth style reported metrics, not forward PE or analyst estimates.
Workflow
- Run
scripts/us_stock_radar.pywith the appropriate mode. - Read JSON output first; treat it as the source of truth.
- Explain conclusions with explicit caveats, confidence, and data gaps.
- Avoid deterministic predictions; present signal grade, trigger reasons, and partial-data warnings.
- If some endpoints fail, continue with degraded coverage and expose the reduction in confidence.
Quick Audit Path
For a fast review:
- Run
python3 skills/us-stock-radar/scripts/us_stock_radar.py --sources - Run
python3 skills/us-stock-radar/scripts/us_stock_radar.py --mode screener --json - Confirm the script only performs read-only public HTTP requests.
- Verify that
availability,data_gaps, anddegraded_modeare exposed when coverage is partial.
Commands
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --sources
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --version
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --mode screener --tickers "AAPL,MSFT,NVDA,AMZN,GOOGL"
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --mode deep-dive --ticker AAPL --audience pro
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --mode deep-dive --ticker TSLA --audience beginner --lang zh
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --mode watchlist --tickers "AAPL,NVDA,TSLA" --event-mode high-alert
python3 skills/research/us-stock-radar/scripts/us_stock_radar.py --mode screener --jsonSafety / Scope Boundary
- Read-only skill: query public market endpoints only.
- Use no authentication, cookies, brokerage accounts, or private APIs.
- Place no orders, execute no trades, and mutate no portfolio state.
- Write no files and send no outbound messages as part of normal use.
- Produce analysis only; not investment advice.
- Daily purchase review must ask for explicit user confirmation before any real-world action.
- Do not connect a brokerage account unless the user explicitly asks for broker integration in a separate request.
Optional Local Integration
- Runtime: configure a Python virtual environment with the dependencies required by the script.
- Config: keep local config files outside the repository when they contain personal workflow settings.
- Logs: write runtime logs to a local ignored directory.
- Reference repos: keep external research repos outside this repository unless they are vendored intentionally.
Output Policy
- Default language behavior:
auto. - If
--lang autoand the prompt contains Chinese, switch final narrative to Chinese. - If
--lang autoand no Chinese is detected, use English. --jsonoutput is language-neutral.- Always include:
as_of_utcmodeevent_modeavailabilitydata_gapsdegraded_modeconfidencesources- heuristic notes / caveats
- Audience modes:
pro: concise signal summarybeginner: plain-language interpretation
- Event modes:
normalhigh-alert(stricter thresholds)
Scoring (A/B/C/D)
Signal score combines heuristic checks such as:
- valuation range (PE)
- RSI health
- volume expansion
- price vs MA50
- revenue growth
- ROE quality
Grades:
- A: score >= 5
- B: score = 4
- C: score = 2-3
- D: score <= 1
Interpretation Guardrails
- Grades are heuristic summaries, not price targets.
- Missing fundamentals should lower confidence rather than silently default bullish/bearish.
- Free-market endpoints can be delayed, partially populated, or blocked by region.
- Premarket / scheduled workflows should keep timestamps explicit.
- In OpenClaw/Bounty conversations, do not fetch Yahoo chart URLs through
web_fetchand do not paste raw Yahoo JSON. Use the local script and summarize its JSON output. - In OpenClaw/Bounty conversations, prefer
--compact-json. Do not describe*_yahoo_quote_skippedor*_yahoo_summary_skippedas current Yahoo rate limiting; those are intentional protection settings unless actual 429/cooldown signals are present. - If
availability.sec_fundamentalsis true, reported fundamentals were filled from SEC Company Facts. Do not call fundamentals missing just becauseforward_peis still unavailable.
Data Sources
- Yahoo Finance quote API:
/v7/finance/quote - Yahoo Finance chart API:
/v8/finance/chart - Yahoo Finance quoteSummary API:
/v10/finance/quoteSummary - SEC EDGAR Company Facts API:
/api/xbrl/companyfacts/CIK##########.json - Stooq public fallback: daily quote / history CSV endpoints
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
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.

