メニュー
Operate TradingCodex server, dashboard, MCP, runtime mode, update status, and read-only broker connector status without build or execution authority.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use TradingCodex build mode for self-update, harness/template changes, Codex config/MCP customization, and broker/API provider scaffold or implementation without submitting live orders.
Coordinate TradingCodex operate-plane investment workflows by turning hook intake hints into validated staged workflow plans, dispatching fixed-role subagents from the recorded plan, evaluating artifacts, and synthesizing only after accepted role outputs.
Analyze business fundamentals for an investment workflow. Use for business model, financial statement quality, management, capital allocation, and fundamental risk reports.
Evaluate portfolio fit before an order draft, including exposure, sizing context, concentration, liquidity, holding period, opportunity cost, and draft readiness.
Review investment and order risk before drafting or approving an order, including downside cases, sizing limits, liquidity, volatility, policy constraints, and go/revise/reject decisions.
Review valuation after research evidence exists. Use for valuation method selection, assumptions, market-implied expectations, scenario ranges, sensitivity, and valuation risk.
| name | tcx-server |
| description | Operate TradingCodex server, dashboard, MCP, runtime mode, update status, and read-only broker connector status without build or execution authority. |
Use this skill for operate-plane TradingCodex status checks, service recovery, dashboard URL guidance, MCP setup, runtime mode status, update status, and safe broker connector inspection.
.tradingcodex/mainagent/server-status.json and .tradingcodex/mainagent/session-start.json../tcx service status, ./tcx doctor --layer service, and ./tcx doctor --layer mcp when status is stale or unhealthy../tcx mode status and ./tcx update status --json for mode/update posture.tcx mode set build --reason <reason> is required, or give the terminal command.service_issue=version_mismatch, db_mismatch, or port_occupied, report the issue with service/package versions or DB paths when present, and give the recorded next action before opening or recommending the dashboard. For a stale same-DB TradingCodex service, prefer ./tcx service stop and Codex restart so MCP autostart can launch the current package.tcx update unless update_status.can_self_update=true and the user explicitly asks.