CtrlK
BlogDocsLog inGet started
Tessl Logo

tdg-personal/energy-procurement

>

68

Quality

68%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines a specific domain (commercial/industrial energy procurement and management), lists numerous concrete capabilities, and includes an explicit 'Use when...' clause with relevant trigger terms. The description is comprehensive without being padded, uses proper third-person voice, and occupies a distinct niche that would be easily distinguishable from other skills. The mention of '15+ years experience' is slightly fluffy credential-signaling but doesn't significantly detract from the overall quality.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: electricity and gas procurement, tariff optimization, demand charge management, renewable PPA evaluation, multi-facility energy cost management, market structure analysis, hedging strategies, load profiling, and sustainability reporting frameworks.

3 / 3

Completeness

Clearly answers both 'what' (procurement, tariff optimization, demand charge management, PPA evaluation, etc.) and 'when' with an explicit 'Use when...' clause listing specific trigger scenarios like procuring energy, optimizing tariffs, managing demand charges, evaluating PPAs, or developing energy strategies.

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'energy procurement', 'tariff optimization', 'demand charges', 'PPA', 'hedging strategies', 'load profiling', 'sustainability reporting', 'electricity', 'gas'. These cover a wide range of terms an energy manager would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused on commercial/industrial energy procurement and management. The specific domain terms like 'tariff optimization', 'demand charge management', 'renewable PPA evaluation', and 'hedging strategies' make it very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Implementation

27%

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

This skill reads more like a comprehensive energy procurement textbook than an actionable skill file for Claude. While the domain expertise is genuine and the content is accurate with useful numerical benchmarks, it is far too verbose, explains many concepts Claude would already know, and lacks executable artifacts (templates, calculation code, query examples). The monolithic structure with no progressive disclosure means the entire ~4000+ word document loads into context every time, wasting tokens on background knowledge.

Suggestions

Reduce the content by 60-70% by removing explanatory background (e.g., what LMP is, how deregulated markets work, what RECs are) and keeping only the decision-relevant thresholds, edge cases, and numerical benchmarks that Claude wouldn't already know.

Split into multiple files: a lean SKILL.md overview with decision frameworks, plus separate reference files for market structures (MARKETS.md), PPA evaluation (PPA_EVALUATION.md), demand charge management (DEMAND_CHARGES.md), and RFP templates (RFP_TEMPLATE.md), with clear one-level-deep links.

Add executable artifacts: a Python/spreadsheet calculation template for PPA NPV analysis, a structured RFP template in markdown, and a demand charge analysis script that processes 15-minute interval data.

Add explicit validation checkpoints to the procurement workflow, such as 'Verify load data completeness before issuing RFP' and 'Confirm hedge position against policy limits before executing contracts.'

DimensionReasoningScore

Conciseness

This skill is extremely verbose at ~4000+ words, explaining many concepts Claude already knows (what LMP is, what RECs are, how load factors work, basic market structures). Extensive background explanations like 'PDF files are a common file format' equivalents for energy concepts consume tokens without adding actionable value. Much of this reads like a textbook rather than a skill instruction.

1 / 3

Actionability

The skill provides concrete numerical examples, specific market references, and decision frameworks with clear criteria, which is good. However, there are no executable code snippets, no specific tool commands, no API calls, and no copy-paste-ready templates (e.g., RFP templates, calculation spreadsheet formulas, or data query examples). The guidance is detailed but remains descriptive rather than directly executable.

2 / 3

Workflow Clarity

The 6-step procurement lifecycle and decision frameworks provide reasonable sequencing. The escalation protocols table is well-structured with clear triggers and timelines. However, validation checkpoints are largely missing — there are no explicit 'verify this before proceeding' steps in the procurement workflow, no feedback loops for error recovery, and the main workflow lacks the rigor needed for high-stakes financial decisions.

2 / 3

Progressive Disclosure

The entire skill is a monolithic wall of text with no references to external files. Content that should be split into separate documents (e.g., market structures reference, tariff analysis guide, PPA evaluation checklist, RFP templates) is all inline. The 'Additional Resources' section at the end vaguely mentions maintaining documents but doesn't link to any. There's no layered structure for discovery.

1 / 3

Total

6

/

12

Passed

Validation

72%

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

Validation8 / 11 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

8

/

11

Passed

Reviewed

Table of Contents