菜单
Use when finance workflows need Vibe-Trading market data, backtests, factor analysis, screening, research swarms, Shadow Account reports, or MCP tool discovery.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a user asks to set up, create, prepare, or start a brief Obsidian PaperRead draft or paper-reading note.
Use when a user asks to review, critique, fact-check, strengthen, or annotate an existing Obsidian PaperRead or paper-reading note by adding source-backed comments inside that note.
Use when a user wants to read current articles from configured WeChat subscriptions, configure selected sources, or receive an incremental scheduled digest through BestBlogs.
Find, check, classify, add, or repair one academic paper across public scholarly sources and the user's Zotero Research library. Use for a title, DOI, arXiv ID/URL, or publisher URL when the user asks whether the paper is saved, where it belongs, or asks to add/save/import it with a verified PDF and Research/ReadLater filing.
Maintain a Karpathy-style, source-backed research LLM Wiki in the user's Obsidian vault. Use when the user asks to ingest papers, Zotero items, web clips, PDFs, or paper notes into `Research/LLM Wiki`; query or synthesize from that wiki; file durable research analyses; lint the wiki for stale claims, missing citations, orphan pages, duplicate concepts, or contradictions; or mentions `$research-llm-wiki ingest`, `$research-llm-wiki query`, or `$research-llm-wiki lint`.
Use when the user asks to explain, teach, clarify, compare, walk through, or help them understand a concept, system behavior, error, or code; especially for why/how questions or when a definition alone is not enough. Do not use for execution-only requests or simple facts that need only a terse answer.
| name | vibe-trading |
| description | Use when finance workflows need Vibe-Trading market data, backtests, factor analysis, screening, research swarms, Shadow Account reports, or MCP tool discovery. |
Use Vibe-Trading for research-heavy finance work: market data, backtests, factor analysis, screening, research swarms, trade-journal analysis, and Shadow Account reports. Use Alpaca MCP for direct Alpaca account, order, asset, crypto, options, and news workflows.
| Need | Prefer |
|---|---|
| Research a strategy or market thesis | vibe_trading |
| Fetch broad market data or fundamentals | vibe_trading |
| Run a backtest, factor analysis, or screen | vibe_trading |
| Run a multi-agent research swarm | vibe_trading |
| Analyze trade journals or Shadow Account reports | vibe_trading |
| Inspect or change Alpaca account/orders | Alpaca MCP |
The toolbox plugin launches the upstream PyPI package with uvx --from vibe-trading-ai vibe-trading-mcp, tracking the latest published version. Optional provider and data-source overrides may live under CODEX_SECRETS_DIR. Native Vibe-Trading state, provider config, run history, and connector profiles live under VIBE_TRADING_HOME.
Do not put API keys, OAuth state, broker credentials, or .env contents in the toolbox repo.
After setup, verify the MCP server is visible:
codex mcp list
For live discovery, start the configured command through an MCP client and confirm tools such as list_skills and get_market_data are present before relying on the integration.
Vibe-Trading's MCP surface is for research and read-oriented connector workflows; it is not the default path for direct broker order actions. Treat generated files, backtest runs, reports, connector selection, and swarm execution as local state changes under VIBE_TRADING_HOME.