CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

81%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 highly actionable single-endpoint API skill: executable worked example, complete parameter and response documentation, explicit response-validation flags, and error-recovery guidance. The weaknesses are presentation, not substance — duplicated and run-on interpretation prose that could be tightened, and interpretation rules that could be split into a reference file.

Suggestions

Remove the duplicated sentence "Missing or invalid LNG imports or nonpositive demand suppress `gasSensitivity`. Observed zero LNG imports remain valid.", which appears verbatim at the end of both the oil-baseline paragraph and the stock-cover paragraph.

Break the 200+ word run-on paragraphs on baselines and stock cover into bullets or a small table keyed by `basis` mode (comtrade_monthly, national_monthly, comtrade_annual), keeping each rule to a single line.

Move the detailed field-semantics rules (cover derivation, product demand fallbacks, gas model bases) into a reference file and keep a short 'How to read the response' checklist inline, which would improve both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

Almost all content is API-specific semantics Claude cannot know (basis fallbacks, bypass rerouting, rounding caveats, deprecation notes), so it is not padded with known concepts (level 2); however, the baseline and cover paragraphs are 200+ word run-ons and "Missing or invalid LNG imports or nonpositive demand suppress `gasSensitivity`. Observed zero LNG imports remain valid." appears verbatim twice, which goes beyond level 4's 'minor instances that could be trimmed'.

3 / 5

Actionability

The skill provides a copy-paste-ready curl with the auth header, URL-encoded parameters, and a jq projection, a full parameter table with constraints ("integer 10-100 ... Values below `10` are clamped to `10`"), a complete JSON response example, and error handling ("`429` - rate limited; retry with backoff"), fully covering the common case per the level 5 anchor.

5 / 5

Workflow Clarity

This is a single-task, read-only skill whose one action (authenticated GET) is unambiguous and demonstrated end-to-end in the worked example, with explicit response-validation checkpoints ("`dataAvailable: false` or `coverageLevel: 'unsupported'` means inputs are insufficient, not zero exposure") and error-recovery guidance, so the simple-skill exception applies; the destructive/batch cap is irrelevant.

5 / 5

Progressive Disclosure

Sections are clear and well-labeled (Authentication, Endpoint, Parameters, Response shape, Worked example, Errors, When NOT to use) and the external references are clearly signaled and one level deep ("OpenAPI: ... operation `ComputeEnergyShockScenario`"), but the ~50 lines of dense response-interpretation rules are inlined in SKILL.md rather than split into a reference file, a minor organization gap that keeps it below level 5.

4 / 5

Total

17

/

20

Passed

Description

82%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: it explicitly states what the skill does and when to use it, with concrete trigger phrases and a clearly distinct niche. Its only gaps are the single-action framing (rather than enumerating several capabilities) and missing common synonyms such as LNG or named chokepoints like Hormuz.

DimensionReasoningScore

Specificity

"Model oil or gas supply shock exposure for a country and chokepoint" names the domain and one concrete action, matching the '1-2 concrete actions, but not comprehensive' anchor; it does not list several distinct actions (level 4), as capabilities like product deficits and cover days only appear as trigger scenarios.

3 / 5

Completeness

It explicitly answers 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, matching the level 5 anchor; the 'when' is already explicit and specific, so level 4's 'could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural terms like "oil", "gas", "supply shock", "energy disruption", and "fuel supply" match what users would say, giving good keyword coverage; common variations such as "LNG", "closure/blockage", or named straits (Hormuz, Malacca) are missing, so it falls short of level 5's comprehensive synonym coverage but sits above level 3's 'missing common variations'.

4 / 5

Distinctiveness Conflict Risk

The country-plus-chokepoint supply-shock scenario niche ("oil or gas supply shock exposure for a country and chokepoint") is highly specific with distinct triggers and minimal conflict risk against generic energy-profile or monitoring skills, matching the level 5 anchor.

5 / 5

Total

17

/

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

Path

public/.well-known/agent-skills/assess-energy-shock/SKILL.md

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.