indicator-expert

marketcalls/openalgo-indicator-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/marketcalls/openalgo-indicator-skills --skill indicator-expert
0 commentsdiscussion
summary

All indicators accessed via from openalgo import ta:

skill.md

OpenAlgo Indicator Expert Skill

Environment

  • Python with openalgo, pandas, numpy, plotly, dash, streamlit, numba
  • Data sources: OpenAlgo (Indian markets via client.history(), client.quotes(), client.depth()), yfinance (US/Global)
  • Real-time: OpenAlgo WebSocket (client.connect(), subscribe_ltp, subscribe_quote, subscribe_depth)
  • Indicators: openalgo.ta (ALWAYS — 100+ Numba-optimized indicators)
  • Charts: Plotly with template="plotly_dark"
  • Dashboards: Plotly Dash with dash-bootstrap-components OR Streamlit with st.plotly_chart()
  • Custom indicators: Numba @njit(cache=True, nogil=True) + NumPy
  • API keys loaded from single root .env via python-dotenv + find_dotenv() — never hardcode keys
  • Scripts go in appropriate directories (charts/, dashboards/, custom_indicators/, scanners/) created on-demand
  • Never use icons/emojis in code or logger output

Critical Rules

  1. ALWAYS use openalgo.ta for ALL technical indicators. Never reimplement what already exists in the library.
  2. Data normalization: Always convert DataFrame index to datetime, sort, and strip timezone after fetching.
  3. Signal cleaning: Always use ta.exrem() after generating raw buy/sell signals. Always .fillna(False) before exrem.
  4. Plotly dark theme: All charts use template="plotly_dark" with xaxis type="category" for candlesticks.
  5. Numba for custom indicators: Use @njit(cache=True, nogil=True) — never fastmath=True (breaks NaN handling).
  6. Input flexibility: openalgo.ta accepts numpy arrays, pandas Series, or lists. Output matches input type.
  7. WebSocket feeds: Use client.connect(), client.subscribe_ltp() / subscribe_quote() / subscribe_depth() for real-time data.
  8. Environment: Load .env from project root via find_dotenv() — never hardcode API keys.
  9. Market detection: If symbol looks Indian (SBIN, RELIANCE, NIFTY), use OpenAlgo. If US (AAPL, MSFT), use yfinance.
  10. Always explain chart outputs in plain language so traders understand what the indicator shows.

Data Source Priority

Market Data Source Method Example Symbols
India (equity) OpenAlgo client.history() SBIN, RELIANCE, INFY
India (index) OpenAlgo client.history(exchange="NSE_INDEX") NIFTY, BANKNIFTY
India (F&O) OpenAlgo client.history(exchange="NFO") NIFTY30DEC25FUT
US/Global yfinance yf.download() AAPL, MSFT, SPY

OpenAlgo API Methods for Data

Method Purpose Returns
client.history(symbol, exchange, interval, start_date, end_date) OHLCV candles DataFrame (timestamp, open, high, low, close, volume)
client.quotes(symbol, exchange) Real-time snapshot Dict (open, high, low, ltp, bid, ask, prev_close, volume)
client.multiquotes(symbols=[...]) Multi-symbol quotes List of quote dicts
client.depth(symbol, exchange) Market depth (L5) Dict (bids, asks, ohlc, volume, oi)
client.intervals() Available intervals Dict (minutes, hours, days, weeks, months)
client.connect() WebSocket connect None (sets up WS connection)
client.subscribe_ltp(instruments, callback) Live LTP stream Callback with {symbol, exchange, ltp}
client.subscribe_quote(instruments, callback) Live quote stream Callback with {symbol, exchange, ohlc, ltp, volume}
client.subscribe_depth(instruments, callback) Live depth stream Callback with {symbol, exchange, bids, asks}

Indicator Library Reference

All indicators accessed via from openalgo import ta:

Trend (20)

ta.sma, ta.ema, ta.wma, ta.dema, ta.tema, ta.hma, ta.vwma, ta.alma, ta.kama, ta.zlema, ta.t3, ta.frama, ta.supertrend, ta.ichimoku, ta.chande_kroll_stop, ta.trima, ta.mcginley, ta.vidya, ta.alligator, ta.ma_envelopes

Momentum (9)

ta.rsi, ta.macd, ta.stochastic, ta.cci, ta.williams_r, ta.bop, ta.elder_ray, ta.fisher, ta.crsi

Volatility (16)

ta.atr, ta.bbands, ta.keltner, ta.donchian, ta.chaikin_volatility, ta.natr, ta.rvi, ta.ultimate_oscillator, ta.true_range, ta.massindex, ta.bb_percent, ta.bb_width, ta.chandelier_exit, ta.historical_volatility, ta.ulcer_index, ta.starc

Volume (14)

ta.obv, ta.obv_smoothed, ta.vwap, ta.mfi, ta.adl, ta.cmf, ta.emv, ta.force_index, ta.nvi, ta.pvi, ta.volosc, ta.vroc, ta.kvo, ta.pvt

Oscillators (20+)

ta.cmo, ta.trix, ta.uo_oscillator, ta.awesome_oscillator, ta.accelerator_oscillator, ta.ppo, ta.po, ta.dpo, ta.aroon_oscillator, ta.stoch_rsi, ta.rvi_oscillator, ta.cho, ta.chop, ta.kst, ta.tsi, ta.vortex, ta.gator_oscillator, ta.stc, ta.coppock, ta.roc

Statistical (9)

ta.linreg, ta.lrslope, ta.correlation, ta.beta, ta.variance, ta.tsf, ta.median, ta.mode, ta.median_bands

Hybrid (6+)

ta.adx, ta.dmi, ta.aroon, ta.pivot_points, ta.sar, ta.williams_fractals, ta.rwi

Utilities

ta.crossover, ta.crossunder, ta.cross, ta.highest, ta.lowest, ta.change, ta.roc, ta.stdev, ta.exrem, ta.flip, ta.valuewhen, ta.rising, ta.falling

Modular Rule Files

Detailed reference for each topic is in rules/:

Rule File Topic
indicator-catalog Complete 100+ indicator reference with signatures and parameters
data-fetching OpenAlgo history/quotes/depth, yfinance, data normalization
plotting Plotly candlestick, overlay, subplot, multi-panel charts
custom-indicators Building custom indicators with Numba + NumPy
websocket-feeds Real-time LTP/Quote/Depth streaming via WebSocket
numba-optimization Numba JIT patterns, cache, nogil, NaN handling
dashboard-patterns Plotly Dash web applications with callbacks
streamlit-patterns Streamlit web applications with sidebar, metrics, plotly charts
multi-timeframe Multi-timeframe indicator analysis
signal-generation Signal generation, cleaning, crossover/crossunder
indicator-combinations Combining indicators for confluence analysis
symbol-format OpenAlgo symbol format, exchange codes, index symbols

Chart Templates (in rules/assets/)

Template Path Description
EMA Chart assets/ema_chart/chart.py EMA overlay on candlestick
RSI Chart assets/rsi_chart/chart.py RSI with overbought/oversold zones
MACD Chart assets/macd_chart/chart.py MACD line, signal, histogram
Supertrend assets/supertrend_chart/chart.py Supertrend overlay with direction coloring
Bollinger assets/bollinger_chart/chart.py Bollinger Bands with squeeze detection
Multi-Indicator assets/multi_indicator/chart.py Candlestick + EMA + RSI + MACD + Volume
Basic Dashboard assets/dashboard_basic/app.py Single-symbol Plotly Dash app
Multi Dashboard assets/dashboard_multi/app.py Multi-symbol multi-timeframe dashboard
Streamlit Basic assets/streamlit_basic/app.py Single-symbol Streamlit app
Streamlit Multi assets/streamlit_multi/app.py Multi-timeframe Streamlit app
Custom Indicator assets/custom_indicator/template.py Numba custom indicator template
Live Feed assets/live_feed/template.py WebSocket real-time indicator
Scanner assets/scanner/template.py Multi-symbol indicator scanner

Quick Template: Standard Indicator Chart Script

import os
from datetime import datetime, timedelta
from pathlib import Path

import numpy as np
import pandas as pd
import plotly.graph_objects as go
from plotly.subplots import make_subplots
from dotenv import find_dotenv, load_dotenv
from openalgo import api, ta

# --- Config ---
script_dir = Path(__file__).resolve().parent
load_dotenv(find_dotenv(), override=False)

SYMBOL = "SBIN"
EXCHANGE = "NSE"
INTERVAL = "D"

# --- Fetch Data ---
client = api(
    api_key=os.getenv("OPENALGO_API_KEY"),
    host=os.getenv("OPENALGO_HOST", "http://127.0.0.1:5000"),
)

end_date = datetime.now().date()
start_date = end_date - timedelta(days=365)

df = client.history(
    symbol=SYMBOL, exchange=EXCHANGE, interval=INTERVAL,
    start_date=start_date.strftime("%Y-%m-%d"),
    end_date=end_date.strftime("%Y-%m-%d"),
)
if "timestamp" in df.columns:
    df["timestamp"] = pd.to_datetime(df["timestamp"])
    df = df.set_index("timestamp")
else:
    df.index = pd.to_datetime(df.index)
df = df.sort_index()
if df.index.tz is not None:
    df.index = df.index.tz_convert(None)

close = df["close"]
high = df["high"]
low = df["low"]
volume = df["volume"]

# --- Compute Indicators ---
ema_20 = ta.ema(close, 20)
rsi_14 = ta.rsi(close, 14)

# --- Chart ---
fig = make_subplots(
    rows=2, cols=1, shared_xaxes=True,
    row_heights=[0.7, 0.3], vertical_spacing=0.03,
    subplot_titles=[f"{SYMBOL} Price + EMA(20)"
how to use indicator-expert

How to use indicator-expert on Cursor

AI-first code editor with Composer

1

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-expert
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/marketcalls/openalgo-indicator-skills --skill indicator-expert

The skills CLI fetches indicator-expert from GitHub repository marketcalls/openalgo-indicator-skills and configures it for Cursor.

3

Select 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
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/indicator-expert

Reload or restart Cursor to activate indicator-expert. Access the skill through slash commands (e.g., /indicator-expert) 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

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.638 reviews
  • Layla Malhotra· Dec 20, 2024

    We added indicator-expert from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Pratham Ware· Dec 8, 2024

    indicator-expert is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Zaid Johnson· Dec 8, 2024

    indicator-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Sophia Smith· Dec 8, 2024

    Keeps context tight: indicator-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Fatima Ramirez· Nov 27, 2024

    Registry listing for indicator-expert matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Sophia Ghosh· Nov 27, 2024

    I recommend indicator-expert for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • William Smith· Nov 15, 2024

    indicator-expert fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Henry Singh· Nov 11, 2024

    Useful defaults in indicator-expert — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • Ama Khanna· Oct 18, 2024

    Keeps context tight: indicator-expert is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Sophia Anderson· Oct 18, 2024

    indicator-expert reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 38

1 / 4