메뉴
Daily morning scan — load saved morning layout, screenshot watchlist symbols, and summarize overnight pre-market state. Use when the user says "good morning", "morning prep", or asks for a pre-open briefing.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | morning-prep |
| description | Daily morning scan — load saved morning layout, screenshot watchlist symbols, and summarize overnight pre-market state. Use when the user says "good morning", "morning prep", or asks for a pre-open briefing. |
You are running the user's daily pre-market routine on TradingView.
watchlist_get — read the active watchlist symbolswatchlist_import (they may have a JSON backup saved from a prior watchlist_export)Example watchlist: ["ES1!", "NQ1!", "CL1!", "GC1!", "DXY", "BTCUSD"].
state_list — check for a snapshot tagged "morning" or similarstate_restore with that snapshot id — this brings back the user's preferred indicators, drawings, timeframe, and chart typestate_snapshot with tag "morning" at the endIf state_restore fails with CHART_LOADING, wait ~2s and retry once.
Use batch_run with action: "screenshot" and the full symbol list. This captures each symbol without manual chart_set_symbol loops.
batch_run({ symbols: <watchlist>, action: "screenshot" })
Screenshots save to screenshots/ with timestamps — reference them in the summary.
Pick the 5 most-relevant symbols (user's main instruments, e.g., ES1!, NQ1!, CL1!, GC1!, BTCUSD). For each:
chart_set_symbol — switch the chartdata_get_ohlcv with summary: true — compact stats (overnight high/low, range, change%)quote_get — live price snapshotKeep OHLCV summary-only to avoid context bloat (see CLAUDE.md context rules).
For the top-5 only:
data_get_study_values — RSI, MACD, EMAs currently on chartdata_get_pine_labels with study_filter if the user runs a custom profiler (e.g., "Profiler", "Session Stats")If data_get_indicator is needed and returns source: "dom_fallback", note that inputs were read from DOM (less reliable than API) — flag any suspicious readings.
Produce a compact briefing:
data_get_pine_lines if a levels indicator is loadedalert_list to cross-reference)Offer to state_snapshot with tag morning-<date> so today's layout is reproducible tomorrow. If the user added throwaway drawings while prepping, draw_clear them before snapshotting.
Analyze a chart — set up symbol/timeframe, add indicators, scroll to key dates, annotate, and screenshot. Use when the user wants technical analysis or chart review.
Post-trade review — pull losing trades from the strategy tester, screenshot each entry in context, and cluster common failure patterns. Use when the user asks "why am I losing?", "review my losses", or "what's wrong with my strategy?".
Cross-asset reasoning across a multi-pane layout — set a 2x2 grid, assign correlated symbols to each pane, and identify leader/laggard/divergence. Use when the user asks to "compare indices", "watch the complex", or wants correlated-asset reasoning.
Scan multiple symbols for setups, patterns, or strategy performance. Use when comparing across instruments or screening for opportunities.
Full Pine Script development loop — write code, compile, fix errors, iterate. Use when building a new indicator or strategy in TradingView.
Migrate Pine Script v4 / v5 source to v6 — analyze, apply migration rules, compile-check, iterate until clean. Use when the user hands over an older script or asks to "upgrade to v6" / "port this Pine code".