CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

energy-procurement

Procure electricity and natural gas for commercial and industrial facilities: tariff and rate-schedule optimization, demand-charge mitigation, supplier RFPs, fixed/index/block-and-index hedging, renewable PPA and REC evaluation, and sustainability reporting. Use when procuring energy, optimizing utility tariffs, managing demand charges, evaluating PPAs, or building energy budgets and hedge strategies.

Quality

81%

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

63%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 knowledge-dense, well-structured domain skill with genuinely valuable specialized content (ratchet clauses, PLC capacity tags, basis risk, stacked-value battery economics) and concrete decision frameworks. Its main weaknesses are monolithic presentation — 220 lines with zero bundle files or references where edge cases, communication templates, and reference tables belong in separate files — and some re-explanation of general energy-market concepts Claude already knows.

Suggestions

Split the 'Key Edge Cases', 'Communication Patterns', and 'Escalation Protocols'/'Performance Indicators' sections into reference files (e.g., references/edge-cases.md, references/stakeholder-communications.md) and keep one-line pointers in SKILL.md, reducing the main file to an overview plus decision frameworks.

Trim explanations of general market concepts Claude already knows (the regulated vs. deregulated primer, the ISO/RTO roster, contract-for-differences mechanics) and retain only the numeric ranges and non-obvious heuristics that are not baseline knowledge.

Add explicit validation checkpoints to the 'How It Works' workflow — e.g., verify interval-data completeness before structuring the RFP, and confirm tariff ratchet provisions before recommending any load-modifying change.

DimensionReasoningScore

Conciseness

The body is efficient in that most of the numeric and domain-specific content (PLC/ratchet mechanics, REC price ranges, Winter Storm Uri exposure figures) is genuinely specialized and not Claude baseline knowledge. However, sections like Market Structures (regulated vs. deregulated explanation, ISO roster) and parts of Renewable Energy Procurement (contract-for-differences mechanics, REC definition) re-explain market concepts Claude already knows, and the ~29K character single file could be tightened throughout — matching anchor 3: 'mostly efficient but includes some unnecessary explanation or could be tightened.'

3 / 5

Actionability

For an instruction-only skill the guidance is highly concrete: numeric decision thresholds ('If simple payback < 5 years with stacked value, the investment is typically justified'), a 6-step procurement sequence, a worked hedge-ratio example ('locks 60% of volume at fixed rates while maintaining 40% index exposure'), escalation tables with timelines, and copy-adaptable communication scripts. It falls short of anchor 5 because some steps remain high-level (e.g., 'model the expected savings against forward curves' gives no method or formula for the modeling itself).

4 / 5

Workflow Clarity

'How It Works' lays out a clear 6-step sequence (profile load → analyze tariff → structure RFP → evaluate bids → execute with layering → monitor and rebalance), and the escalation protocol table plus monthly KPI red flags function as monitoring checkpoints with explicit timelines. Not a 5 because there are no explicit validate-before-proceeding steps within the workflow (e.g., confirming interval-data completeness before bidding) — checkpoints are reactive triggers rather than embedded validation.

4 / 5

Progressive Disclosure

The file has good internal section structure (Core Knowledge, Decision Frameworks, Key Edge Cases, Communication Patterns, Escalation Protocols), but it is entirely monolithic: no references/, scripts/, or assets/ exist and no content is split into separate files. Large blocks that would fit the rubric's 'separate file' pattern (edge-case playbooks, communication templates, escalation tables) are fully inlined — matching anchor 3, 'some structure but could be better organized... content that should be separate is inline.' It is not a 2 because the internal organization and headers keep it navigable despite the length.

3 / 5

Total

14

/

20

Passed

Description

92%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 enumerates concrete domain capabilities, names the target context (commercial and industrial facilities), and closes with an explicit and well-phrased 'Use when' trigger clause covering the major workflows. Its only weakness is that a few natural synonyms (RECs, renewable energy, power costs) are absent from the trigger list.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions — 'tariff and rate-schedule optimization, demand-charge mitigation, supplier RFPs, fixed/index/block-and-index hedging, renewable PPA and REC evaluation, and sustainability reporting' — with comprehensive coverage of the procurement domain. It exceeds anchor 4 because the action list spans the full lifecycle (tariffs, RFPs, hedging, PPAs, reporting) rather than leaving coverage gaps.

5 / 5

Completeness

It explicitly answers both questions: the 'what' ('Procure electricity and natural gas for commercial and industrial facilities: tariff and rate-schedule optimization...') and the 'when' ('Use when procuring energy, optimizing utility tariffs, managing demand charges, evaluating PPAs...'). This matches the anchor-5 pattern of a concrete action list followed by explicit trigger phrases; a 4 would require the 'when' clause to be less explicit, which it is not.

5 / 5

Trigger Term Quality

The 'Use when' clause includes good natural phrases users would actually say: 'procuring energy, optimizing utility tariffs, managing demand charges, evaluating PPAs, or building energy budgets and hedge strategies.' Not a 5 because a few common variations are missing (e.g., 'RECs', 'renewable energy', 'power costs', 'electricity rates'), though the core vocabulary is well covered.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — commercial/industrial energy procurement — with distinct domain-specific triggers (tariffs, demand charges, PPAs, hedge strategies) that would not naturally invoke unrelated skills. The only mild overlap is with general sustainability reporting, which is a minor sub-capability rather than a competing trigger.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

affaan-m/ECC

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.