crypto-ta-analyzer▌
dkyazzentwatwa/chatgpt-skills · updated May 19, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
29+ technical indicators with 7-tier trading signals, divergence detection, and volume confirmation for crypto and stocks.
- ›Combines 29 proven indicators (RSI, MACD, Bollinger Bands, Ichimoku, OBV, and 24 others) weighted by reliability to generate consensus-based buy/sell signals
- ›Detects bullish and bearish divergences across RSI, MACD, and OBV; identifies Bollinger Band squeezes and volume confirmation levels
- ›Supports multiple data sources including CoinGecko, exchange APIs, Yahoo F
Crypto & Stock Technical Analysis
Multi-indicator technical analysis system that generates high-confidence trading signals by combining 29+ proven algorithms. Features divergence detection, Bollinger Band squeeze alerts, volume confirmation, and a 7-tier signal system. Ideal for cryptocurrency and stock market analysis.
Core Workflow
1. Data Acquisition
Fetch historical price data from any supported source:
CoinGecko (via MCP tools):
Use coingecko_get_historical_chart tool with:
- coin_id: Target cryptocurrency (e.g., 'bitcoin', 'ethereum')
- days: Time range ('7', '30', '90', '365', 'max')
- vs_currency: Base currency (default 'usd')
Other Supported Sources:
- Exchange APIs (Binance, Coinbase, etc.) - OHLCV format
- Yahoo Finance - Stock data
- Any price-only data - Automatic OHLC approximation
Minimum Requirements:
- At least 100 data points for reliable analysis (50 minimum)
- Price data required, volume recommended
- Recent data preferred for active trading signals
2. Convert Data to OHLCV Format
The generic data converter auto-detects and normalizes any supported format:
from scripts.data_converter import normalize_ohlcv, validate_data_quality
# Auto-detect format and convert
ohlcv_df, metadata = normalize_ohlcv(raw_data, source="auto")
# Check conversion quality
print(f"Format detected: {metadata['detected_format']}")
print(f"Rows: {metadata['original_rows']} -> {metadata['final_rows']}")
print(f"Warnings: {metadata['warnings']}")
# Validate data quality
quality_report = validate_data_quality(ohlcv_df)
Backward compatible with old CoinGecko converter:
from scripts.data_converter import prepare_analysis_data
ohlcv_df = prepare_analysis_data(coingecko_json_data)
3. Run Technical Analysis
Execute the analyzer with prepared data:
from scripts.ta_analyzer import TechnicalAnalyzer
import json
# Initialize analyzer with OHLCV data
analyzer = TechnicalAnalyzer(ohlcv_df)
# Run comprehensive analysis
results = analyzer.analyze_all()
# Display results
print(json.dumps(results, indent=2))
4. Interpret Results
Analysis returns comprehensive data including new features:
{
"scoreTotal": 8.5,
"tradeSignal": "STRONG_UPTREND",
"tradeSignal7Tier": "STRONG_BUY",
"tradeTrigger": true,
"currentPrice": 45234.56,
"priceChange24h": 3.45,
"confidence": 0.75,
"normalizedScore": 0.42,
"volumeConfirmation": 0.85,
"squeezeDetected": false,
"divergences": {
"RSI": "NONE",
"MACD": "NONE",
"OBV": "NONE"
},
"individualScores": {
"RSI": 1.0,
"MACD": 1.0,
"BB": 0.75,
"OBV": 0.8,
"ICHIMOKU": 1.0,
...
},
"individualSignals": {
"RSI": "BUY",
"MACD": "BUY",
"BB": "BUY",
...
},
"regime": {
"regime": "TRENDING",
"adx": 32.5,
"dmiDirection": "UP"
},
"warnings": []
}
7-Tier Signal System (NEW):
- STRONG_BUY: High confidence bullish (normalized >= 0.5, confidence >= 0.7)
- BUY: Moderate confidence bullish (normalized >= 0.35, confidence >= 0.5)
- WEAK_BUY: Low confidence bullish (normalized >= 0.2)
- NEUTRAL: No clear direction
- WEAK_SELL: Low confidence bearish (normalized <= -0.2)
- SELL: Moderate confidence bearish (normalized <= -0.35, confidence >= 0.5)
- STRONG_SELL: High confidence bearish (normalized <= -0.5, confidence >= 0.7)
Legacy Signal Interpretation (backward compatible):
- scoreTotal >= 7.0: STRONG_UPTREND - High confidence bullish signal
- scoreTotal 3.0-6.9: NEUTRAL - Mixed signals, wait for clarity
- scoreTotal < 3.0: DOWNTREND - Bearish signal, avoid longs
Divergence Types:
- BULLISH_DIV: Price lower low + indicator higher low = potential reversal up
- BEARISH_DIV: Price higher high + indicator lower high = potential reversal down
- HIDDEN_BULLISH: Trend continuation signal in uptrend
- HIDDEN_BEARISH: Trend continuation signal in downtrend
- NONE: No divergence detected
Available Indicators (29)
Core Indicators (10) - Weight: 1.0
- RSI (Relative Strength Index) - Momentum oscillator with divergence detection
- MACD (Moving Average Convergence Divergence) - Trend-following momentum with divergence
- BB (Bollinger Bands) - NEW: Volatility bands with squeeze detection
- OBV (On-Balance Volume) - NEW: Volume-price divergence indicator
- ICHIMOKU (Ichimoku Cloud) - NEW: Multi-component trend system (crypto-optimized 10/30/60)
- EMA (Exponential Moving Average) - Short/long crossover
- SMA (Simple Moving Average) - Short/long crossover
- MFI (Money Flow Index) - Volume-weighted RSI
- KDJ (Stochastic with J line) - Overbought/oversold with momentum
- SAR (Parabolic SAR) - Trend reversal detection
Strong Indicators (5) - Weight: 0.75
- DEMA (Double Exponential MA) - Reduced lag moving average
- MESA (MESA Adaptive MA) - Ehlers Hilbert Transform based
- CCI (Commodity Channel Index) - Cyclical trend identification
- AROON - Trend timing indicator
- APO (Absolute Price Oscillator) - Trend strength
Supporting Indicators (14) - Weight: 0.5
- ADX (Average Directional Index) - Trend strength
- DMI (Directional Movement Index) - Trend direction
- CMO (Chande Momentum Oscillator) - Modified RSI
- KAMA (Kaufman Adaptive MA) - Volatility-adjusted MA
- MOMI (Momentum) - Rate of price change
- PPO (Percentage Price Oscillator) - Normalized MACD
- ROC (Rate of Change) - Percentage momentum
- TRIMA (Triangular MA) - Smoothed moving average
- TRIX (Triple Exponential MA) - Smoothed momentum
- T3 (Tillson T3) - Low-lag smooth MA
- WMA (Weighted MA) - Linearly weighted
- VWAP (Volume Weighted Average Price) - NEW: Institutional reference
- ATR_SIGNAL (ATR Volatility Signal) - NEW: Volatility-based signals
- CAD (CMO with Regime-Aware Mean Reversion) - Adaptive momentum
See references/indicators.md for detailed indicator explanations.
Usage Patterns
Quick Analysis
For rapid assessment of a single cryptocurrency:
1. Call coingecko_get_historical_chart for target coin (7-30 days)
2. Convert data using coingecko_converter
3. Run ta_analyzer.analyze_all()
4. Present scoreTotal and tradeSignal to user
Comparative Analysis
To compare multiple cryptocurrencies:
1. Call coingecko_compare_coins for target coins
2. For each coin:
- Fetch historical chart data
- Run technical analysis
- Store results
3. Create comparison table with scores and signals
4. Identify strongest/weakest performers
Deep Dive Analysis
For comprehensive assessment with context:
1. Fetch multiple timeframes (7d, 30d, 90d)
2. Run analysis on each timeframe
3. Check for signal agreement across timeframes
4. Review individual indicator signals for divergences
5. Cross-reference with market data (market cap, volume, dominance)
6. Provide detailed report with confidence levels
Trend Monitoring
For ongoing market surveillance:
1. Fetch current data for watchlist
2. Run analysis on all coins
3. Filter for STRONG_UPTREND signals (score >= 7)
4. Rank by score descending
5. Present top opportunities with context
Best Practices
Data Quality
- Always validate data quality before analysis using validate_data_quality()
- Ensure minimum 100 data points (preferably 200+)
- Check for missing values or data gaps
- Use appropriate timeframe for user's trading strategy
Interpretation Guidelines
- Never rely on single indicator - the power is in consensus
- Consider market context - indicators behave differently in trending vs ranging markets
- Watch for divergences - when price contradicts indicators, reversal may be coming
- Volume confirms price - MFI provides crucial validation
- Multiple timeframes - confirm signals across different periods
Common Patterns
High Conviction Bullish (STRONG_BUY):
- 7-tier signal: STRONG_BUY or BUY
- Confidence >= 0.7
- RSI between 30-70 (not overbought)
- MACD bullish crossover
- Price above Ichimoku cloud
- OBV confirms with no bearish divergence
- Volume confirmation >= 0.7
- ADX > 25 (strong trend)
Breakout Setup:
- Bollinger Band squeeze detected (squeezeDetected: true)
- ADX rising from < 20
- Volume starting to increase
- Watch for band expansion
Trend Exhaustion Warning:
- Score > 7 BUT RSI > 80 or MFI > 90
- Bearish divergence on RSI, MACD, or OBV
- Price above Bollinger upper band (%B > 1.0)
- Potential reversal or pullback incoming
Divergence-Based Reversal:
- Bearish divergence: Prepare for potential top
- Bullish divergence: Watch for potential bottom
- OBV divergence is most reliable (volume precedes price)
False Breakout:
- Strong price move BUT ADX < 20
- Low volume (volumeConfirmation < 0.5)
- OBV not confirming price move
- Likely whipsaw or temporary spike
Ichimoku Confirmation:
- Price above cloud + Tenkan above Kijun = Strong bullish
- Price below cloud + Tenkan below Kijun = Strong bearish
- Price inside cloud = No-trade zone, wait for clarity
Limitations
CoinGecko Data Considerations
- CoinGecko provides price points, not true OHLC bars
- Converter approximates OHLC from adjacent prices
- Works well for trend analysis, less precise for intraday patterns
Indicator Nature
- Most indicators are lagging - calculated from past data
- Can generate whipsaws in choppy, sideways markets
- Overfitting risk - too many indicators can cause analysis paralysis
- Market regime changes require adaptation
Recommended Use Cases
✅ Great for: Trend identification, medium-term signals, portfolio screening
✅ Good for: Entry/exit timing, risk assessment, comparative analysis
⚠️ Limited for: High-frequency trading, precise intraday timing, ranging markets
❌ Avoid for: News-driven moves, low-liquidity coins, extreme volatility events
Advanced Techniques
Custom Scoring Weights
Modify indicator weights based on market conditions:
- Trending markets: Increase weight of MACD, EMA, ADX
- Ranging markets: Increase weight of RSI, CCI, Stochastic
- High volatility: Increase weight of SAR, KAMA (adaptive indicators)
Multi-Timeframe Confirmation
Analyze same coin across multiple timeframes:
- 7 days (short-term trend)
- 30 days (medium-term trend)
how to use crypto-ta-analyzerHow to use crypto-ta-analyzer on Cursor
AI-first code editor with Composer
1Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add crypto-ta-analyzer
2Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
$npx skills add https://github.com/dkyazzentwatwa/chatgpt-skills --skill crypto-ta-analyzerThe skills CLI fetches crypto-ta-analyzer from GitHub repository dkyazzentwatwa/chatgpt-skills and configures it for Cursor.
3Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
◆ Which agents do you want to install to?││ ── Universal (.agents/skills) ── always included ────│ • Amp│ • Antigravity│ • Cline│ • Codex│ ●Cursor(selected)│ • Cursor│ • Windsurf4Verify installation
Confirm successful installation by checking the skill directory location:
.cursor/skills/crypto-ta-analyzerReload or restart Cursor to activate crypto-ta-analyzer. Access the skill through slash commands (e.g., /crypto-ta-analyzer) or your agent's skill management interface.
⚠Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
Additional Resources
List & Monetize Your Skill
Submit your Claude Code skill and start earning
GET_STARTED →Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
✓Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
✓Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
✓Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
✓Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
general reviewsRatings
4.6★★★★★71 reviews- ★★★★★Ganesh Mohane· Dec 28, 2024
crypto-ta-analyzer reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Neel Chawla· Dec 28, 2024
crypto-ta-analyzer is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Nia Martin· Dec 12, 2024
Registry listing for crypto-ta-analyzer matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Evelyn Diallo· Dec 8, 2024
crypto-ta-analyzer has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Luis Reddy· Dec 8, 2024
Keeps context tight: crypto-ta-analyzer is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Camila Gonzalez· Nov 27, 2024
We added crypto-ta-analyzer from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Rahul Santra· Nov 19, 2024
I recommend crypto-ta-analyzer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Neel Malhotra· Nov 19, 2024
crypto-ta-analyzer fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kofi White· Nov 3, 2024
Useful defaults in crypto-ta-analyzer — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Anika Wang· Oct 22, 2024
I recommend crypto-ta-analyzer for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 71
1 / 8