Classify market conditions as bullish, bearish, ranging, or volatile to guide strategy selection and historical testing. Distinguish synthetic demonstrations from analysis of actual price data, with confidence levels and historical comparisons where available.
Detect current market regime using npx neural-trader — bull/bear/ranging/volatile classification with recommended strategy. Use when the user asks about market conditions, wants to pick a strategy for current conditions, or before running a backtest/signal that should be regime-aware.
Review the instructions the agent will receive before you install.
Detect the current market regime using neural-trader's regime detection engine.
Steps:
npm ls neural-trader 2>/dev/null || npm install --ignore-scripts neural-tradernpx neural-trader --regime --symbol TICKER
--regime-detect and --symbols are not recognised; the CLI answers "Unknown command"). In 2.8.11 this classifies a built-in sample price series (the result says "Synthetic prices used for demo"), so it is a demo of the output shape, not a read on TICKER. Say so in the report. For a real read, get the symbol's bars with --backtest --live (dataSource: "yahoo-finance") and classify from those.--indicators is rejected). Use the nt.calculateRsi / nt.calculateSma library functions on real bars, or the multi-indicator strategy inside a backtest.mcp__plugin_ruflo-core_ruflo__neural_predict({ input: "indicators: RSI=X, ADX=Y, VIX=Z" })mcp__plugin_ruflo-core_ruflo__memory_search({ query: "regime similar to CURRENT", namespace: "trading-analysis" })mcp__plugin_ruflo-core_ruflo__memory_store({ key: "regime-DATE", value: "REGIME_ANALYSIS", namespace: "trading-analysis" })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.