technical-analysis
Skill33 starsChanged 35 days agoMITView on GitHub
Use when analyzing price and volume structure. Covers trend identification, support and resistance, volume confirmation, moving-average structure, and the limits of what chart analysis can tell you. Trigger on "look at this chart", "where is support and resistance on spy", "is this stock breaking out". Do not use for market-wide participation internals — see the market-breadth skill.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- staskh/trading_skillstheir own version, first seen Nov 3, 2026
- target1m/traderspy-mcptheir own version, first seen Nov 3, 2026
- Shubhamkumartrichy/claude-trading-skills-indiatheir own version, first seen Nov 1, 2026
- Distilla-AI/distilla-skillstheir own version, first seen Nov 1, 2026
- Serennity007/invest-skilltheir own version, first seen Aug 25, 2026
- qunyou-agent/finance-skillstheir own version, first seen Jul 6, 2026
Used with
Projects with it also use fundamental-analysis and stock-screener.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
iceyccSkillfundamental-analysis
股票基本面分析和选股工具集,支持获取财务指标(PE、PB、ROE、EPS、BPS、资产负债率等)、执行基本面选股策略(格雷厄姆 PB 选股、多因子选股)。用于分析公司基本面、筛选优质股票、执行价值投资策略。当需要获取股票财务指标、进行基本面选股、或执行价值投资策略时使用。
Also in 3 projects that use this
theepanSkillstock-screener
A comprehensive growth stock screening and analysis skill. Use this skill whenever the user asks about growth stocks, stock screening, equity analysis, investment opportunities, stock picks, market trends affecting equities, sector rotation, earnings analysis, revenue growth analysis, or fundamental stock evaluation. Also trigger when the user mentions terms like "high-growth companies", "multibagger", "momentum stocks", "earnings growth", "revenue acceleration", "TAM expansion", "secular trends", "stock watchlist", "portfolio ideas", or asks questions like "what stocks should I look at", "find me growth opportunities", "which companies are benefiting from AI/cloud/EVs", or "analyze this stock's growth potential". This skill combines quantitative financial screening with qualitative trend analysis to deliver institutional-grade growth stock research.
Also in 3 projects that use this
Other versions11 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 11
- staskh/trading_skills★ 405same name
- Shubhamkumartrichy/claude-trading-skills-india★ 56same name
- Bhala-Srinivash/nse-trading-skills★ 36same name
- ishenli/investment-agent★ 10same name
- Distilla-AI/distilla-skills★ 9same name
- qunyou-agent/finance-skills★ 4same name
- kuntal-r-d/my-skills★ 3same name
- target1m/traderspy-mcp★ 3same name
- lin30/claude-skills★ 1same name
- Serennity007/invest-skill★ 0same name
1 more not listed
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 repository137 other files it gives its agents.
- agent-instructionsSkill
- agent-memorySkill
- hooksSkill
- plugin-developmentSkill
- skill-authoringSkill
- skill-reviewSkill
- slash-commandsSkill
- subagentsSkill
- agent-designSkill
- context-engineeringSkill
- fine-tuningSkill
- llm-cost-optimizationSkill
- llm-evaluationSkill
- llm-integrationSkill
- mcp-serverSkill
- ml-pipelineSkill
- model-selectionSkill
- prompt-engineeringSkill
- ragSkill
- structured-outputSkill
- api-designSkill
- background-jobsSkill
- cachingSkill
- djangoSkill
- event-driven-architectureSkill
- fastapiSkill
- graphqlSkill
- microservicesSkill
- nestjsSkill
- realtime-websocketsSkill
- spring-bootSkill
- competitive-analysisSkill
- lead-researchSkill
- product-analysisSkill
- resumeSkill
- user-researchSkill
- database-performanceSkill
- data-modelingSkill
- data-qualitySkill
- pandasSkill
- postgresSkill
- sparkSkill
- brand-guidelinesSkill
- generative-artSkill
- themingSkill
- ui-reviewSkill
- visual-designSkill
- architecture-decisionsSkill
- bug-fix-protocolSkill
- cli-developmentSkill
- code-reviewSkill
- debuggingSkill
- design-patternsSkill
- domain-modelingSkill
- git-workflowSkill
- legacy-modernizationSkill
- refactoringSkill
- repository-explorationSkill
- simple-designSkill
- system-designSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
1
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 14
Read price and volume structure to characterize a trend and identify where a thesis would be proven wrong.
“Common” is measured: kept by at least 6 in 10 of the 7 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 Analysis
Purpose
Read price and volume structure to characterize a trend and identify where a thesis would be proven wrong. Technical analysis describes what price is doing; it does not predict what it will do, and treating it as prediction is where practitioners lose money.
When to Use
- Assessing whether an instrument is trending, ranging, or breaking down.
- Identifying levels for entry, stop, and target.
- Confirming or contradicting a fundamental thesis with price action.
- Reviewing a chart before a trade.
Capabilities
- Trend structure: higher highs and lows, moving-average alignment.
- Support and resistance identification.
- Volume analysis and confirmation.
- Relative strength against a benchmark.
- Common patterns and their actual, unimpressive reliability.
Inputs
- Price and volume history, in sufficient length to see the structure.
- The benchmark, for relative strength.
- The time frame that matches the intended holding period.
Outputs
- A characterization of the trend and its stage.
- Levels: where the structure breaks, where resistance sits.
- An explicit invalidation point.
Workflow
- Establish the trend, on the right time frame — Higher highs and higher lows is an uptrend. The 50-day above the 200-day, both rising, is a confirmed one. Match the time frame to the holding period; a daily chart is irrelevant to a multi-year position.
- Mark the levels that matter — Prior swing highs and lows, and areas where price has repeatedly reversed. A level touched twice is a hypothesis; a level touched four times is a level.
- Check volume — A breakout on below-average volume is a hypothesis without evidence. An advance on declining volume is a warning.
- Measure relative strength — An instrument rising less than its index in an advance is weak, whatever the chart looks like in isolation.
- Define the invalidation before entry — The price at which the read is wrong. This is the stop, and it must be identified before there is money at stake and an incentive to move it.
Best Practices
- Technical analysis is descriptive, not predictive. It tells you what has happened and where you are wrong. Anyone claiming it predicts is selling something.
- Volume is the confirmation. Price can be moved by a small amount of capital; volume cannot be faked.
- The more subjective the pattern, the less reliable it is. Trend and volume are near-objective. A head-and-shoulders is in the eye of the beholder, and the beholder has a position.
- Indicators are transformations of price. A dozen indicators derived from the same price series do not constitute a dozen confirmations — they are one observation, restated.
- The trend in the dominant time frame constrains the smaller ones. Buying a bounce in a confirmed downtrend is fighting the primary trend for a secondary move.
- Backtest any pattern you intend to trade. Most classic patterns perform far worse than their reputation, and several perform no better than random.
Examples
Characterizing structure objectively:
def trend_state(df: pd.DataFrame) -> TrendState:
"""Objective structure: no interpretation, no drawing on charts."""
ma50 = df.close.rolling(50).mean()
ma200 = df.close.rolling(200).mean()
swing_highs = find_swing_highs(df, lookback=10)
swing_lows = find_swing_lows(df, lookback=10)
higher_highs = swing_highs.iloc[-1] > swing_highs.iloc[-2]
higher_lows = swing_lows.iloc[-1] > swing_lows.iloc[-2]
return TrendState(
structure=(
"uptrend" if higher_highs and higher_lows else
"downtrend" if not higher_highs and not higher_lows else
"range"
),
ma_aligned=bool(ma50.iloc[-1] > ma200.iloc[-1] and ma200.diff().iloc[-1] > 0),
above_ma50=bool(df.close.iloc[-1] > ma50.iloc[-1]),
# The invalidation level: below the last higher low, the uptrend structure
# is broken by definition. This is the stop, and it was chosen by the
# structure rather than by how much loss feels tolerable.
invalidation=float(swing_lows.iloc[-1]),
# Volume confirmation on the most recent advance.
volume_confirms=bool(
df.volume.iloc[-5:].mean() > df.volume.iloc[-50:].mean() * 1.2
and df.close.iloc[-1] > df.close.iloc[-5]
),
# Relative strength: is it outperforming the benchmark?
rs_vs_benchmark=float(
(df.close.iloc[-1] / df.close.iloc[-63] - 1)
- (bench.close.iloc[-1] / bench.close.iloc[-63] - 1)
),
)A read that is honest about its limits:
AAPL, daily:
Structure : Uptrend. Higher highs and higher lows since the March low.
MA alignment : 50-day above 200-day, both rising. Confirmed uptrend.
Location : Price is 11% above the 50-day. Extended; the prior three
touches of the 50-day were buyable, but chasing here has
poor asymmetry.
Volume : The last advance came on volume 18% BELOW the 50-day average.
The move is not confirmed. This is the most important line here.
Relative str. : +4.2% vs SPY over 63 days. Leading.
Invalidation : 182.40 — the last higher low. Below that, the uptrend structure
is broken and this read is wrong.
What this does NOT tell you: whether it goes up from here. The structure is
constructive and the volume is not. That is a description, not a forecast.Notes
- The distinction between description and prediction is the whole discipline. "Price is in an uptrend and will break 200" is two claims: the first is observable, the second is a guess wearing the first one's clothes.
- Most published pattern-reliability statistics come from studies with severe selection bias — the patterns were identified after the fact, on charts chosen because the pattern worked. Backtest on out-of-sample data or do not trust the number.
- This is educational material about chart-reading methodology, not financial advice, and not a recommendation to trade any instrument.
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.

