indicator-chart▌
marketcalls/openalgo-indicator-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Create an interactive Plotly chart for a technical indicator on a symbol.
Create an interactive Plotly chart for a technical indicator on a symbol.
Arguments
Parse $ARGUMENTS as: indicator symbol exchange interval
$0= indicator name (e.g., ema, rsi, macd, supertrend, bbands, adx, stochastic, ichimoku, obv, vwap). Default: ema$1= symbol (e.g., SBIN, RELIANCE, NIFTY, AAPL). Default: SBIN$2= exchange (e.g., NSE, BSE, NFO, NSE_INDEX). Default: NSE. For US symbols use: YFINANCE$3= interval (e.g., D, 1h, 5m). Default: D
If no arguments, ask the user which indicator and symbol they want.
Instructions
- Read the indicator-expert skill rules for reference patterns
- Create
charts/{indicator_name}/directory if it doesn't exist (on-demand) - Create a
.pyfile incharts/{indicator_name}/named{symbol}_{indicator}_chart.py - Use the matching template from
rules/assets/{indicator}_chart/chart.pyas starting point (if available) - The script must:
- Load
.envfrom project root usingfind_dotenv() - Fetch data via OpenAlgo
client.history()(or yfinance for US symbols) - Normalize data: convert index to datetime, sort, strip timezone
- Compute the indicator using
openalgo.ta - Create a Plotly chart with
template="plotly_dark"andxaxis_type="category" - Overlay indicators (EMA, Bollinger, Supertrend, Ichimoku) go on the candlestick panel
- Subplot indicators (RSI, MACD, Stochastic, ADX, Volume, OBV) go below in separate panels
- Use
make_subplotsfor multi-panel layouts - Add horizontal reference lines where appropriate (RSI 30/70, Stochastic 20/80)
- Print a plain-language explanation of the current indicator reading
- Save chart as HTML:
{symbol}_{indicator}_chart.html - Show chart with
fig.show()
- Load
- Never use icons/emojis in code or output
Indicator Chart Types
Overlay Indicators (on candlestick panel)
| Indicator | Chart Type |
|---|---|
| ema, sma, wma, dema, tema, hma | Line overlay |
| bbands | Fill-between bands + midline |
| supertrend | Color-coded line (green=up, red=down) |
| ichimoku | 5 lines + cloud fill |
| keltner, donchian | Fill-between channels |
| sar | Dot markers above/below price |
| ma-envelopes | Upper/lower band lines |
Subplot Indicators (separate panel below)
| Indicator | Chart Type |
|---|---|
| rsi | Line + horizontal 30/70 zones |
| macd | Line + signal + histogram bars |
| stochastic | K% + D% lines + 20/80 zones |
| adx | DI+, DI-, ADX lines + 25 threshold |
| cci | Line + horizontal +100/-100 zones |
| williams_r | Line + -20/-80 zones |
| obv | Line (cumulative) |
| mfi | Line + 20/80 zones |
| volume | Bar chart (green/red by price direction) |
| atr | Line (volatility) |
Multi-Indicator Charts
If user asks for "multi" or multiple indicators, create a comprehensive multi-panel chart with:
- Row 1: Candlestick + EMA overlays
- Row 2: RSI(14)
- Row 3: MACD(12,26,9)
- Row 4: Volume bars
Signal Markers
If the indicator generates clear buy/sell signals (e.g., crossover, supertrend direction change), add triangle markers:
- Buy: green triangle-up markers
- Sell: red triangle-down markers
Data Periods
| Interval | Default Lookback |
|---|---|
| D | 1 year (365 days) |
| 1h | 6 months (180 days) |
| 15m, 30m | 3 months (90 days) |
| 5m | 1 month (30 days) |
| 1m | 7 days |
Plain-Language Explanation
After creating the chart, print a brief explanation:
SBIN — RSI(14) Analysis
Current RSI: 42.3
Interpretation: Neutral zone (between 30-70). Neither overbought nor oversold.
Trend: RSI has been declining from 65 over the past 5 bars, suggesting weakening momentum.
Example Usage
/indicator-chart ema SBIN NSE D
/indicator-chart rsi RELIANCE NSE D
/indicator-chart macd AAPL YFINANCE D
/indicator-chart supertrend NIFTY NSE_INDEX D
/indicator-chart multi SBIN NSE D
/indicator-chart bbands INFY NSE 1h
How to use indicator-chart on Cursor
AI-first code editor with Composer
Prerequisites
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 indicator-chart
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches indicator-chart from GitHub repository marketcalls/openalgo-indicator-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate indicator-chart. Access the skill through slash commands (e.g., /indicator-chart) 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.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
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.
Ratings
4.7★★★★★54 reviews- ★★★★★Aarav Farah· Dec 24, 2024
Useful defaults in indicator-chart — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kwame Thomas· Dec 20, 2024
Solid pick for teams standardizing on skills: indicator-chart is focused, and the summary matches what you get after install.
- ★★★★★Chinedu Martin· Dec 20, 2024
indicator-chart fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Ganesh Mohane· Dec 12, 2024
I recommend indicator-chart for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Diya Johnson· Dec 8, 2024
indicator-chart is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Min Liu· Nov 27, 2024
Useful defaults in indicator-chart — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Sakshi Patil· Nov 19, 2024
Keeps context tight: indicator-chart is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Jin Harris· Nov 15, 2024
indicator-chart is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ama Malhotra· Nov 11, 2024
indicator-chart has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ama Khanna· Nov 11, 2024
I recommend indicator-chart for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 54