Conciseness

Every section carries information Claude could not infer: the auth-header rules ('Authorization: Bearer … is for MCP/OAuth or Clerk JWTs — not raw API keys'), parameter shapes, the estimate-band guidance ('quote the band, not just the point estimate'), and sibling-skill disambiguation. There is no concept explanation or padding; every token earns its place.

Actionability

The skill gives a full endpoint URL, a concrete auth header with a sample key, a complete parameter table, the response JSON contract, and a copy-paste-ready curl command piped into jq covering the common filtered-country case. Error codes (401, 429) come with handling guidance.

Workflow Clarity

This is a simple single-purpose skill and the single action is unambiguous: authenticate with X-WorldMonitor-Key, set query params, GET the endpoint, handle 401/429 (retry with backoff), and paginate via the returned cursor. The simple-skill exception applies and no destructive/batch validation cap is triggered.

Progressive Disclosure

Sections are well organized with clear headers, and the References section signals one-level-deep external links (OpenAPI operation, auth matrix, docs). It stops short of anchor 5 because the body runs ~88 lines — above the under-50-line guideline — with the parameter table and response schema inlined where a split reference file could carry the detail.

Specificity

The description is dense with concrete detail — 'Retrieve geolocated armed-conflict events (UCDP) with parties, fatality estimates, and violence type, filterable by country and date range' — naming the data source, returned attributes, and two filter capabilities in third-person voice. It sits at anchor 4 rather than 5 because it is built around a single retrieve verb plus filtering rather than multiple distinct concrete actions.

Completeness

Both halves are explicit: the 'what' ('Retrieve geolocated armed-conflict events (UCDP) with parties, fatality estimates, and violence type, filterable by country and date range') and the 'when' ('Use when the user asks about recent fighting, attacks, or conflict activity in a country or region') with concrete trigger phrases. This matches the anchor-5 example structure exactly.

Trigger Term Quality

'Use when the user asks about recent fighting, attacks, or conflict activity in a country or region' uses natural phrasing users would actually say. It falls short of anchor 5 because common synonyms such as 'violence', 'clashes', 'casualties', or 'war' are absent.

Distinctiveness Conflict Risk

'armed-conflict events (UCDP)' carves a clear niche, but 'conflict activity in a country or region' has minor overlap risk with closely related skills (unrest/protest event data, humanitarian summaries) that the description itself does not disambiguate. That fits anchor 4 rather than the minimal-conflict anchor 5.