finviz-screener

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-stock-analysis)
• Portfolio review with holdings (use portfolio-manager)
• Chart pattern analysis on images (use technical-analyst)
• Earnings-based screening (use earnings-trade-analyzer or pead-screener)

---

Workflow

Step 1: Load Filter Reference

Read the filter knowledge base:

cat references/finviz_screener_filters.md

Step 2: Interpret User Request

Map the user's natural-language request to FinViz filter codes. Use the Common Concept Mapping table below for quick translation, and reference the full filter list for precise code selection.

Note: For range criteria (e.g., "dividend 3-8%", "P/E between 10 and 20"), use the {from}to{to} range syntax as a single filter token (e.g., fa_div_3to8, fa_pe_10to20) instead of combining separate _o and _u filters.