CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

energy-procurement

Codified expertise for electricity and gas procurement, tariff optimization, demand charge management, renewable PPA evaluation, and multi-facility energy cost management. Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers. Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks. Use when procuring energy, optimizing tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.

Quality

76%

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

The canonical home for this skill is energy-procurement in affaan-m/ECC

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 body is an unusually actionable advisory skill — numeric thresholds, worked formulas, sequenced decision frameworks, escalation tables, and ready-to-use stakeholder scripts — with a clear six-step workflow. It is held back by a padded persona narrative, duplication between Core Knowledge and Key Edge Cases, and a fully monolithic structure with no reference files despite content that clearly belongs in them.

Suggestions

Move the eight edge-case playbooks and the market-structure reference material (ISO descriptions, LMP components, capacity tag mechanics) into references/ files, keeping only brief summaries with clearly signaled links in SKILL.md.

Trim the 'Role and Context' persona narrative to the few facts that change decisions (multi-site C&I portfolio, budget-certainty vs. cost tradeoff) — the rest restates what the knowledge sections already imply.

Deduplicate content appearing in both Core Knowledge and Key Edge Cases (the Winter Storm Uri example and the demand ratchet mechanics) by cross-referencing the earlier section instead of repeating it.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain specifics ('$8–$25/kW', '60–80% of the highest peak demand', 'PLC is measured at your meter during the system coincident peak'), but the persona narrative ('You are a senior energy procurement manager... annual energy spend of $15M–$80M across 10–50+ sites') is padding, and Key Edge Cases repeats Core Knowledge — the Winter Storm Uri $1.5M example and ratchet mechanics each appear twice. Not 4 because the persona section and duplication are noticeable; not 2 because nearly all content is domain data Claude does not already know, not explanation of familiar concepts.

3 / 5

Actionability

Fully concrete instruction guidance: worked formulas ('Load factor = (Total kWh) / (Peak kW × Hours in period)'), explicit decision thresholds ('If simple payback < 5 years with stacked value, the investment is typically justified'), step-by-step procedures ('Calculate current demand charges: Peak kW × demand rate × 12 months'), and ready-to-use stakeholder scripts ('ICE forward curves for 2027 are showing $42/MWh for AEP Dayton Hub. Your quote of $48/MWh reflects a 14% premium...'). For an instruction-only skill this is copy-paste-ready guidance covering the common cases.

5 / 5

Workflow Clarity

'How It Works' gives a clear six-step sequence (profile load → analyze tariffs → structure RFP → evaluate bids → execute contracts → monitor and rebalance), and the escalation table ('Wholesale prices exceed 2× budget assumption for 5+ consecutive days | ... | Within 24 hours') plus monthly KPI review provide real checkpoints. Not 5 because the workflow steps lack explicit validation checkpoints (e.g., verifying interval data completeness before load profiling); not 3 because monitoring triggers and escalation protocols function as feedback loops, and this is an advisory skill so no destructive/batch cap applies.

4 / 5

Progressive Disclosure

Well-sectioned with headers, but the ~30KB body is monolithic — no references/, scripts/, or assets/ directories exist, and content that belongs in reference files (eight edge-case playbooks, ISO market structure details, LMP components, communication patterns) is fully inlined. The body itself acknowledges the gap ('Brief summaries are included here so you can expand them into project-specific playbooks'). Not 4 because nearly all reference-grade content is inline with no bundle files; not 2 because section structure is strong and edge cases are deliberately kept as brief summaries.

3 / 5

Total

15

/

20

Passed

Description

75%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 establishes a specialized niche in commercial/industrial energy procurement with an explicit 'Use when' clause and broad, domain-specific capability coverage. Its main weaknesses are a credential-padding sentence, trigger terms that restate the capability list rather than mirroring natural user phrasing, and missing common synonyms like 'utility bills' or 'renewable energy'.

Suggestions

Remove the credential sentence ('Informed by energy procurement managers with 15+ years experience at large commercial and industrial consumers') — it is unverifiable fluff that dilutes the capability statement.

Diversify the 'Use when' triggers beyond restating the capability list by adding user-natural contexts such as 'reviewing utility bills', 'comparing supplier quotes', 'renewing an electricity contract', or 'buying renewable energy'.

Spell out 'PPA (Power Purchase Agreement)' at first mention and add synonyms such as 'utility rates' and 'energy suppliers' so the description matches how users actually phrase requests.

DimensionReasoningScore

Specificity

Lists broad, domain-specific capabilities — 'tariff optimization, demand charge management, renewable PPA evaluation' plus 'market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks' — but frames them as expertise domains ('Codified expertise for...') rather than concrete actions, and the credential line 'Informed by energy procurement managers with 15+ years experience' adds no capability information. Not 5 because the actions are nominalizations with minor gaps; not 3 because coverage is comprehensive and specific to the domain.

4 / 5

Completeness

Both parts are explicit: the what ('Includes market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks') and the when ('Use when procuring energy, optimizing tariffs, managing demand charges, evaluating PPAs...'). Not 5 because the when-clause largely restates the capability list instead of adding distinct user trigger contexts, and the credential sentence dilutes the what; not 3 because both what and when are clearly present.

4 / 5

Trigger Term Quality

The trigger clause 'Use when procuring energy, optimizing tariffs, managing demand charges, evaluating PPAs, or developing energy strategies' contains natural domain phrases a user would say, but misses common variations such as 'utility bills', 'electricity rates', 'renewable energy', or 'power purchase agreement' spelled out (PPA appears only as an acronym). Not 5 because several natural synonyms are missing; not 3 because keyword coverage is good rather than partial.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche in commercial and industrial energy procurement with distinctive triggers like 'demand charge management' and 'renewable PPA evaluation'; minor overlap risk remains with general sustainability or utilities skills via 'sustainability reporting frameworks'. Not 5 because of that overlap; not 3 because the triggers are highly domain-specific and unlikely to fire for unrelated skills.

4 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository

valeriibeck-star/claude-skills

Path

skills/energy-procurement/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.