Agent skill

longbridge-elliott-wave

Elliott Wave technical timing analysis for individual stocks. Identifies current wave cycle position (impulse 5-wave / corrective ABC), validates with Fibonacci ratios, confirms with momentum indicators (MACD, RSI, volume divergence), and evaluates market environment per market (HK / US / A-share / SGX). Outputs structured natural language report with Fibonacci price zones and actionable reference. Triggers on "波浪分析", "艾略特波浪", "Elliott Wave", "波浪周期", "wave analysis", "技术择时", "technical timing", stock ticker + wave/timing keywords, "现在是第几浪", "处于哪个波浪", "波浪判断", "波浪理论", "浪形分析", "波浪择时".

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill longbridge-elliott-wave --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/analysis/longbridge-elliott-wave/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Elliott Wave Analysis > **Response language**: match the user's input language — Simplified Chinese / Traditional Chinese / English. Technical timing skill that positions a stock within its Elliott Wave cycle, confirms with momentum, and contextualizes with market environment. Three modules run sequentially; each result feeds the next. ## When to Use | Trigger | Example | |---------|---------| | Wave position inquiry | "TSLA.US 现在是第几浪" / "700.HK波浪分析" | | Technical timing | "NVDA.US 技术择时" / "苹果波浪择时" | | Pre-trade check | "我想买,波浪角度看合适吗" | | General wave theory | "帮我做个艾略特波浪分析" | **Do not trigger if:** the user requests fundamental analysis, earnings preview, or valuation — use the relevant skill instead. ## Data Sources All price data comes from the Longbridge CLI. **Before the first invocation of any `longbridge` subcommand in a session, run `longbridge <subcommand> --help` to confirm available flags, required arguments, and symbol format.** Do this for every distinct subcommand you use (e.g. `kline`, `quote`, `capital`, `news`). ### What to fetch | Data | Purpose | Minimum | |------|---------|---------| | Daily K-line | Primary wave analysis | ≥ 250 bars, JSON | | Weekly K-line |

What's inside
Steps it walks through
  1. When to Use
  2. Data Sources
  3. What to fetch
  4. Symbol validation
  5. Practical notes
  6. Workflow
  7. Step 1 — Pre-flight checks
  8. Step 2 — Module A: Wave Cycle Identification
  9. Step 3 — Module B: Momentum Confirmation
  10. Step 4 — Module C: Market Environment
  11. Step 5 — Generate Output
  12. Output Template
  13. Output rules
  14. Error Handling
Ships with 1 file
  • metadata.json
Commands it runs
python3 scripts/signal_engine.py --kline /tmp/kline_day.json --symbol SYMBOL
pip install pandas numpy
python3 scripts/signal_engine.py --kline /tmp/kline_day.json --symbol AAPL.US
More from claude-skill-registry
All skills →
About this skill
What does the longbridge-elliott-wave skill do?

Elliott Wave technical timing analysis for individual stocks. Identifies current wave cycle position (impulse 5-wave / corrective ABC), validates with Fibonacci ratios, confirms with momentum indicators (MACD, RSI, volume divergence), and evaluates market environment per market (HK / US / A-share / SGX). Outputs structured natural language report with Fibonacci price zones and actionable reference. Triggers on "波浪分析", "艾略特波浪", "Elliott Wave", "波浪周期", "wave analysis", "技术择时", "technical timing", stock ticker + wave/timing keywords, "现在是第几浪", "处于哪个波浪", "波浪判断", "波浪理论", "浪形分析", "波浪择时".

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill longbridge-elliott-wave --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going