Find candlestick and chart patterns in previously ingested market data. Classify detections by reversal or continuation, bullish or bearish direction, and reliability score, then rank and store them for later reference.
Detect and classify candlestick patterns from ingested OHLCV data
Review the instructions the agent will receive before you install.
Scan ingested OHLCV data for known candlestick patterns, classify them by type and reliability, and store for future reference.
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.
mcp__plugin_ruflo-core_ruflo__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.mcp__plugin_ruflo-core_ruflo__agentdb_pattern-store with type: 'market-pattern'. Don't pass a namespace arg — ReasoningBank routes it; on bridge unavailability the fallback writes to the reserved pattern namespace with controller: 'memory-store-fallback' (see ruflo-agentdb ADR-0001).mcp__plugin_ruflo-core_ruflo__memory_store --namespace market-patterns — this DOES respect the market-patterns namespace because memory_* is namespace-routed.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-patterns
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.