This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance levels, scenario planning, or probability assessments

Technical Analyst Overview This skill enables comprehensive technical analysis of weekly price charts. Analyze chart images to identify trends, support and resistance levels, moving average relationships, volume patterns, and develop probabilistic scenarios for future price movement. All analysis is conducted objectively using only chart data, without influence from news, fundamentals, or market sentiment. When to Use User provides weekly chart images (stocks, indices, crypto, forex) and requests technical analysis Need to identify trend direction, strength, and potential reversal points Looking for support/resistance levels and key price zones Want probabilistic scenario planning with specific price targets Require objective chart based analysis without fundamental or news considerations Prerequisites Chart Images : User must provide weekly timeframe chart images for analysis No API Keys Required : This skill analyzes user provided images; no external data fetches Output This skill generates markdown analysis reports saved to the reports/ directory: File format : [SYMBOL] technical analysis [YYYY MM DD].md Content : Comprehensive analysis including trend, S/R levels, MA analysis, volume, patterns, and 2 4 probabilistic scenarios with targets and invalidation levels Core Principles 1. Pure Chart Analysis : Base all conclusions exclusively on technical data visible in the chart 2. Systematic Approach : Follow a structured methodology for each chart analysis 3. Objective Assessment : Avoid subjective bias; focus on observable patterns and data 4. Probabilistic Scenarios : Express future possibilities as probability weighted scenarios 5. Sequential Processing : Analyze each chart individually and document findings immediately Analysis Workflow Step 1: Receive Chart Images When the user provides one or more weekly chart images for analysis: 1. Confirm receipt of all chart images 2. Identify the number of charts to analyze 3. Note any specific focus areas requested by the user 4. Proceed to analyze charts sequentially, one at a time Step 2: Load Technical Analysis Framework Before beginning analysis, read the comprehensive technical analysis methodology: This reference contains detailed guidance on: Trend analysis and classification Support and resistance identification Moving average interpretation Volume analysis Chart patterns and candlestick analysis Scenario development and probability assignment Analysis discipline and objectivity Step 3: Analyze Each Chart Systematically For each chart image, conduct a systematic analysis following this sequence: 3.1 Trend Analysis Identify trend direction (uptrend, downtrend, sideways) Assess trend strength (strong, moderate, weak) Note trend duration and potential exhaustion signals Examine higher highs/lows or lower highs/lows pattern 3.2 Support and Resistance Analysis Mark significant horizontal support levels Mark significant horizontal resistance levels Identify trendline support/resistance Note any support resistance role reversals Assess confluence zones where multiple S/R levels align 3.3 Moving Average Analysis Determine price position relative to 20 week, 50 week, and 200 week MAs Assess MA alignment (bullish, bearish, or neutral configuration) Note MA slope (rising, falling, flat) Identify any recent or pending MA crossovers Observe MAs acting as dynamic support or resistance 3.4 Volume Analysis Assess overall volume trend (increasing, decreasing, stable) Identify volume spikes and their context (at support/resistance, on breakouts) Check for volume confirmation or divergence with price Note any volume climax or exhaustion patterns 3.5 Chart Patterns and Price Action Identify any reversal patterns (hammers, shooting stars, engulfing patterns, etc.) Identify any continuation patterns (flags, triangles, etc.) Note significant candlestick formations Observe recent breakouts or breakdowns 3.6 Synthesize Observations Integrate all technical elements into coherent current assessment Identify the most significant factors influencing the chart Note any conflicting signals or ambiguity Establish key levels that will determine future direction Step 4: Develop Probabilistic Scenarios For each analyzed chart, create 2 4 distinct scenarios for future price movement: Scenario Structure Each scenario must include: 1. Scenario Name : Clear, descriptive title (e.g., "Bull Case: Breakout Above Resistance") 2. Probability Estimate : Percentage likelihood based on technical factors (must sum to 100% across all scenarios) 3. Description : What this scenario entails and how it would unfold 4. Supporting Factors : Technical evidence supporting this scenario (minimum 2 3 factors) 5. Target Levels : Expected price levels if scenario plays out 6. Invalidation Level : Specific price level that would negate this scenario Typical Scenario Framework Base Case Scenario (40 60%) : Most likely outcome based on current structure Bull Case Scenario (20 40%) : Optimistic scenario requiring upside breakout Bear Case Scenario (20 40%) : Pessimistic scenario requiring downside breakdown Alternative Scenario (5 15%) : Lower probability but technically plausible outcome Adjust probabilities based on strength of supporting technical factors. Ensure probabilities are realistic and sum to 100%. Step 5: Generate Analysis Report For each chart analyzed, create a comprehensive markdown report using the template structure: The report must include all sections: 1. Chart Overview 2. Trend Analysis 3. Support and Resistance Levels 4. Moving Average Analysis 5. Volume Analysis 6. Chart Patterns and Price Action 7. Current Market Assessment 8. Scenario Analysis (2 4 scenarios with probabilities) 9. Summary 10. Disclaimer File Naming Convention : Save each analysis as [SYMBOL] technical analysis [YYYY MM DD].md Example: SPY technical analysis 2025 11 02.md Step 6: Repeat for Multiple Charts If multiple charts are provided: 1. Complete the full analysis workflow (Steps 3 5) for the first chart 2. Save the analysis report 3. Proceed to the next chart 4. Repeat until all charts have been analyzed and documented Do not batch analyses. Complete and save each report before moving to the next chart. Quality Standards Objectivity Requirements Base all analysis strictly on observable chart data Avoid incorporating external information (news, fundamentals, sentiment) Do not use subjective language like "I think" or "I feel" Express uncertainty clearly when signals are ambiguous Present both bullish and bearish possibilities to avoid confirmation bias Completeness Requirements Address all sections of the analysis template Provide specific price levels for support, resistance, and targets Justify probability estimates with technical factors Include invalidation levels for each scenario Note any limitations or caveats to the analysis Clarity Requirements Use precise technical terminology correctly Write in clear, professional language Structure information logically Include specific price levels (not vague descriptions) Make scenarios distinct and mutually exclusive Example Usage Scenarios Example 1: Single Chart Analysis Example 2: Multiple Chart Analysis Example 3: Focused Analysis Request Contrarian Confirmation Mode (Shapiro Step 3) This is an ADDITIVE mode, separate from the pure chart analysis workflow above. It activates only on an explicit contrarian confirmation request — typically after cot contrarian detector (step 1) has flagged a market crowded and, optionally, news reaction failure analyzer (step 2) has shown it failed to react to favorable news. A plain "analyze this chart" request still runs the original workflow (Steps 1 6 above) unchanged. Purpose Confirm whether the WEEKLY chart is showing price action evidence that a crowded market is reversing: a weekly key reversal, an intraweek failed extreme, or a confirmed then rejected failed breakout — vetoed by a continuation check (a new closing extreme in the crowd's direction more recent than any signal found). See references/contrarian confirmation checklist.md for the full, word for word methodology shared by both chart mode and script mode. Inputs Crowd direction : CROWDED LONG or CROWDED SHORT — from the user, or from a prior cot contrarian detector report. Chart image (primary) : a user supplied weekly chart, read the same way as the existing workflow, using the strict definitions below. Script fallback (data driven) : scripts/check weekly price action.py when no chart is supplied, or when an auditable, deterministic result is wanted instead of (or alongside) a visual read. The Three Checks + Swing Levels 1. Weekly key reversal : a new swing lookback extreme (default 13 weeks) followed by a close through the prior week's opposite level. 2. Failed extreme : an intraweek poke past the prior extreme lookback level (default 52 weeks) that closes back through it the same week. 3. Failed breakout : a weekly CLOSING breakout past the prior extreme lookback level, rejected (closed back through) within <=3 subsequent weeks — week of is the FAILURE week, never the breakout week. 4. Continuation veto : a new CLOSING extreme in the crowd's direction, strictly more recent than the newest triggered signal above, vetoes confirmation regardless of what triggered. 5. Swing levels : the nearest fractal swing high/low (5 week pivot, with a documented fallback) supplies stop reference — the nearest swing high when fading a crowded LONG, the nearest swing low when fading a crowded SHORT. Every comparison is a STRICT inequality; window truncation is per evaluated week, not per run. Full definitions, the direction mirror table, worked examples, and the confidence HIGH rule are in references/contrarian confirmation checklist.md — read it before producing a chart mode verdict, so chart and script judge identically. Output Contract Invariant : checks (and swing levels ) is null whenever verdict: INSUFFICIENT DATA — regardless of the specific reason ( no price source , insufficient weekly bars , a detector json refusal, ...). A downstream consumer can check verdict alone before deciding whether checks. is safe to read, without branching on verdict reason . File naming : ta confirmation <SYMBOL <as of .json and ta confirmation <SYMBOL <as of .md , saved to reports/ . Chart Primary, Script Fallback Chart images remain the PRIMARY input, consistent with this skill's identity. Run the script instead of (or alongside) a chart read when no chart is supplied, or when an auditable, deterministic result is preferred: Or resolve direction from a cot contrarian detector report directly: The script fetches weekly resampled OHLC via a documented futures to ETF fallback chain (see the module docstring in scripts/check weekly price action.py ), truncates daily bars to as of BEFORE resampling (no lookahead), and fails closed to INSUFFICIENT DATA — never a crash — on an unreadable (missing file), syntactically invalid, stale, or structurally malformed detector json , too little price history ( min weeks , default 30), or no usable price source. Conservative Disagreement Rule If both chart mode and script mode produce a result for the same symbol/direction and their verdicts DISAGREE, the final verdict is NOT CONFIRMED ( verdict reason: mode disagreement ), with both sub results attached for review — never silently prefer one mode. If one mode is INSUFFICIENT DATA and the other is a clean verdict, the clean verdict stands. Guardrails Verdict only — never a trade recommendation on its own. This confirms step 3 of 5 (Shapiro's process). Entry and

technical-analyst