Agent skill

finviz-screener

Build and open FinViz screener URLs from natural language requests. Use when user wants to screen stocks, find stocks matching criteria, filter by fundamentals or technicals, or asks to open FinViz with specific conditions. Supports both Japanese and English input (e.g., "高配当で成長している小型株を探したい", "Find oversold large caps with high ROE").

BaggaT236github.com/BaggaT236GitHub ↗
claude-codeships scriptsMIT
Install
npx skills add BaggaT236/AI-Trading-Skills --skill finviz-screener --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 5
SKILL.md size: 12 KB
Bundled scripts: yes
Path: skills/finviz-screener/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 118
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# FinViz Screener ## Overview Translate natural-language stock screening requests into FinViz screener filter codes, build the URL, and open it in Chrome. No API key required for public screener; FINVIZ Elite is auto-detected from `$FINVIZ_API_KEY` for enhanced functionality. **Key Features:** - Natural language → filter code mapping (Japanese + English) - URL construction with view type and sort order selection - Elite/Public auto-detection (environment variable or explicit flag) - Chrome-first browser opening with OS-appropriate fallbacks - Strict filter validation to prevent URL injection --- ## When to Use This Skill **Explicit Triggers:** - "高配当で成長している小型株を探したい" - "Find oversold large caps near 52-week lows" - "テクノロジーセクターの割安株をスクリーニングしたい" - "Screen for stocks with insider buying" - "FinVizでブレイクアウト候補を表示して" - "Show me high-growth small caps on FinViz" - "配当利回り5%以上でROE15%以上の銘柄を探して" **Implicit Triggers:** - User describes stock screening criteria using fundamental or technical terms - User mentions FinViz screener or stock filtering - User asks to find stocks matching specific financial characteristics **When NOT to Use:** - Deep fundamental analysis of a specific stock (use us-stoc

What's inside
Steps it walks through
  1. Overview
  2. When to Use This Skill
  3. Workflow
  4. Step 1: Load Filter Reference
  5. Step 2: Interpret User Request
  6. Step 3: Present Filter Selection
  7. Step 4: Execute Script
  8. Step 5: Report Results
  9. Usage Recipes
  10. Recipe 1: High-Dividend Growth Stocks (Kanchi-Style)
  11. Recipe 2: Minervini Trend Template + VCP
  12. Recipe 3: Unfairly Sold-Off Growth Stocks
  13. Recipe 4: Turnaround Stocks
  14. Recipe 5: Momentum Trade Candidates
Ships with 4 files
  • references/finviz_screener_filters.md
  • scripts/open_finviz_screener.py
  • scripts/tests/conftest.py
  • scripts/tests/test_open_finviz_screener.py
Commands it runs
cat references/finviz_screener_filters.md
python3 scripts/open_finviz_screener.py \
Theme-only screening (no --filters required)
Theme + sub-theme + filters combined
More from AI-Trading-Skills
All skills →
About this skill
What does the finviz-screener skill do?

Build and open FinViz screener URLs from natural language requests. Use when user wants to screen stocks, find stocks matching criteria, filter by fundamentals or technicals, or asks to open FinViz with specific conditions. Supports both Japanese and English input (e.g., "高配当で成長している小型株を探したい", "Find oversold large caps with high ROE").

How do I install it?

Run `npx skills add BaggaT236/AI-Trading-Skills --skill finviz-screener --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BaggaT236/AI-Trading-Skills, a repository with 118 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going