본문으로 건너뛰기
cccskills
무료GitHub에 공개

market-pattern

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

설치 방법 보기

이럴 때 유용합니다

  • Finding candlestick patterns for a symbol and period
  • Reviewing patterns ranked by reliability
  • Organizing bullish and bearish signals
  • Saving detected patterns for future reference

포함된 파일(1)

  • SKILL.md2.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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__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.
  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__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).
    • Plain store (namespace-routable): mcp__plugin_ruflo-core_ruflo__memory_store --namespace market-patterns — this DOES respect the market-patterns namespace because memory_* 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-patterns

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Adding newly available router models to chat-ui
  • Writing concise descriptions of model capabilities
  • Updating production and development model entries together
ruvnet/ruflo7.7만2026년 10월 18일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Record the reasoning behind adopting a technology
  • Start an ADR for an API or data model change
  • Document an infrastructure decision
ruvnet/ruflo7.7만2026년 10월 18일 업데이트

adr-index

무료

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Index ADRs imported from another project
  • Refresh a graph that differs from files on disk
  • Set up ADR tracking in an existing codebase
ruvnet/ruflo7.7만2026년 10월 18일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Rebuild the index after deleting an ADR file
  • Remove stale relationships after editing an ADR
  • Reconcile the ADR index on a schedule
ruvnet/ruflo7.7만2026년 10월 18일 업데이트

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 a pull request before merging
  • Review major code changes against agreed design decisions
  • Find references to superseded ADRs
ruvnet/ruflo7.7만2026년 10월 18일 업데이트

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.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking ADR integrity after import
  • Blocking CI when ADR issues are found
  • Reviewing ADR data before a release
ruvnet/ruflo7.7만2026년 10월 18일 업데이트

ruvnet의 스킬 모두 보기

이 스킬의 문제 신고