What problem does it solve? Developers working with the packages/investing monorepo package face a confusing surface: five distinct subsystems (Alpaca brokerage, stock data, Polymarket sync, LangGraph debate agents, and the merged PredictOS prediction-market core), subpath exports that silently resolve to nothing, and a former standalone predictos package whose imports broke after the merge. This Skill maps every task to the correct import path, call signature, and environment variable, and provides a troubleshooting table for the most common failures. ## Core Features & Use Cases - Import and API routing: Maps each task (equity trading, quotes, SEC filings, Polymarket data, debate agents, arbitrage) to the exact export and subpath such as investing/predictos or investing/stocks. - PredictOS agent workflows: Documents the full URL-to-order pipeline using getEvents, runEventAnalysisAgent, runBookmakerAgent, runMapperAgent, and findArbitrage, including config objects and error behavior like NoTradeError. - Troubleshooting guide: Covers broken subpath exports, missing model/url parameters, D1 connection failures, DOME/DFlow 401 errors, and stale README API names. - Use Case: A developer whose predictos import broke after the merge uses this Skill to learn the code now lives at investing/predictos, then follows the recipe to run an event analysis with a Grok model and map the result to Polymarket order parameters. ## Quick Start Ask the assistant how to run a prediction-market event analysis from a Polymarket or Kalshi URL using the investing package.
