Technical Analyst
Use this skill for chart-only technical analysis. It is optimized for weekly charts.
Workflow
- Confirm the chart context:
- symbol
- timeframe
- date range
- visible indicators
- whether volume is shown
- If the chart is unclear, say so and lower confidence or stop.
- Read references/technical_analysis_framework.md.
- Analyze in this order:
- trend
- support / resistance
- EMAs or MAs
- RSI
- Fibonacci levels
- fair value gaps
- volume
- chart patterns, candlestick patterns, and price action
- Use zones instead of false precision when levels are approximate.
- Use indicators only when they are visible on the chart. If they are not shown, mark them
Not shownorUnavailable. - If a chart or candlestick pattern is visible, name it explicitly and state:
- whether it is bullish, bearish, or neutral
- what it could mean if confirmed
- what would confirm it
- what would weaken or invalidate it
- If no credible pattern is visible, say
No clear chart or candlestick pattern. - Build 2-4 scenarios with:
- probability
- trigger
- target
- invalidation
- Write the result with assets/analysis_template.md.
Rules
- Use only chart data. No news, no fundamentals, no sentiment.
- Default to latest visible chart context unless the user explicitly asks for historical-only analysis.
- Do not claim price action that is not visibly plotted on the provided chart.
- If quote widgets or side panels show values not represented by visible candles, label them as
quote fieldand do not treat them as confirmed candle closes. - If the user asks for
current/right nowand the chart is ambiguous, request a refreshed chart or explicit timestamp before making intraday claims. - Distinguish visible facts from inference.
- Keep confidence tied to signal alignment and chart quality.
- Make bullish and bearish paths explicit.
- Do not batch multiple charts into one blended analysis.
- Use EMAs or MAs, RSI, Fibonacci, and fair value gaps as core indicators when the chart supports them.
- Call out notable chart patterns and candlestick patterns when they are actually visible.
- For every named pattern, explain what it could mean in context instead of listing the label alone.
- Do not force a pattern match when the structure is incomplete, ambiguous, or cropped.