monitor-energy-disruptions

Retrieve the curated energy disruption event log for pipelines and storage facilities. Use when the user asks what energy assets are disrupted, sanctioned, offline, or under watch.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

96%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, highly actionable single-endpoint skill: executable example, complete parameter and response documentation, and explicit error semantics with no wasted tokens. The only structural improvement is moving the annotated response example to a reference file to tighten SKILL.md further.

Suggestions

Move the fully annotated response-shape example into a one-level-deep reference file (e.g., references/response-shape.md) and keep only the key fields inline, so SKILL.md stays a tighter overview.

Dimension	Reasoning	Score
Conciseness	Every section carries non-obvious information Claude cannot know (the X-WorldMonitor-Key vs Bearer distinction, `upstreamUnavailable` semantics, error codes) with zero padding or explanation of known concepts, matching the lean anchor 5.	5 / 5
Actionability	The worked example is a fully executable curl command with auth header, URL-encoded parameters, and a jq projection, and the parameters table plus response shape make the guidance copy-paste ready, matching anchor 5.	5 / 5
Workflow Clarity	The single action (one authenticated GET) is unambiguous, with preconditions, error recovery guidance (429 backoff, upstreamUnavailable retry), and clear response interpretation; the skill is read-only so the destructive/batch validation cap does not apply, matching the simple-skill case at anchor 5.	5 / 5
Progressive Disclosure	Sections are well organized with a clear When NOT to use and References section, but at roughly 95 body lines the full annotated response-shape example (~25 lines) is bulk that could live in a one-level-deep reference file, matching anchor 4 rather than 5.	4 / 5
	Total	19 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit what-and-when structure and natural trigger phrases. Its main gap is thin action coverage (retrieve only) and a few missing synonyms such as outage or LNG terminal that users might naturally say.

Suggestions

Enumerate one or two more concrete actions or outputs (e.g., filter by asset type or ongoing status, project selected fields) to raise specificity beyond a single retrieve action.

Add common synonyms such as "outage", "down", or "LNG terminals" and "tank farms" to the trigger clause to broaden natural keyword coverage.

Dimension	Reasoning	Score
Specificity	"Retrieve the curated energy disruption event log for pipelines and storage facilities" names the domain and one concrete action with concrete artifacts, but offers only a single action (retrieve), matching anchor 3 rather than the several-actions coverage of anchor 4.	3 / 5
Completeness	It explicitly answers both what ("Retrieve the curated energy disruption event log for pipelines and storage facilities") and when ("Use when the user asks what energy assets are disrupted, sanctioned, offline, or under watch") with concrete trigger phrases, matching anchor 5 exactly.	5 / 5
Trigger Term Quality	"disrupted, sanctioned, offline, or under watch" and "pipelines and storage facilities" are natural user phrases with good coverage, but common synonyms like "outage", "down", or "LNG terminal" are missing, so it falls between anchors 4 and 5.	4 / 5
Distinctiveness Conflict Risk	The niche (curated disruption events for energy assets) is distinct with differentiated trigger verbs, but broad terms like "offline" and "sanctioned" leave minor overlap risk with sibling energy registry or impact skills, matching anchor 4.	4 / 5
	Total	16 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: koala73/worldmonitor
Path: public/.well-known/agent-skills/monitor-energy-disruptions/SKILL.md
Commit: da33e7a

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.