Skip to content
Back to skills

Claims

ASecurity

Use when users ask about Nexus Mutual claims history, claim statistics, approval/denial rates, payout amounts, or want to analyze past claims for a product or time period.

  • 71 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 27, 2026
research

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add FDU-INS/Insurance-Skills --skill claims --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Claims?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Claims
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/fdu-ins-claims/badge)](https://www.skillsdirectory.com/skills/fdu-ins-claims)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: claims
description: "Use when users ask about Nexus Mutual claims history, claim statistics, approval/denial rates, payout amounts, or want to analyze past claims for a product or time period."
---

# Nexus Mutual Claims Analysis

You help users explore and understand Nexus Mutual's historical claims data using the `query_claims` tool.

## Tool

`query_claims` returns closed claims (V1 and V2/V3 combined) with these filters — all optional:

| Filter | Type | Behavior |
|--------|------|----------|
| `verdict` | `"approved"` or `"denied"` | Exact match |
| `productName` | string | Case-insensitive substring match |
| `productType` | string | Case-insensitive exact match (e.g. "Protocol Cover", "Multi Protocol Cover", "Custody") |
| `submitDateFrom` | date string | Inclusive start (ISO 8601 or YYYY-MM-DD) |
| `submitDateTo` | date string | Inclusive end |
| `minDollarClaimAmount` | number | Minimum USD claim amount |
| `limit` | number | Max results per call (default 50, max 100) |
| `offset` | number | Pagination offset |

Each claim includes: id, version (v1/v2), coverId, verdict, url, productName, productType, coverAsset, coverAmount, dollarCoverAmount, claimAmount, dollarClaimAmount, coverStartTime, coverEndTime, submitTime, stakingPools.

## How to Respond

- Lead with the key insight: "X out of Y claims were approved" or "Total payouts: $X".
- Use tables for multi-claim results — columns: Claim ID, Product, Verdict, Claim Amount (USD), Date.
- Link to individual claims when urls are available (V2/V3 claims with id > 28).
- When comparing products, show side-by-side totals.
- For time-based analysis, group by year or quarter.

## Pagination

Results are paginated. When `hasMore: true`, fetch the next page with `offset` before presenting totals or aggregates. Don't present partial data as complete.

## Common Questions

- **"How many claims were approved/denied?"** — Query by verdict, report counts and totals.
- **"Show claims for [product]"** — Filter by productName, present as table.
- **"What's the largest claim payout?"** — Sort results by dollarClaimAmount, or use minDollarClaimAmount to find large claims.
- **"Claims in [year/period]"** — Use submitDateFrom/submitDateTo.
- **"What products have the most claims?"** — May need multiple queries or full scan to group by product.

## Staking Pools

V2/V3 claims include `stakingPools` — the list of staking pool IDs that backed the cover. Some may contain "v1" which indicates the claim was backed by the legacy V1 staking pool.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…