← ClaudeAtlas

quant-stock-polling-traderlisted

Plan, validate, poll, and reconcile deterministic Korean and U.S. stock orders through broker adapters after a frozen quant-stock-technical screen. Use when the user wants a first-hour entry window, Toss Securities or 한국투자증권 (KIS) API integration, secure KIS credential setup, dotenv or OS secret-store resolution, credential status inspection, token authentication checks, paper/shadow/live promotion gates, cross-broker exposure snapshots, position sizing, order-state recovery, or fail-closed automated trading. Never infer missing risk, account, fee, FX, calendar, fractional-share, or broker semantics.
mrcha033/skills · ★ 0 · AI & Automation · score 62
Install: claude install-skill mrcha033/skills
# Quant Stock Polling Trader Keep model calculation and broker mutation separate. Accept only a complete `qta-screen/v1` or exchange-aware `qta-screen/v2` artifact from `$quant-stock-technical`. Require `qta-exposure-snapshot/v2` with explicit exchange membership for a v2 screen. The current v2 universe is qualified from KIS stock-master snapshots, so v2 planning is KIS-only; block Toss until a separate Toss-qualified universe snapshot contract exists. ## KIS credential setup Keep credentials out of chat, plans, receipts, repositories, and shell arguments. Resolve them in this order: 1. existing process environment; 2. an OS secret store that injects process environment; 3. `~/.config/mrcha-skills/secrets.env` as a `0600` fallback. Use separate paper and live values because KIS issues them independently: ```text QTA_KIS_PAPER_APP_KEY QTA_KIS_PAPER_APP_SECRET QTA_KIS_PAPER_ACCOUNT_PREFIX QTA_KIS_PAPER_ACCOUNT_PRODUCT QTA_KIS_LIVE_APP_KEY QTA_KIS_LIVE_APP_SECRET QTA_KIS_LIVE_ACCOUNT_PREFIX QTA_KIS_LIVE_ACCOUNT_PRODUCT QTA_ACCOUNT_BINDING_KEY ``` Legacy process variables `QTA_KIS_APP_KEY`, `QTA_KIS_APP_SECRET`, `QTA_KIS_ACCOUNT_PREFIX`, and `QTA_KIS_ACCOUNT_PRODUCT` take precedence for one-off runtime injection. Override the fallback path with `QTA_SECRETS_FILE` when needed. Never persist an access token in the dotenv file. ### Agent guidance contract When assisting a user with KIS credentials, follow this sequence exactly: 1. Confirm whether the user means `paper` or