technical-analyst
starsforks
How to install technical-analyst?
ajeeshworkspace/indian-trading-skills/technical-analyst
$npx -y skills add ajeeshworkspace/indian-trading-skills --skill technical-analystThis skill should be used when analyzing weekly price charts for Indian stocks (NSE/BSE), indices (Nifty 50, Bank Nifty, Sensex), or any other instrument. Use this skill when the user provides chart images and requests technical analysis, trend identification, support/resistance
SKILL.md
| 1 | # Technical Analyst (India Markets) |
| 2 | |
| 3 | ## Overview |
| 4 | |
| 5 | This skill enables comprehensive technical analysis of weekly price charts for Indian market instruments. 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. |
| 6 | |
| 7 | ## Indian Market Context |
| 8 | |
| 9 | - **Trading Hours**: NSE/BSE operate 9:15 AM – 3:30 PM IST (Monday–Friday) |
| 10 | - **Key Indices**: Nifty 50, Bank Nifty, Nifty IT, Nifty Pharma, Sensex |
| 11 | - **Circuit Limits**: Individual stocks have daily upper/lower circuit limits (2%, 5%, 10%, 20%) which can affect pattern interpretation |
| 12 | - **Settlement**: T+1 settlement for equities |
| 13 | - **F&O Expiry**: Weekly (Thursday) for index options, monthly for stock options |
| 14 | - **Currency**: All analysis in INR (₹) |
| 15 | |
| 16 | ## Core Principles |
| 17 | |
| 18 | 1. **Pure Chart Analysis**: Base all conclusions exclusively on technical data visible in the chart |
| 19 | 2. **Systematic Approach**: Follow a structured methodology for each chart analysis |
| 20 | 3. **Objective Assessment**: Avoid subjective bias; focus on observable patterns and data |
| 21 | 4. **Probabilistic Scenarios**: Express future possibilities as probability-weighted scenarios |
| 22 | 5. **Sequential Processing**: Analyze each chart individually and document findings immediately |
| 23 | |
| 24 | ## Analysis Workflow |
| 25 | |
| 26 | ### Step 1: Receive Chart Images |
| 27 | |
| 28 | When the user provides one or more weekly chart images for analysis: |
| 29 | |
| 30 | 1. Confirm receipt of all chart images |
| 31 | 2. Identify the number of charts to analyze |
| 32 | 3. Note any specific focus areas requested by the user |
| 33 | 4. Proceed to analyze charts sequentially, one at a time |
| 34 | |
| 35 | ### Step 2: Load Technical Analysis Framework |
| 36 | |
| 37 | Before beginning analysis, read the comprehensive technical analysis methodology: |
| 38 | |
| 39 | ``` |
| 40 | Read: references/technical_analysis_framework.md |
| 41 | ``` |
| 42 | |
| 43 | This reference contains detailed guidance on: |
| 44 | - Trend analysis and classification |
| 45 | - Support and resistance identification |
| 46 | - Moving average interpretation |
| 47 | - Volume analysis |
| 48 | - Chart patterns and candlestick analysis |
| 49 | - Scenario development and probability assignment |
| 50 | - Analysis discipline and objectivity |
| 51 | |
| 52 | ### Step 3: Analyze Each Chart Systematically |
| 53 | |
| 54 | For each chart image, conduct a systematic analysis following this sequence: |
| 55 | |
| 56 | #### 3.1 Trend Analysis |
| 57 | - Identify trend direction (uptrend, downtrend, sideways) |
| 58 | - Assess trend strength (strong, moderate, weak) |
| 59 | - Note trend duration and potential exhaustion signals |
| 60 | - Examine higher highs/lows or lower highs/lows pattern |
| 61 | |
| 62 | #### 3.2 Support and Resistance Analysis |
| 63 | - Mark significant horizontal support levels |
| 64 | - Mark significant horizontal resistance levels |
| 65 | - Identify trendline support/resistance |
| 66 | - Note any support-resistance role reversals |
| 67 | - Assess confluence zones where multiple S/R levels align |
| 68 | - Note proximity to circuit limit levels for individual stocks |
| 69 | |
| 70 | #### 3.3 Moving Average Analysis |
| 71 | - Determine price position relative to 20-week, 50-week, and 200-week MAs |
| 72 | - Assess MA alignment (bullish, bearish, or neutral configuration) |
| 73 | - Note MA slope (rising, falling, flat) |
| 74 | - Identify any recent or pending MA crossovers |
| 75 | - Observe MAs acting as dynamic support or resistance |
| 76 | |
| 77 | #### 3.4 Volume Analysis |
| 78 | - Assess overall volume trend (increasing, decreasing, stable) |
| 79 | - Identify volume spikes and their context (at support/resistance, on breakouts) |
| 80 | - Check for volume confirmation or divergence with price |
| 81 | - Note any volume climax or exhaustion patterns |
| 82 | - Consider delivery volume patterns if visible (higher delivery % = stronger conviction) |
| 83 | |
| 84 | #### 3.5 Chart Patterns and Price Action |
| 85 | - Identify any reversal patterns (hammers, shooting stars, engulfing patterns, etc.) |
| 86 | - Identify any continuation patterns (flags, triangles, etc.) |
| 87 | - Note significant candlestick formations |
| 88 | - Observe recent breakouts or breakdowns |
| 89 | |
| 90 | #### 3.6 Synthesize Observations |
| 91 | - Integrate all technical elements into coherent current assessment |
| 92 | - Identify the most significant factors influencing the chart |
| 93 | - Note any conflicting signals or ambiguity |
| 94 | - Establish key levels that will determine future direction |
| 95 | |
| 96 | ### Step 4: Develop Probabilistic Scenarios |
| 97 | |
| 98 | For each analyzed chart, create 2-4 distinct scenarios for future price movement: |
| 99 | |
| 100 | #### Scenario Structure |
| 101 | |
| 102 | Each scenario must include: |
| 103 | 1. **Scenario Name**: Clear, descriptive title (e.g., "Bull Case: Breakout Above Resistance") |
| 104 | 2. **Probability Estimate**: Percentage likelihood based on technical factors (must sum to 100 |
People who liked this also viewed
6 picksType
- azure-costAzure cost management: query costs, forecast spending, optimize to reduce waste. WHEN: \"Azure costs\", \"Azure bill\", \"cost breakdown\", \"how much am I spending\", \"forecast spending\", \"optimizSkillsJul 2026
- pricingWhen the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increaseSkillsJul 2026
- stripe-integrationMulti-harness agentic plugin marketplace for Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, and Gemini CLISkillsJul 2026
- startup-financial-modelingMulti-harness agentic plugin marketplace for Claude Code, Codex CLI, Cursor, OpenCode, GitHub Copilot, and Gemini CLISkillsJul 2026
- tushare-finance专为 Claude Code 设计的 Tushare Pro 金融数据技能包，支持 220+ 个接口，用自然语言获取 A 股行情、财务数据、宏观经济等金融数据。SkillsJul 2026
- azure-pricingFetches real-time Azure retail pricing using the Azure Retail Prices API (prices.azure.com) and estimates Copilot Studio agent credit consumption. Use when the user asks about the cost of any Azure seSkillsJul 2026
