Market Pattern
- 641 installs
- 67k repo stars
- Updated August 4, 2026
- ruvnet/ruflo
market-pattern is a Claude Code skill that scans ingested OHLCV market data for known candlestick and chart patterns, classifies them by type and reliability, and stores results for developers building trading analytics
About
market-pattern is a ruflo skill for candlestick and chart pattern detection over previously ingested OHLCV data. It accepts a symbol and optional period (for example 1D), searches memory for stored bars, classifies formations such as doji, hammer, engulfing, and head-shoulders, and persists matches through AgentDB pattern-store and pattern-search alongside Claude Flow memory tools. The skill also routes through ruvllm HNSW for pattern lookup workflows. Developers use market-pattern after market data ingestion completes and they need repeatable pattern classification rather than manual chart review. It does not ingest raw feeds by itself.
- Extracts repeatable market patterns from successful products and campaigns
- Generates positioning frameworks and go-to-market angles in minutes
- Works across consumer, SaaS, AI, and content verticals
- Delivers structured output ready for validation or spec writing
- Reduces unstructured market research from hours to a single agent call
Market Pattern by the numbers
- 641 all-time installs (skills.sh)
- +10 installs in the week ending Jul 26, 2026 (Skillselion tracking)
- Ranked #643 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ruvnet/ruflo --skill market-patternAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 641 |
|---|---|
| repo stars | ★ 67k |
| Last updated | August 4, 2026 |
| Repository | ruvnet/ruflo ↗ |
How do you detect candlestick patterns in OHLCV data?
Rapidly surface proven market patterns, positioning strategies, and competitive angles before committing to an idea.
Who is it for?
Developers building quantitative trading tools who already ingested OHLCV bars and need automated candlestick pattern classification.
Skip if: Product positioning research or teams without ingested OHLCV market data in the Claude Flow memory pipeline.
When should I use this skill?
User asks to scan candlestick patterns, classify chart formations, or query stored OHLCV pattern hits for a ticker.
What you get
Classified pattern records, reliability scores, AgentDB pattern-store entries
- Pattern classification results
- AgentDB pattern records
By the numbers
- Documents detection for 4 named pattern families: doji, hammer, engulfing, and head-shoulders
Files
Market Pattern
Scan ingested OHLCV data for known candlestick patterns, classify them by type and reliability, and store for future reference.
When to use
When you need to identify candlestick patterns (doji, hammer, engulfing, head-shoulders, etc.) in market data. Requires data to be ingested first via market-ingest.
Steps
1. Load candles -- call mcp__claude-flow__memory_search (or memory_list) on the market-data namespace to retrieve normalized OHLCV data for the symbol and period. The memory_* tool family routes by namespace; the agentdb_hierarchical-* family does NOT (it routes by tier), so use memory_* for namespaced reads. 2. Scan for patterns -- iterate through candle sequences looking for:
- Single-candle: doji (open ~= close), hammer (long lower wick), inverted hammer
- Two-candle: bullish/bearish engulfing
- Three-candle: morning star, evening star, three white soldiers, three black crows
- Multi-candle: head & shoulders, double top/bottom, cup & handle
3. Classify -- for each detection, assign: pattern name, type (reversal/continuation), direction (bullish/bearish), reliability score (0.0-1.0) 4. Rank -- sort by reliability score descending 5. Store -- two paths (per ruflo-cost-tracker ADR-0001 dual-path pattern):
- Pattern-store (typed, recommended):
mcp__claude-flow__agentdb_pattern-storewithtype: 'market-pattern'. Don't pass anamespacearg — ReasoningBank routes it; on bridge unavailability the fallback writes to the reservedpatternnamespace withcontroller: 'memory-store-fallback'(see ruflo-agentdb ADR-0001). - Plain store (namespace-routable):
mcp__claude-flow__memory_store --namespace market-patterns— this DOES respect themarket-patternsnamespace becausememory_*is namespace-routed.
6. Report -- display: pattern name, date range, direction, reliability, suggested action
CLI alternative
npx @claude-flow/cli@latest memory search --query "bullish reversal patterns" --namespace market-patterns
npx @claude-flow/cli@latest memory store --key "pattern-AAPL-2026-05-04-doji" --value '{...}' --namespace market-patternsRelated skills
Grill MeHave an agent relentlessly pressure-test their plan or design until every decision branch is resolved and shared understanding is reached.691k196kGrill With DocsPressure-test architecture decisions against their live codebase and living documentation before writing production code.585k196k
Lark CalendarLet their coding agents read, create, and manage events inside Lark (Feishu) Calendar directly from natural language instructions.493kLark ImLet their coding agent send instant notifications, post updates, and receive commands directly inside Lark (Feishu) workspaces.493kLark ContactLet their AI coding agents read and write contacts, send messages, and manage user data inside Lark (Feishu).493kLark AttendanceAutomatically fetch and report daily attendance data from Lark (Feishu) into their own tools or agents.493kHow it compares
Use market-pattern for stored OHLCV candlestick classification; pair with ingestion skills first because scanning requires preloaded bars.
FAQ
Does market-pattern ingest raw market feeds?
market-pattern expects OHLCV data to be ingested first through the companion market ingestion flow; the skill scans stored bars, classifies candlestick and chart patterns, and saves matches rather than pulling live quotes.
Which candlestick patterns does market-pattern detect?
market-pattern identifies common formations including doji, hammer, engulfing, and head-shoulders, classifying each hit by pattern type and reliability before persisting results for later search.