--- name: pp-nepra description: "Pakistan's electricity regulator publishes the country's only plant-level power data as Excel-exported HTML that reads as empty and PDFs nobody extracts — this turns it into a queryable panel and names every gap. Trigger phrases: `pakistan power plant generation`, `nepra generation data`, `disco t&d losses`, `saifi saidi pakistan`, `pakistan electricity capacity by fuel`, `use nepra`, `run nepra`." author: "qazmataz" license: "Apache-2.0" argument-hint: " [args] | install cli|mcp" allowed-tools: "Read Bash" metadata: openclaw: requires: bins: - nepra-pp-cli install: - kind: go bins: [nepra-pp-cli] module: github.com/mvanhorn/printing-press-library/library/other/nepra/cmd/nepra-pp-cli --- # NEPRA — Printing Press CLI ## Prerequisites: Install the CLI This skill drives the `nepra-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first: 1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows: ```bash npx -y @mvanhorn/printing-press-library install nepra --cli-only ``` 2. Verify: `nepra-pp-cli --version` 3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill. If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.6 or newer). This installs into `$GOPATH/bin` (default `$HOME/go/bin`), so add that directory to `$PATH` instead: ```bash go install github.com/mvanhorn/printing-press-library/library/other/nepra/cmd/nepra-pp-cli@latest ``` If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds. NEPRA is the sole public source for monthly plant-by-plant generation and per-distribution-company reliability in Pakistan, and there is no API, no dataset and no package for any of it. This CLI extracts those releases live from the published documents, keeps unreported months distinct from measured zeros, follows plants across years despite renamed rows and re-sorted row numbers, and surfaces the places the regulator's own documents disagree with themselves instead of quietly picking one. ## When to Use This CLI Reach for this CLI for any question about Pakistani electricity generation at plant granularity, distribution-company reliability against regulatory targets, licensed capacity, or fuel cost adjustment history. It is strongest on questions that need a time series or a cross-entity join that no single published page answers — a plant's seven-year load factor, a listed operator's consolidated fleet, or which distribution company's loss gap widened most. It is also the right tool when you need to know whether a figure is contested, because it records where the regulator's own documents disagree. ## Anti-triggers Do not use this CLI for: - Do not use this to audit or recompute a household or business electricity bill — the governing consumer tariff schedules are published as scanned images with no extractable rates, so any figure would be invented. - Do not use this for net-metering or prosumer payback simulation; that is a modelling product and this CLI carries only published regulator data. - Do not use this for load-shedding schedules or outage timetables; those are distribution-company publications, not regulator data, and are not carried here. - Do not use this for consumer-end applicable tariff rates or fuel adjustment after the published consolidated series ends — the later determinations exist only as image-only or character-corrupted documents and the CLI refuses rather than guessing. - Do not use this for circular debt, national sales or consumer-count aggregates; those live only inside very large State of Industry PDFs, one of which has no text layer at all. ## Unique Capabilities These capabilities aren't available in any other tool for this API. ### The panel nobody else has - **`gen`** — Pull every power plant's monthly generation and utilisation for a fiscal year as rows you can pipe, with unreported months kept distinct from real zeros. _Reach for this when you need the whole fiscal year at plant granularity; it is the only machine-readable form of this table that exists._ ```bash nepra-pp-cli gen --fy 2023-24 --agent ``` - **`fleet`** — Follow one plant or a listed operator's whole fleet across the fiscal years the crosswalk has observed, through renames and re-sorted row numbers. _Use this for any question spanning more than one fiscal year, and for mapping plants to listed operators. meta reports observed_fys against published_fys: the embedded crosswalk does not cover every published year, and the gap is stated rather than hidden._ ```bash nepra-pp-cli fleet --parent HUBC --agent ``` - **`capacity`** — Installed and dependable capacity broken out by plant status and system, so each headline megawatt figure is labelled and derivable. _Use this when a capacity number has to reconcile; it shows which definition produces which total._ ```bash nepra-pp-cli capacity --as-of 2024-06-30 --by status --agent ``` ### Trust the number or don't - **`conflicts`** — List every place NEPRA's own published figures disagree — two sources on one key, an unexplained step inside a single series, or a row that fails its own arithmetic — showing both values and both citations without picking a winner. _Reach for this before quoting any NEPRA figure. `--kind conflict` is the two-source case; `--kind break` is a step inside one series (those entries carry same_key=false, because there is no second source to cite); `--kind arithmetic` is a row that contradicts itself. Default is all three._ ```bash nepra-pp-cli conflicts --surface per --agent ``` - **`disco`** — Per-distribution-company transmission losses, recovery, interruption frequency and duration against the regulator's own targets, across report years. _Use this for any per-DISCO performance question; the national averages everyone quotes hide the spread._ ```bash nepra-pp-cli disco --metric saidi --fy 2024-25 --agent ``` - **`verify`** — Assert every published NEPRA surface against status, byte floor, content checksum, in-document year token and the frozen column fingerprint, exiting non-zero when stale or drifted. _Use this before trusting any extract. It is a FETCH gate, not a cache gate — nothing is stored locally — and it catches the decoys this site serves under an HTTP 200._ ```bash nepra-pp-cli verify --fy 2023-24 --agent ``` ### Find the document - **`events`** — A dated feed of tariff determinations and orders by company, distribution company or docket, with the verbatim document link. _Use this to find which determination applies to a company and when; it returns document identity, not rates._ ```bash nepra-pp-cli events --surface ipp-thermal --docket TRF-71 --agent ``` - **`licence`** — The licence register with gross capacity, plant type, fuel and the modification trail, searchable by name or fuel. _Reach for this for licensed-capacity and plant-type questions. Search by --search or --fuel; lookup by PSX ticker is refused with exit 2 because the crosswalk resolves only 28 of 335 register names, and fleet --parent is the right instrument for an operator's generation panel._ ```bash nepra-pp-cli licence --fuel Coal --agent ``` - **`fca`** — The monthly requested-versus-allowed fuel cost adjustment series with cumulative disallowance, bounded to the window the source actually covers. _Use this to see how much of a requested fuel adjustment the regulator actually allowed, month by month._ ```bash nepra-pp-cli fca --entity cppag --cumulative --agent ``` - **`sources`** — Catalogue every reachable published document with size, coverage window, text-layer flag and reachability state, and diff it against the shipped manifest. _Use this to discover what exists before fetching, and to tell an unreachable document apart from one with no data._ ```bash nepra-pp-cli sources --kind per --agent ``` ## Command Reference **coverage** — The coverage ledger: what this CLI serves, from where, and how old - `nepra-pp-cli coverage` — The coverage ledger: all 104 surfaces this CLI can serve, joined from its four in-code catalogues, with the command that answers for each and the age of every measurement. MAKES NO REQUEST. `--provenance` declares what a fetch of each surface records and what it deliberately does not; `--check-stale` exits 6 when ANY surface is past the window, which is what makes it usable as a cron gate. **events** — Tariff determinations and Authority orders - `nepra-pp-cli events` — The determinations feed. REQUIRES gzip: without Accept-Encoding this page silently truncates under a 30 s timeout and returns a partial list under an HTTP 200. **fca** — Fuel cost adjustment: monthly requested versus allowed, CPPA-G and K-Electric - `nepra-pp-cli fca` — The consolidated FCA table. Coverage is hard-bounded Jul-2018 to Jun-2022; negatives are written in accounting parentheses. **generation** — Plant-level installed and dependable capacity with monthly generation and utilisation, per fiscal year - `nepra-pp-cli generation index` — The site's own generation index. INCOMPLETE — links 5 of the 7 reachable years; never use as the sole enumerator. - `nepra-pp-cli generation year` — Fetch one fiscal year's generation workbook payload. windows-1252 encoded; the HTTP header declares no charset. - `nepra-pp-cli generation plants` — One row per plant for a fiscal year: installed and dependable capacity, technology, fuel and status, filterable with `--technology` and `--fuel`. Capacity is INDEPENDENT of the monthly block in both directions, and the `*_state` columns carry that: a delicensed plant keeps its published capacity, while eleven FY2017-18 plants publish no capacity number at all. NO capacity factor or utilisation is emitted at this or any grain — the source publishes no hours-per-month denominator. - `nepra-pp-cli generation monthly` — Twelve rows per plant for a fiscal year, the monthly GWh and `% age` cells, same `--technology` / `--fuel` filters. Unfiltered it emits exactly what `gen --fy ` emits, from the same builder. A blank NEVER becomes a zero. **hydel** — Hydel generation and dependable capacity - `nepra-pp-cli hydel` — Hydel data. Dependable capacities are pinned upstream to 'July 2018 - June 2022'. **licence** — Generation licence register: gross capacity, licence number, plant type, fuel, modification trail - `nepra-pp-cli licence` — The licence register accordion. Key lookup must be typo-aliased: the page misspells its own column as 'Gross Capacityy', hiding the largest entry. **quarterly** — Quarterly data for ex-WAPDA DISCOs and K-Electric - `nepra-pp-cli quarterly` — Quarterly index. FROZEN upstream at 'April 2022- June 2022 (4th Quarter)' with 'Not Yet Issued' against every DISCO; nothing on the page says it is stale. **reliability** — DISCO Performance Evaluation Reports: T&D losses against allowed target, recovery, SAIFI, SAIDI, complaints, safety - `nepra-pp-cli reliability ` — Fetch one Performance Evaluation Report PDF. Filenames are unconstructible across years — always scrape from sources, never build the path. **sir** — State of Industry Report PDFs - `nepra-pp-cli sir ` — One State of Industry Report, returned as PDF bytes. Very large: 2025 is ~316 MB. **sro** — SRO notifications - `nepra-pp-cli sro` — SRO notification index. **tariff** — Per-distribution-company notified tariff pages - `nepra-pp-cli tariff ` — One DISCO's tariff page. UTF-8 on this surface, unlike the generation workbooks. Rate schedules themselves are image-only PDFs and are NOT extractable. ### Finding the right command When you know what you want to do but not which command does it, ask the CLI directly: ```bash nepra-pp-cli which "" ``` `which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query. `--json` (and other machine formats) keep that exit-2 contract and write `{"matches":[]}` on stdout so agents can inspect the envelope without treating a miss as success. ## Recipes ### One operator's fleet across every published year ```bash nepra-pp-cli fleet --parent HUBC --agent ``` Follows a listed operator's plants through renames and re-sorted rows, narrowing the payload to the four fields an availability model needs. ### Which distribution company misses its loss target by most ```bash nepra-pp-cli disco --metric tnd --fy 2024-25 --agent ``` Returns actual reported losses alongside the level allowed in tariff and the breach, per company, which no published page tabulates together. ### Check a figure is not contested before quoting it ```bash nepra-pp-cli conflicts --surface per --agent ``` Lists same-key disagreements between two published documents with both citations, so a quoted number can be defended or avoided. ### See which fiscal years and surfaces actually exist upstream ```bash nepra-pp-cli sources --diff --agent ``` Diffs the live catalogue against the shipped manifest, separating genuinely unreachable documents from ones with no data. ### Gate a published surface on bytes, decoys and the column fingerprint ```bash nepra-pp-cli verify --fy 2023-24 --check-stale --agent ``` Emits a citable checksum manifest and exits non-zero if any artifact drifted or aged past its staleness window. ## Auth Setup No authentication required. Run `nepra-pp-cli doctor` to verify setup. ## Agent Mode Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color`. Global format flags share one contract on promoted, novel, sync, and `--deliver` paths: - `--json` — one JSON document on stdout (assertions, summaries and warnings go to stderr) - `--compact` — keep identity/status/timestamp fields; does not change the document vs stream shape - `--csv` / `--plain` — tabular rows (collection envelopes unwrap to the row array) - `--quiet` — one identity value per row, no envelope - **Pipeable** — JSON on stdout, errors on stderr - **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs: ```bash nepra-pp-cli events --agent ``` - **Previewable** — `--dry-run` shows the request without sending - **Live-only** — every data command reads the published documents on each invocation, or computes from an embedded catalogue. There is no sync command and no local NEPRA store; `--data-source local` is refused rather than answered emptily - **Non-interactive** — never prompts, every input is a flag - **Read-only** — do not use this CLI for create, update, delete, publish, comment, upvote, invite, order, send, or other mutating requests ### Response envelope Commands that read from the local store or the API wrap output in a provenance envelope: ```json { "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."}, "results": } ``` Parse `.results` for data and `.meta.source` to know where it came from. `meta.source` is NOT just live-or-local on this CLI — there is no local NEPRA store — and it takes four values: | `meta.source` | Meaning | Commands | |---|---|---| | `live` | read from nepra.org.pk on this invocation | gen, generation plants/monthly, capacity, disco, events, licence, fca, verify, the promoted resources | | `computed` | derived from an embedded crosswalk, no request | fleet | | `ledger` | a shipped in-code registry, no request | conflicts without `--recompute` | | `catalogue` | an in-code catalogue, no request | coverage, and the no-selector branch of gen/sources/events/licence | TWO COMMANDS DO NOT USE THE TWO-KEY ENVELOPE, so an agent reading only `.results` loses data: - `disco` emits a THIRD top-level key, `weighted_average`, carrying NEPRA's own published W.Av row as a separate series. It is deliberately not mixed into `.results`, because a published average is not another entity. - `verify --manifest` emits no `meta`/`results` pair at all: it prints the frozen expectation manifest as its own document (`manifest_as_of`, `column_fingerprint`, `logical_columns`, `surfaces`) and makes no request. A human-readable `N results (live)` summary is printed to stderr only when stdout is a terminal AND no machine-format flag (`--json`, `--csv`, `--compact`, `--quiet`, `--plain`, `--select`) is set — piped/agent consumers and explicit-format runs get pure JSON on stdout. ## Paths and state Agents should treat the CLI's path resolver as part of the runtime contract: - Use `--home ` for one invocation, or set `NEPRA_HOME=` to relocate all four path kinds under one root. - Use per-kind env vars only when a specific kind must diverge: `NEPRA_CONFIG_DIR`, `NEPRA_DATA_DIR`, `NEPRA_STATE_DIR`, `NEPRA_CACHE_DIR`. - Resolution order is per-kind env var, `--home`, `NEPRA_HOME`, XDG (`XDG_CONFIG_HOME`, `XDG_DATA_HOME`, `XDG_STATE_HOME`, `XDG_CACHE_HOME`), then platform defaults. - `config` contains settings like `config.toml` and profiles. `data` contains `data.db`, which holds only the Printing Press learn and playbook tables — there is no NEPRA data in it. `state` contains persisted queries, jobs, and `teach.log`. `cache` contains regenerable HTTP/cache files. THIS CLI STORES NO CREDENTIAL OF ANY KIND: there is no `credentials.toml`, no cookie jar and no auth sidecar, because NEPRA needs none. - Run `nepra-pp-cli doctor --fail-on warn` to surface path warnings. `agent-context` exposes a schema v4 `paths` block for agents that need the resolved dirs. - For MCP, pass relocation through the MCP host config. The MCP binary does not inherit CLI flags: ```json { "mcpServers": { "nepra": { "command": "nepra-pp-mcp", "env": { "NEPRA_HOME": "/srv/nepra" } } } } ``` Fleet precedence: an inherited per-kind env var overrides an explicit `--home` for that kind. Use `NEPRA_HOME` or per-kind vars as durable fleet levers, and use `--home` only for a single invocation. Relocation is not reversible by unsetting env vars; move files manually before clearing `NEPRA_HOME`, or `doctor` will not find the learn/playbook database left under the former root. ## Automatic learning This CLI ships a self-capturing learning loop. The CLI does its own bookkeeping: every invocation is journaled locally, a failed flag followed by a corrected retry auto-derives a `flag_alias` candidate, and a `teach` on a query family without a playbook auto-synthesizes a `playbook_candidate` from the session's journal. Your job is judgment only: `recall` first, act on surfaced candidates, `teach` the final answer, `playbook amend` when you observe a correction. You never record failures by hand. ### Step 1: `recall` before any discovery Before list/search/drill commands on a new user question, run: ```bash nepra-pp-cli recall "" --agent ``` The response envelope: ```json { "query": "...", "normalized": "", "query_entities": ["..."], "found": true | false, "match_score": 0.0, "results": [ { "res