Review and validate pending predictions against current market data. Usage: /validate-predictions
Scanned 5/27/2026
Install via CLI
openskills install hugoguerrap/crypto-claude-desk---
name: validate-predictions
description: Review and validate pending predictions against current market data. Usage: /validate-predictions
user-invocable: true
---
# Validate Predictions
Review all pending predictions and check them against current market data.
## Workflow
### Step 0: Auto-Find Expired Predictions
Delegate using the Task tool with `subagent_type: general-purpose` and `model: opus`:
"You are the learning-agent. Read agents/learning-agent.md for your analysis framework.
First, use get_crypto_prices() from crypto-data MCP to get current prices for major coins (bitcoin, ethereum, solana, etc.).
Then call find_expired_predictions(current_prices='{\"BTC/USDT\": ..., \"ETH/USDT\": ...}') from crypto-learning-db to discover predictions whose timeframe has passed.
For each expired prediction, reason about how close it was and validate with an NL evaluation using validate_prediction().
Do NOT use the Edit tool."
### Step 1: Check Remaining Pending Predictions
Delegate using the Task tool with `subagent_type: general-purpose` and `model: opus`:
"You are the learning-agent. Call query_predictions(status='pending') from crypto-learning-db for predictions still within their timeframe.
For each prediction:
1. Use get_exchange_prices(symbol=...) from crypto-exchange MCP to check current price
2. Compare current price against the prediction's target_value
3. Report current progress toward or away from target
Do NOT use the Edit tool."
### Step 2: Present Results
Show a summary table:
```
## Prediction Validation Report
### Resolved This Check
| ID | Agent | Prediction | Target | Actual | Result |
|----|-------|-----------|--------|--------|--------|
### Still Pending
| ID | Agent | Prediction | Target | Current | Progress | Expires |
|----|-------|-----------|--------|---------|----------|---------|
### Overall Accuracy
- Total predictions: X
- Correct: X (X%)
- Incorrect: X (X%)
- Pending: X
### Track Record by Setup Type
| Setup Type | Total | Correct | Accuracy | Trend |
|-----------|-------|---------|----------|-------|
```
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.