CtrlK
BlogDocsLog inGet started
Tessl Logo

energy-procurement

Codified expertise for electricity and gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management.

48

Quality

53%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/energy-procurement/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

48%Scale 1-5

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

This skill contains genuinely valuable domain expertise with strong decision frameworks, concrete numerical benchmarks, and well-structured escalation protocols. However, it is severely over-long for a SKILL.md file — it reads as a comprehensive training manual rather than a concise skill that respects Claude's existing knowledge. The core knowledge sections explaining basic concepts (what demand charges are, how LMP works, what RECs are) should be drastically condensed or moved to reference files, keeping only the decision-relevant thresholds and non-obvious insights.

Suggestions

Move the bulk of 'Core Knowledge' sections (Pricing Structures, Market Structures, Sustainability Reporting) to reference files, keeping only decision-critical thresholds and non-obvious gotchas in the main SKILL.md.

Add executable artifacts: calculation templates (e.g., load factor formula as a ready-to-use spreadsheet formula or Python snippet), RFP template outlines, or PPA financial model structures rather than just describing what to evaluate.

Eliminate the duplicate 'When to Use' sections (appears at both the top and bottom of the file).

Condense explanatory text that teaches basic energy concepts Claude already knows — for example, replace the full paragraph explaining what demand charges are with just the key insight about the 15-minute interval measurement and the specific $/kW ranges that matter for decisions.

DimensionReasoningScore

Conciseness

The skill is extremely verbose at ~400+ lines, extensively explaining concepts Claude already knows (what LMP is, what RECs are, how load factors work, basic market structures). It reads like a textbook or training manual rather than a concise skill file. Much of the core knowledge section could be reduced to key parameters and decision-relevant thresholds.

2 / 5

Actionability

The skill provides concrete numerical thresholds, decision frameworks, and specific examples (e.g., demand charge calculations, PPA evaluation criteria, escalation protocols with timelines). However, it lacks executable code, specific tool commands, or copy-paste ready artifacts like RFP templates or calculation formulas. The guidance is detailed but more descriptive than executable.

3 / 5

Workflow Clarity

The decision frameworks provide clear sequenced steps (procurement strategy selection, PPA evaluation, demand charge ROI). The escalation protocols table with triggers, actions, and timelines is well-structured. However, explicit validation/verification checkpoints and feedback loops are mostly absent — for example, the PPA evaluation framework lists considerations but doesn't include a 'validate assumptions before proceeding' step.

4 / 5

Progressive Disclosure

The skill references three external files (decision-frameworks.md, edge-cases.md, communication-templates.md) with clear signaling, which is good structure. However, the massive amount of core knowledge content inlined in the SKILL.md should largely be in those reference files instead. The main file should be an overview with key thresholds and decision rules, not a comprehensive textbook. No bundle files were provided to verify the references exist.

3 / 5

Total

12

/

20

Passed

Description

57%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.

The description identifies a clear niche domain (energy procurement and cost management) with several specific capabilities listed. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. The opening phrase 'Codified expertise for' is vague framing that could be replaced with active verbs describing what the skill does.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user asks about utility bills, energy procurement, electricity rates, PPA contracts, or reducing energy costs across facilities.'

Replace 'Codified expertise for' with active verb phrases like 'Analyzes and optimizes electricity and gas procurement...' to make the description more action-oriented.

Include common synonyms and related terms such as 'utility bills', 'power purchase agreement', 'energy audit', 'rate schedule', and 'kWh' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Lists several specific actions: electricity/gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. These are concrete domain-specific capabilities, though 'codified expertise' is somewhat vague framing.

4 / 5

Completeness

Has a reasonable 'what' (the listed capabilities), but completely lacks any 'when' clause or trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 3, and the 'what' is framed abstractly as 'codified expertise' rather than concrete actions, pushing it to 2.

2 / 5

Trigger Term Quality

Contains good domain-specific keywords like 'electricity', 'gas procurement', 'tariff', 'demand charge', 'renewable PPA', 'energy cost' that users in this domain would naturally use. Missing some synonyms like 'utility bills', 'power purchase agreement' (spelled out), 'rate optimization', or 'energy audit'.

4 / 5

Distinctiveness Conflict Risk

The energy procurement and tariff optimization domain is fairly niche and specific. There's minor overlap risk with general financial analysis or sustainability skills, but the specific terms like 'demand charge management' and 'renewable PPA evaluation' create a distinct identity.

4 / 5

Total

14

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.