CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, highly actionable single-API skill body with a copy-paste example, full schema, and clear error/safety guidance. Minor gains are available from tightening intro redundancy and explicitly sequencing a response-validation step.

Suggestions

Trim the intro paragraph's restatement of triggers already in the description, keeping only the added asset-type detail to improve conciseness.

Add an explicit short sequence (check upstreamUnavailable, then interpret events; on 429 retry with backoff) to raise workflow clarity toward the top anchor.

DimensionReasoningScore

Conciseness

The body is lean with no concept-explanation padding and assumes competence; the only minor trim is the intro restating trigger language already in the description, placing it just below the leanest anchor.

4 / 5

Actionability

A copy-paste-ready curl example with headers, URL-encoded params, and a jq pipe, plus a full parameters table with a JMESPath example and a complete response JSON, make the guidance fully executable and cover the common cases.

5 / 5

Workflow Clarity

The single authenticated GET is unambiguous and the Errors section provides a 429 retry/backoff feedback loop plus upstreamUnavailable handling; it stops short of an explicitly sequenced validate-then-interpret checklist, fitting just below the top anchor.

4 / 5

Progressive Disclosure

Sections are well-organized and the References are clearly signaled one-level external URLs, but the detailed parameters table and full response JSON are reference-grade material kept inline, so it sits just below the cleanly-split top anchor.

4 / 5

Total

17

/

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, concise description that clearly answers both 'what' and 'when' with natural trigger terms and a well-defined domain. It could push higher by enumerating more concrete actions and adding trigger synonyms.

Suggestions

Add one or two more concrete retrieval actions (e.g., filter by asset type or ongoing status) to lift specificity beyond a single named action.

Include common synonyms in the trigger clause such as 'out of service', 'embargoed', or 'force majeure' to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('pipelines and storage facilities') and one concrete action ('Retrieve the curated energy disruption event log'), but does not list several specific actions, matching the anchor for domain plus 1-2 concrete actions rather than comprehensive coverage.

3 / 5

Completeness

It explicitly states what it does ('Retrieve the curated energy disruption event log...') and when to use it ('Use when the user asks what energy assets are disrupted...') with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Natural user-facing terms ('disrupted, sanctioned, offline, or under watch') give good keyword coverage, but synonyms such as 'out of service' or 'embargoed' are missing, so it falls short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche (disruption event log for pipelines/storage) is mostly distinct with specific triggers, but 'what energy assets are disrupted' carries minor overlap risk with closely related energy skills, fitting just below the clear-niche anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
koala73/worldmonitor
Reviewed

Table of Contents

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.