MCP skill examples

# $boros-carry-inputs

Use when the user asks for Boros carry inputs, funding-minus-implied APR, 7d or 30d funding averages, or current implied versus observed floating context.

## MCP workflow
1. Call `screen_markets` with `status: "live"` and any asset or venue filters.
2. Treat `sort` as row ordering only. Do not call sorted rows recommendations.
3. For selected markets, call `get_market_parameters` and `get_recent_trades`.
4. Call `check_freshness` before summarizing.

## Output
- Current implied APR and floating APR.
- 7d and 30d average funding APR with sample counts.
- Funding-minus-implied APR fields as observed data, not advice.
- OI, recent volume, recent trades, margin floor, available fee/margin coverage, and caveats.
- Missing external assumptions needed for a trade model.

## Do not
- Treat high carry deltas as trade recommendations.
- Hide sample-count or freshness gaps.
- Treat YU/notional fields as USD unless a USD field is present.

# $boros-settlement-window

Use when the user asks what settlement rates have been since a timestamp, whether a claim about historical settlement rows was right, or how a market settled over a bounded window.

## MCP workflow
1. Resolve the target market with `lookup_market` if the market ID is unknown.
2. Call `get_settlements` with `timestampFrom`, optional `timestampTo`, `limit: 100`, and `includeWindowTotals: true` when simple full-window stats are enough.
3. Follow `pagination.nextPage` while `hasNextPage` is true.
4. Call `get_market_detail` only when maturity, current rates, or market identity needs confirmation.
5. Call `check_freshness` before finalizing.

## Output
- The row count and exact inclusive timestamp window.
- Raw settlement rows or a concise row-derived table, depending on user request.
- `pageSummary` for returned rows, `sourcePageSummary` for the underlying server page, and `windowTotals` when requested.
- Agent-computed medians, custom extrema, and threshold counts only after all needed rows are fetched.
- Context source, context timestamp, contextUnavailableReason, markPriceUnavailableReason, and comparability caveats.

## Do not
- Treat `summary.total` as the returned page count; use `pageSummary.total` for that.
- Mix exchange funding APR and Boros context fields without labeling them.
- Ignore pagination.

# $boros-protocol-activity-brief

Use when the user asks what is going on with Boros today, which markets are moving, or whether activity changed over a recent window.

## MCP workflow
1. Call `get_protocol_activity` with the user's requested `windowHours` or the 24 hour default.
2. Include market movers and recent events unless the user asks for headlines only.
3. Use `get_protocol_summary` when the user only wants headline counts.
4. Call `check_freshness` if the answer depends on recency.

## Output
- `windowAggregates` for windowed activity facts, `protocolState.stateAtWindowEnd` and `protocolState.latestMarketDirectory` for state fields, and previous-window changes.
- Market movers by observed OI or trade-volume changes.
- Recent largest trades, normalized liquidation rows, and expiring markets when included.
- `timeSemantics` when the request supplied or omitted `timestampTo`, especially if a future timestamp was clamped.
- Clear separation between facts and interpretation.

## Do not
- Turn movers into recommendations.
- Label gross indexed fees as protocol revenue.
- Hide stale-source caveats.