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.

60

Quality

70%

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 ./plugins/AI-Agents-Safe-Coding-Skills/skills/energy-procurement/SKILL.md

The canonical home for this skill is energy-procurement in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a well-structured, actionable expertise skill with excellent progressive disclosure pointing to real bundle files and concrete decision frameworks. Its main weakness is conciseness — duplicated "When to Use" sections and edge-case re-summaries add length without new information.

Suggestions

Remove the duplicate "When to Use" section at the bottom (lines 198–203) or consolidate it with the opening one to eliminate redundancy.

Trim the Key Edge Cases summaries that restate Core Knowledge content (Uri, basis risk, ratchet) to just the novel lesson plus the pointer to edge-cases.md.

Add explicit validation checkpoints inside the decision frameworks (e.g., "re-run the load-factor calculation before finalising block sizing") to lift workflow clarity toward 5.

DimensionReasoningScore

Conciseness

The ~196-line body is mostly valuable specialized operational knowledge Claude does not already know, but it carries notable redundancy: the "When to Use" section appears twice (top and bottom) and the Key Edge Cases re-summarize material already covered in Core Knowledge (Uri, basis risk, ratchet), so it could be tightened; not a 4 because the duplication exceeds minor over-explanation.

3 / 5

Actionability

Provides concrete, specific guidance — numbered decision frameworks with explicit thresholds ("simple payback < 5 years"), a load-factor formula, RFP steps ("issue RFPs to 5–8 qualified REPs"), and ready-to-use communication scripts — but a meaningful portion (Utility Bill Anatomy, Market Structures) is explanatory reference knowledge rather than direct executable steps, keeping it below 5.

4 / 5

Workflow Clarity

Multi-step processes (Procurement Strategy Selection, PPA Evaluation, Demand Charge Mitigation ROI, Market Timing) are clearly sequenced, and the escalation protocols plus performance indicators function as monitoring checkpoints; however explicit validate→fix→retry feedback loops are largely absent, so it stops at 4 rather than 5. No destructive/batch cap applies.

4 / 5

Progressive Disclosure

The body is an overview that clearly signals one-level-deep references to three real bundle files (decision-frameworks.md, edge-cases.md, communication-templates.md) via markdown links and an Additional Resources section, with content appropriately split and easy to navigate, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

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

The description is specific and highly distinctive, naming a clear niche with good natural trigger terms, but it omits any explicit "Use when..." trigger guidance, which caps its completeness. Adding a trigger clause would raise the strongest-scoring opportunity.

Suggestions

Append an explicit "Use when..." clause, e.g. "Use when evaluating electricity/gas tariffs, PPAs or VPPAs, demand charges, or multi-facility energy cost strategies."

Lead with concrete action verbs (e.g. "Optimise tariffs, evaluate PPAs, manage demand charges") instead of the abstract "Codified expertise for" framing.

Add common synonyms users might say, such as "power purchase agreements", "utility bills", and "reduce energy costs", to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists five concrete capability areas — "electricity and gas procurement, tariff optimisation, demand charge management, renewable PPA evaluation, and multi-facility energy cost management" — giving comprehensive domain coverage, though the "Codified expertise for" framing and noun-phrase list lack explicit action verbs, keeping it below a 5.

4 / 5

Completeness

The description clearly answers "what" via its enumerated capabilities but contains no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3; it is not a 4 because the "when" is entirely absent rather than weakly implied.

3 / 5

Trigger Term Quality

Contains multiple natural domain terms a user would say ("energy procurement", "tariff optimisation", "demand charge management", "PPA evaluation"), but misses common synonyms and phrasings like "power purchase agreement" spelled out, "utility bills", or "reduce energy costs", so not a 5.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific — commercial/industrial energy procurement, PPAs, demand charges, capacity tags — with distinct triggers and minimal overlap risk against other skills, matching the anchor for a clear niche.

5 / 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.

Validation15 / 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
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.