technical-analyst
Skill75 starsChanged 8 months agoMITView on GitHub
This 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 levels, scenario planning, or probability assessments based purely on chart data without consideration of news or fundamental factors.
4 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- IngAs8/ClaudeSkilledited, first seen Sep 28, 2026
- hanlinlibham/skillsedited, first seen Jul 4, 2026
- finskills/technical-analysttheir own version, first seen May 4, 2026
- cooragent/ClarityFinancetheir own version, first seen Jan 19, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- hanlinlibham/skills★ 280% same
- IngAs8/ClaudeSkill★ 080% same
Wrote their own version · 2
- cooragent/ClarityFinance★ 62same name
- finskills/technical-analyst★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository9 other files it gives its agents.
- backtest-expertSkill
- fii-dii-flow-trackerSkill
- india-market-breadthSkill
- india-news-trackerSkill
- india-stock-analysisSkill
- nse-vcp-screenerSkill
- options-strategy-advisorSkill
- scenario-analyzerSkill
- weekly-fno-trade-plannerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 11 are common, 2 are distinctive, and 0 are very specific to this project.
11
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Currency: All analysis in INR (₹)
- Common: line 24
Systematic Approach: Follow a structured methodology for each chart analysis
- Common: line 25
Objective Assessment: Avoid subjective bias; focus on observable patterns and data
- Common: line 33
When the user provides one or more weekly chart images for analysis:
- Common: line 42
Before beginning analysis, read the comprehensive technical analysis methodology:
- Common: line 85
Check for volume confirmation or divergence with price
- Distinctive: line 87
Consider delivery volume patterns if visible (higher delivery % = stronger conviction)
- Common: line 136
If multiple charts are provided:
- Common: line 143
Do not batch analyses. Complete and save each report before moving to the next chart.
- Common: line 150
Avoid incorporating external information (news, fundamentals, sentiment)
- Common: line 151
Do not use subjective language like "I think" or "I feel"
- Common: line 165
Use precise technical terminology correctly
- Common: line 166
Write in clear, professional language
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Technical Analyst (India Markets)
Overview
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.
Indian Market Context
- Trading Hours: NSE/BSE operate 9:15 AM – 3:30 PM IST (Monday–Friday)
- Key Indices: Nifty 50, Bank Nifty, Nifty IT, Nifty Pharma, Sensex
- Circuit Limits: Individual stocks have daily upper/lower circuit limits (2%, 5%, 10%, 20%) which can affect pattern interpretation
- Settlement: T+1 settlement for equities
- F&O Expiry: Weekly (Thursday) for index options, monthly for stock options
- Currency: All analysis in INR (₹)
Core Principles
- Pure Chart Analysis: Base all conclusions exclusively on technical data visible in the chart
- Systematic Approach: Follow a structured methodology for each chart analysis
- Objective Assessment: Avoid subjective bias; focus on observable patterns and data
- Probabilistic Scenarios: Express future possibilities as probability-weighted scenarios
- 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:
- Confirm receipt of all chart images
- Identify the number of charts to analyze
- Note any specific focus areas requested by the user
- Proceed to analyze charts sequentially, one at a time
Step 2: Load Technical Analysis Framework
Before beginning analysis, read the comprehensive technical analysis methodology:
Read: references/technical_analysis_framework.mdThis 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
- Note proximity to circuit limit levels for individual stocks
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
- Consider delivery volume patterns if visible (higher delivery % = stronger conviction)
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:
- Scenario Name: Clear, descriptive title (e.g., "Bull Case: Breakout Above Resistance")
- Probability Estimate: Percentage likelihood based on technical factors (must sum to 100% across all scenarios)
- Description: What this scenario entails and how it would unfold
- Supporting Factors: Technical evidence supporting this scenario (minimum 2-3 factors)
- Target Levels: Expected price levels if scenario plays out
- 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
Step 5: Generate Analysis Report
For each chart analyzed, create a comprehensive markdown report using the template structure:
Read and use as template: assets/analysis_template.mdFile Naming Convention: Save each analysis as [SYMBOL]_technical_analysis_[YYYY-MM-DD].md
Example: NIFTY50_technical_analysis_2026-03-12.md
Step 6: Repeat for Multiple Charts
If multiple charts are provided:
- Complete the full analysis workflow (Steps 3-5) for the first chart
- Save the analysis report
- Proceed to the next chart
- 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 (in ₹)
- 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
User: "Please analyze this weekly chart of Nifty 50"
[Provides chart image]
Analyst:
1. Confirms receipt of chart image
2. Reads technical_analysis_framework.md for methodology
3. Conducts systematic analysis (trend, S/R, MA, volume, patterns)
4. Develops 3 scenarios with probabilities
5. Generates comprehensive analysis report using template
6. Saves as NIFTY50_technical_analysis_2026-03-12.mdExample 2: Multiple Chart Analysis
User: "Analyze these three charts: Reliance, HDFC Bank, and Bank Nifty"
[Provides 3 chart images]
Analyst:
1. Confirms receipt of 3 charts
2. Reads technical_analysis_framework.md
3. Analyzes Reliance chart → Generates report → Saves as RELIANCE_technical_analysis_2026-03-12.md
4. Analyzes HDFC Bank chart → Generates report → Saves as HDFCBANK_technical_analysis_2026-03-12.md
5. Analyzes Bank Nifty chart → Generates report → Saves as BANKNIFTY_technical_analysis_2026-03-12.md
6. Notifies user that all three analyses are completeExample 3: Focused Analysis Request
User: "I'm particularly interested in whether TCS will break above resistance. Analyze the chart."
[Provides chart image]
Analyst:
1. Conducts full systematic analysis
2. Pays special attention to resistance levels and breakout probability
3. Develops scenarios with emphasis on breakout vs. rejection possibilities
4. Assigns probabilities based on volume, trend strength, and proximity to resistance
5. Generates complete report with focused scenario analysisResources
references/technical_analysis_framework.md
Comprehensive methodology for technical analysis including:
- Trend analysis criteria and classification
- Support and resistance identification techniques
- Moving average interpretation guidelines
- Volume analysis principles (including delivery volume context for Indian markets)
- Chart pattern recognition
- Scenario development and probability assignment framework
- Indian market specific considerations (circuit limits, F&O expiry effects)
assets/analysis_template.md
Structured template for technical analysis reports with all required sections.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

