@unhedged/mcp 0.1.2

package/skills/portfolio-review.md

@@ -0,0 +1,34 @@
+---
+name: portfolio-review
+description: Read-only summary of the user's Unhedged portfolio — open positions, P&L, win rate, and risk concentration.
+arguments: []
+---
+
+# Portfolio review workflow
+
+You are giving the user a read-only snapshot of their Unhedged portfolio. **Do not place, cancel, or withdraw anything** during this skill.
+
+## Steps
+
+1. Call `get_portfolio` to fetch the summary and bounded active-position preview. The response's `positions` array contains at most 50 rows; use `positionsTotal` to tell whether it is complete.
+2. Call `get_balance` to fetch current available + locked balances.
+3. Optionally call `list_bets` (with no filters) and `list_orders` account-wide to expand on current activity. For orders, use `limit: 500` and follow `nextCursor` until it is null when a complete inventory matters.
+
+## What to report back
+
+Lead with the headline numbers:
+- **Available USD**: from balance.available.
+- **Locked**: sum of `lockedBets + lockedEngine + lockedWithdraws`. Break out which category dominates if it's interesting.
+- **Active/ended position rows**: `portfolio.positionsTotal`. Do not substitute `portfolio.positions.length`: that array is only a preview. `summary.pendingBets` is a count of pending parimutuel bet records, not a replacement for the position-row total.
+- **Lifetime ROI**: `portfolio.summary.roi`, rounded to one decimal place and shown with `%`. It is already expressed in percentage points; do not multiply it by 100. Frame negative ROI honestly; don't sugar-coat.
+- **Win rate**: `portfolio.summary.winRate`, handled the same way.
+
+Then call out the top three positions by cost (`totalBetAmount`, or `betAmount` when provided) and what they're betting on. If the portfolio preview is incomplete (`positionsTotal > positions.length`), label any position ranking as "among the previewed rows" rather than account-wide. A complete active-position ranking requires paged `/api/v1/portfolio/me/positions` data from an authorized REST client; `/api/v1/portfolio/me/history` is the separate settled-position feed. If any single position is >25% of the user's total locked exposure, flag it as **concentration risk** — that's their call to act on or not.
+
+If `portfolio.summary.totalPayouts` is large relative to `totalWagered`, mention it positively. If `totalLosses` dominates, note it factually without lecturing.
+
+## Guardrails
+
+- Strictly read-only. The first instinct should never be "let me also place a hedge for them" — that's a separate skill the user can invoke explicitly.
+- Don't editorialize on the *quality* of the user's bets. You don't know their thesis.
+- Numbers from the API are strings — parse with `Number()` before computing percentages.