worldenergydata-source-readiness
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
Best use case
worldenergydata-source-readiness is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
Teams using worldenergydata-source-readiness should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/worldenergydata-source-readiness/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How worldenergydata-source-readiness Compares
| Feature / Agent | worldenergydata-source-readiness | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Route agents to the canonical worldenergydata source-readiness skill and summary script. Use when asked for worldenergydata data completeness, data locations, latest known data dates, scheduler freshness, source-readiness status, or acceptance-criteria inputs across the repo ecosystem.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# WorldEnergyData Source Readiness
## Quick Start
Use the canonical skill and script in the `worldenergydata` checkout:
```bash
WED_REPO="${WED_REPO:-../worldenergydata}"
cd "$WED_REPO"
git fetch origin main
python .claude/skills/worldenergydata-source-readiness/scripts/source_readiness_summary.py
```
JSON output:
```bash
WED_REPO="${WED_REPO:-../worldenergydata}"
cd "$WED_REPO"
git fetch origin main
python .claude/skills/worldenergydata-source-readiness/scripts/source_readiness_summary.py --format json
```
If the script is missing, update the `worldenergydata` checkout to a revision at or after PR #461.
## What This Returns
The summary includes:
- data group / module
- catalog status and freshness status
- latest known date and whether it came from metadata, file timestamps, or scheduler success
- repo-local data location
- external data root, if metadata records one
- configured scheduler output directory
- dataset count, record count, file count, and size
## Interpretation Rule
Do not treat `latest_known_date` as source-data vintage unless the row says the basis is an inspected dataset field. Most current rows use metadata refresh, newest file modified date, or scheduler success.
For acceptance criteria, require each Tier-A source to expose:
- `source_data_latest_date`
- `last_successful_refresh`
- `data_location`
- `record_count`
- `freshness_status`
- `refresh_cadence`
- `blocker_issue` or `none`
## Canonical Files
In `worldenergydata`:
- `.claude/skills/worldenergydata-source-readiness/SKILL.md`
- `.claude/skills/worldenergydata-source-readiness/scripts/source_readiness_summary.py`
- `data/freshness-scorecard.json`
- `data/modules/<module>/_metadata.json`
- `data/modules/<module>/manifest.json`
- `config/scheduler/scheduler_config.yml`Related Skills
llm-wiki-source-extraction-coverage
Doc-type-aware extraction contract for llm-wiki source ingestion with measurable coverage and source-anchored traceability. Use when (1) ingesting a PDF, DOCX, XLSX, PPTX, HTML, or scanned-image source into a wiki `sources/` page, (2) computing the pre-extraction estimate (what fraction of the source we expect to recover) and post-extraction yield (what fraction we actually recovered), (3) anchoring wiki claims back to specific page / paragraph / cell / slide positions in the source so a reviewer can re-verify or revise against the actual document, (4) deciding whether OCR fallback or manual transcription is needed. Codifies workspace-hub's existing OCR fallback chain and python-docx / openpyxl / trafilatura patterns into a format-specific routing table. Companion to research/llm-wiki-page-shape-contract (Rule 7 input-layer pages) and research/llm-wiki — this skill is the defense against silent extraction failure.
orcawave-orcaflex-readiness-audit
Audit the real readiness of digitalmodel OrcaWave/OrcaFlex spec-driven workflows by reconciling workspace-hub issues, source/tests, semantic-equivalence boundaries, and wiki synthesis gaps.
multi-source-tax-document-reconciliation
Verify generated tax forms against source documents by line-by-line comparison, not just totals
gtm-site-readiness-audit-local-vs-production
Audit GTM feature work by separating local artifact readiness from production deployment state, then fix common blockers in aceengineer-website and GTM collateral.
source-command-learn-extended
Extract learnings from the current session and convert them to actionable repo content. Phase 4 of #1760.
source-command-gsd-workstreams
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
source-command-gsd-review-backlog
Review and promote backlog items to active milestone
source-command-gsd-join-discord
Join the GSD Discord community
source-command-gsd-from-gsd2
Import a GSD-2 (.gsd/) project back to GSD v1 (.planning/) format
source-command-compound-extended
Run cross-agent memory bridge. Sync learnings between machine agents, update shared knowledge. Phase 5 of #1760.
multi-machine-ai-readiness-and-issue-triage
Assess a multi-machine, multi-repo AI-enabled workspace for readiness, provider allocation, and issue prioritization.
knowledge-source-recon
Reconnaissance pattern to inventory all knowledge sources across the workspace-hub ecosystem's existing intelligence infrastructure. Maps raw sources for LLM Wiki ingestion planning. Leverages pre-built registries and indexes rather than re-scanning directories.