CtrlK
BlogDocsLog inGet started
Tessl Logo

assess-energy-shock

Model oil or gas supply shock exposure for a country and chokepoint. Use when the user asks how an energy disruption could affect fuel supply, strategic cover, or product deficits.

71

Quality

89%

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

88%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 tight, executable API skill: authentication, endpoint, parameters, response semantics, a worked example, error handling, and neighboring-skill disambiguation are all present with essentially no filler. The only structural opportunity is moving the response-shape and gas-semantics detail into a reference file.

DimensionReasoningScore

Conciseness

The body is dense API documentation with no padding and no explanations of concepts Claude already knows; every caveat (coverage flags, gas model basis, deprecation) carries non-obvious domain information. A few of the gas-semantics sentences (e.g. around "A recent response does not make observations current") could be slightly tightened, matching anchor 4 rather than the every-token-earns-its-place bar of 5.

4 / 5

Actionability

The content is fully executable: a copy-paste curl with all parameters and a jq projection, a parameter table with concrete enums and clamping rules, exact auth header format, and explicit error codes - matching anchor 5's copy-paste-ready standard covering the common case.

5 / 5

Workflow Clarity

This is a single-action skill and the action is unambiguous: authenticate with X-WorldMonitor-Key, call the endpoint with documented parameters, interpret the response flags (dataAvailable, coverageLevel, degraded, limitations), and handle the listed errors. No destructive or batch operations exist, so no validation checkpoint is required and the simple-skill exception applies.

5 / 5

Progressive Disclosure

Sections are clearly organized with well-signaled one-level-deep external references (OpenAPI, auth matrix, docs), but there are no bundle files and all ~110 lines of parameter, response-shape, and semantic detail live inline in SKILL.md; the response-shape and gas-semantics material could arguably be split into a reference file, placing this at anchor 4 rather than 5.

4 / 5

Total

18

/

20

Passed

Description

87%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 that pairs a concrete, well-scoped capability statement with an explicit "Use when the user asks" trigger clause in third person. Trigger coverage is good but omits a few natural variations that users would plausibly say.

DimensionReasoningScore

Specificity

"Model oil or gas supply shock exposure for a country and chokepoint" states a concrete action with an enumerated scope (fuel modes, country, chokepoint), making it more specific than anchor 3's generic 1-2 actions, but it is a single action verb rather than a list of several specific actions, so it falls short of anchor 5.

4 / 5

Completeness

The description explicitly answers both what ("Model oil or gas supply shock exposure for a country and chokepoint") and when ("Use when the user asks how an energy disruption could affect fuel supply, strategic cover, or product deficits") with concrete trigger phrases, in third-person voice - an exact match for anchor 5.

5 / 5

Trigger Term Quality

"energy disruption", "fuel supply", "strategic cover", and "product deficits" are natural user phrasings, giving good coverage; however common variations a user might actually say ("LNG", "Hormuz", "chokepoint closure") appear only in the body, not the description, keeping it below the comprehensive-synonyms bar of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The country-plus-chokepoint scenario-modeling niche with distinctive terms like "strategic cover" and "product deficits" is clearly set apart from adjacent skills (static energy profiles, storage observations, asset-level disruption monitoring), matching anchor 5's clear-niche bar.

5 / 5

Total

18

/

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.