Skip to content

Agent Skills

eptr2 includes Claude Agent Skills that provide specialized guidance for different types of electricity market data queries.

What are Agent Skills?

Agent Skills are structured knowledge files that help Claude understand domain-specific concepts and provide better assistance. When you ask about electricity prices, consumption, or generation, Claude automatically loads the relevant skill.

Available Skills

Skill Triggers On Use Case
eptr2-price-analysis PTF, SMF, MCP, SMP, electricity prices Price queries and analysis
eptr2-consumption-data UECM, load plan, demand forecast Consumption tracking
eptr2-generation-tracking UEVM, generation, renewables Generation monitoring
eptr2-imbalance-costs KUPST, imbalance, deviation costs Imbalance calculations
eptr2-market-operations GÖP, GİP, DGP, market orders Market operations data
eptr2-api-discovery Available endpoints, API search Finding the right API

How Skills Work

Skills are automatically invoked based on your query:

Your Question Skill Triggered
"What are today's electricity prices?" eptr2-price-analysis
"Show me wind generation data" eptr2-generation-tracking
"Calculate imbalance costs for my portfolio" eptr2-imbalance-costs
"What APIs are available for market data?" eptr2-api-discovery

Skill Details

eptr2-price-analysis

Covers: - Market Clearing Price (MCP/PTF) - System Marginal Price (SMP/SMF) - Weighted Average Price (WAP/AOF) - Intraday market prices - Price comparisons and spreads

Example queries: - "What was the average MCP for July 2024?" - "Compare PTF and SMF for the last week" - "Show hourly price distribution"

eptr2-consumption-data

Covers: - Real-time consumption - Settlement consumption (UECM) - Load plan forecasts - Consumption patterns

Example queries: - "What's the current electricity consumption?" - "Compare forecast vs actual consumption" - "Show consumption trends by hour"

eptr2-generation-tracking

Covers: - Real-time generation by source - Settlement generation (UEVM) - Renewable energy output - Plant-level production

Example queries: - "How much solar generation right now?" - "Show wind generation for the past month" - "What's the generation mix?"

eptr2-imbalance-costs

Covers: - Imbalance price calculations - KUPST (deviation costs) - Energy surplus/deficit penalties - DSG tolerance calculations

Example queries: - "Calculate imbalance cost for 100 MWh deficit" - "What's the KUPST for yesterday?" - "Explain imbalance pricing mechanism"

eptr2-market-operations

Covers: - Day-Ahead Market (GÖP) operations - Intraday Market (GİP) trading - Balancing Power Market (DGP) - Order books and volumes

Example queries: - "Show GÖP clearing quantities" - "What's the GİP trading volume today?" - "Explain YAL and YAT instructions"

eptr2-api-discovery

Covers: - Finding available endpoints - Understanding API categories - Parameter requirements - Call aliases

Example queries: - "What APIs are available for price data?" - "How do I get power plant information?" - "List all consumption-related endpoints"

Installing Skills Personally

To use skills across all your projects, copy to your personal skills directory:

cp -r .claude/skills/* ~/.claude/skills/

xcopy /E /I .claude\skills %USERPROFILE%\.claude\skills

Skill Files Location

In the eptr2 repository, skills are located at:

.claude/skills/
├── eptr2-price-analysis/
│   └── SKILL.md
├── eptr2-consumption-data/
│   └── SKILL.md
├── eptr2-generation-tracking/
│   └── SKILL.md
├── eptr2-imbalance-costs/
│   └── SKILL.md
├── eptr2-market-operations/
│   └── SKILL.md
└── eptr2-api-discovery/
    └── SKILL.md

Creating Custom Skills

You can create custom skills for your specific use cases:

  1. Create a directory under .claude/skills/
  2. Add a SKILL.md file with:
  3. Skill description
  4. Trigger keywords
  5. Domain knowledge
  6. Example patterns

Example structure:

# My Custom Skill

## Description
This skill helps with [specific use case].

## Triggers
- keyword1
- keyword2

## Knowledge
[Domain-specific information]

## Examples
- "Example query 1" → [Expected behavior]
- "Example query 2" → [Expected behavior]

Best Practices

  1. Be specific - Detailed queries trigger more accurate skill matching
  2. Use Turkish terms - Skills recognize both English and Turkish terminology
  3. Combine skills - Complex queries may utilize multiple skills
  4. Iterate - Follow up with clarifying questions for best results

Next Steps