Syntic

Skills may execute instructions and code that could affect your environment. Marketplace scans reduce risk but do not guarantee safety. Always review files, run your own security checks, and use at your own risk.

TechnicalFree Safe

technical-analyst

Security Scan Summary

Status: Safe

Source: Syntic Skills registry

Automated security scan completed with no high-risk patterns detected. Manual review is still required.

About This Skill

Use when the user provides weekly chart images (stocks, indices, crypto, forex) and requests technical analysis, trend identification, support/resistance levels, or scenario planning.

Downloadable SKILL.md

Download SKILL.md and place it in your Syntic skills folder. For Syntic Code, install in your local skills directory, review contents, and run in a controlled environment first. Acknowledge the risk notice above to enable the download.

SKILL.md
---
name: technical-analyst
description: Use when the user provides weekly chart images (stocks, indices, crypto, forex) and requests technical analysis, trend identification, support/resistance levels, or scenario planning.
category: Technical
version: 1.0.0
tools: []
---

# Technical Analyst

Conduct technical analysis of weekly price charts: identify trends, support and resistance, moving-average relationships, volume patterns, and probabilistic scenarios for future price movement — using only the chart itself, without input from news, fundamentals, or market sentiment.

## When to Use

- The user provides weekly chart images (stocks, indices, crypto, forex) and requests technical analysis
- Trend direction, strength, or potential reversal points need identifying
- Support/resistance levels or key price zones are needed
- Probabilistic scenario planning with specific price targets is requested
- Objective, chart-only analysis is requested (no fundamentals or news)

## Prerequisites

Requires user-provided weekly-timeframe chart images. No external data lookups are needed — analysis is based solely on what's visible in the chart.

## Output

Return the analysis as a structured chat report (not a saved file): trend, support/resistance levels, moving-average analysis, volume, chart patterns, and 2-4 probabilistic scenarios with price targets and invalidation levels.

## Core Principles

1. **Pure chart analysis** — base every conclusion exclusively on technical data visible in the chart
2. **Systematic approach** — follow the same structured methodology for every chart
3. **Objective assessment** — avoid subjective bias; focus on observable patterns and data
4. **Probabilistic scenarios** — express future possibilities as probability-weighted scenarios, not single predictions
5. **Sequential processing** — analyze and write up each chart individually before moving to the next

## Analysis Methodology

### Step 1 — Receive Chart Images

Confirm receipt of all chart images, note how many charts need analysis, note any focus areas the user specifies, then analyze charts sequentially, one at a time.

### Step 2 — Load Technical Analysis Framework

Before analyzing, apply the technical analysis framework below systematically to every chart — it governs trend classification, support/resistance identification, moving-average interpretation, volume analysis, chart-pattern recognition, and scenario/probability assignment. Treat it as the fixed methodology for every analysis, not an optional reference.

### Step 3 — Analyze Each Chart Systematically

**3.1 Trend analysis** — direction (up/down/sideways), strength (strong/moderate/weak), duration and exhaustion signals, higher-highs/higher-lows vs. lower-highs/lower-lows structure.

**3.2 Support and resistance** — mark significant horizontal support and resistance, trendline support/resistance, any support-resistance role reversals, and confluence zones where multiple levels align.

**3.3 Moving average analysis** — price position relative to the 20-week, 50-week, and 200-week moving averages; MA alignment (bullish/bearish/neutral configuration); MA slope; recent or pending crossovers; MAs acting as dynamic support/resistance.

**3.4 Volume analysis** — overall volume trend, volume spikes and their context (at support/resistance, on breakouts), volume confirmation vs. divergence from price, any climax or exhaustion patterns.

**3.5 Chart patterns and price action** — reversal patterns (hammers, shooting stars, engulfing patterns), continuation patterns (flags, triangles), notable candlestick formations, recent breakouts or breakdowns.

**3.6 Synthesize** — integrate every element above into one coherent current assessment, identify the most significant factors, flag conflicting signals or ambiguity, and establish the key levels that will determine future direction.

### Step 4 — Develop Probabilistic Scenarios

Build 2-4 distinct scenarios per chart. Each scenario needs: a clear descriptive name (e.g., "Bull Case: Breakout Above Resistance"), a probability estimate (all scenarios for one chart must sum to 100%), a description of how it would unfold, at least 2-3 supporting technical factors, target price levels, and an invalidation level that would negate the scenario.

**Typical Scenario Framework:**
- **Base Case (40-60%)** — the most likely outcome given current structure
- **Bull Case (20-40%)** — optimistic scenario requiring an upside breakout
- **Bear Case (20-40%)** — pessimistic scenario requiring a downside breakdown
- **Alternative Scenario (5-15%)** — lower-probability but technically plausible outcome

Adjust these ranges based on the strength of the supporting technical factors for the specific chart, and always keep the total at 100%.

### Step 5 — Generate the Analysis Report

For each chart, return a report covering: chart overview, trend analysis, support/resistance levels, moving-average analysis, volume analysis, chart patterns and price action, current market assessment, scenario analysis (2-4 scenarios with probabilities), summary, and a disclaimer that this is chart-based analysis, not financial advice.

### Step 6 — Repeat for Multiple Charts

Complete the full workflow (Steps 3-5) for one chart, deliver that report, then move to the next chart. Don't batch analyses — finish and deliver each one before starting the next.

## Quality Standards

**Objectivity** — base analysis strictly on observable chart data; don't incorporate news, fundamentals, or sentiment; avoid subjective language ("I think," "I feel"); state uncertainty clearly when signals are ambiguous; present both bullish and bearish possibilities to avoid confirmation bias.

**Completeness** — cover every section of the report; give specific price levels for support, resistance, and targets, not vague descriptions; justify probability estimates with technical factors; include an invalidation level for every scenario.

**Clarity** — use precise technical terminology; write in clear, professional language; make scenarios distinct and mutually exclusive.

## Example Usage

**Single chart:** User provides one weekly chart and asks for analysis → confirm receipt → apply the technical analysis framework → run the full systematic analysis (trend, S/R, MA, volume, patterns) → develop 3 scenarios with probabilities (e.g., 55% bullish continuation, 30% consolidation, 15% reversal) → deliver the complete report.

**Multiple charts:** User provides three charts (e.g., Bitcoin, Ethereum, Nasdaq) → confirm receipt of all three → analyze and deliver the first chart's full report → repeat for the second and third → confirm all three are complete.

**Focused request:** User asks specifically whether a stock will break above resistance → run the full systematic analysis, but weight the write-up toward resistance levels and breakout probability, with scenario probabilities driven by volume, trend strength, and proximity to resistance.

Bundle Download

Includes SKILL.md and bundled support files where provided. Risk acknowledgement is required.

Install Targets

Syntic App

  1. 1. Create a dedicated folder for this skill in your local skills library.
  2. 2. Place SKILL.md into that folder.
  3. 3. Restart Syntic and invoke this skill on matching tasks.

Syntic Code (CLI)

  1. 1. Save SKILL.md in your local Syntic Code skills directory.
  2. 2. Keep related files in the same skill folder.
  3. 3. Run in a safe environment and validate outputs.

Source

https://github.com/tradermonty/claude-trading-skills/blob/main/skills/technical-analyst/SKILL.md

Open Source Link
Technical

Related Skills