菜单
Use at the end of a cryptozavr research session (or when the user asks "wrap up" / "what did we do"). Produces a disciplined 3-bullet summary — artifacts produced, decisions made, what's next — so the next session starts warm.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when the user asks a crypto-research question that needs multiple tool calls (ticker + OHLCV, comparison, trend analysis, liquidity check). This skill explains the research loop, when to call which tool, and how to structure findings.
Use when the user brings a declarative trading strategy (StrategySpec payload, a saved strategy id, or a plain-language "review my strategy" request). This skill runs the validate → explain → backtest → compare/stress → save loop against the Phase-2 MCP tools and packages the findings in a Claude-friendly order.
Use when a cryptozavr tool returns degraded/stale data, times out, or reports an upstream failure (KuCoin/CoinGecko). Walks through the L2 infrastructure chain, inspects provider metrics, and pinpoints whether the issue is rate limiting, transport, provider downtime, or cache staleness.
Use when you've just received output from a cryptozavr MCP tool (ticker, OHLCV, orderbook, trades) and need to read it correctly. Covers field meanings, staleness flags, reason_codes, and common pitfalls.
| name | post-session-reflection |
| description | Use at the end of a cryptozavr research session (or when the user asks "wrap up" / "what did we do"). Produces a disciplined 3-bullet summary — artifacts produced, decisions made, what's next — so the next session starts warm. |
Use this skill when the user signals the session is winding down (phrases like "wrap up", "what did we do", "summarize", "done for today"), or immediately after a multi-tool research collage that warrants a recap.
- **Produced**: <artifacts — tool outputs, files, commits, plan docs>
- **Decided**: <non-obvious choices made this session, with the reason>
- **Next**: <explicit next step, owner, and trigger condition>
- **Produced**: `MetricsDecorator` + `HealthMonitor` (commits b7c6991, bb1b8aa) and 24 new unit tests in `tests/unit/observability/`.
- **Decided**: Prometheus-compatible dict snapshot over text format for now — keeps the surface JSON-serialisable until we add the HTTP endpoint in Phase 2.
- **Next**: Wire `HealthMonitor.start()` into `build_production_service` and expose `venue_health_check_total` via `/cryptozavr:health` when Supabase is reachable again.
venue-debug instead).feature-dev skill's plan format there.