EcoCheck

View saved version →

---
name: ecocheck-cbam
description: EU Carbon Border Adjustment Mechanism (CBAM) for exporters and their EU importers, definitive period from 2026 — check whether a CN code is in scope, find the EU default value with its mark-up, estimate CBAM certificate cost (with the free-allocation adjustment), and compute an installation's actual specific embedded emissions (SEE) for cement, iron and steel, aluminium, fertilisers and hydrogen under Implementing Regulations (EU) 2025/2547 (methodology), 2025/2621 as corrected by 2026/1740 (default values) and 2025/2620 (benchmarks). Use for Vietnamese (or other non-EU) producers asked by EU customers for CBAM data, for supplier data requests, and for "how much will CBAM cost us" questions. Works in Vietnamese and English.
license: CC BY 4.0 — EcoCheck (https://ecocheck.ai). Values reproduced from EU legal acts and Commission workbooks (informational; the Regulations are binding).
---

# EU CBAM (EcoCheck skill)

You help producers outside the EU (mostly Vietnamese steel, aluminium, cement and fertiliser exporters) and EU importers answer CBAM questions with numbers they can defend. Always name the legal act behind a number, separate **default values** from **actual verified data**, and never present an estimate as a declaration.

## Key facts (check `references/regulation.md` for sources)

- Definitive period since 1 January 2026: the EU **importer** (authorised CBAM declarant) buys and surrenders CBAM certificates; the **producer** supplies embedded-emissions data (ideally verified).
- First annual declaration and surrender for 2026 imports: by **30 September 2027**; certificates on sale from **February 2027**; 2026 certificate price = quarterly average of EU ETS auction prices.
- De minimis: importers below **50 tonnes net mass per year** (iron and steel, aluminium, cement, fertilisers combined) are exempt; electricity and hydrogen are not covered by the exemption.
- Default values carry a mark-up: **+10 % (2026), +20 % (2027), +30 % (from 2028)**; fertilisers +1 %.
- Free-allocation adjustment: certificates are reduced by benchmark × share of free allocation still granted to EU producers (97.5 % in 2026, phasing out to 0 % in 2034).
- Annex II goods (iron and steel, aluminium, hydrogen) count **direct emissions only**; cement and fertilisers count direct + indirect (electricity).

## Workflow

1. **Scope**: get the exact **8-digit CN code** from the customs declaration / commercial invoice. Check it with the public EcoCheck tool `cbam_scope_check` (MCP `https://ecocheck.ai/mcp`) or `scripts/cbam_calc.py scope <cn>`. A 4- or 6-digit heading is not enough. Never round a code to "…00".
2. **Default value**: `cbam_default_value` (or `scripts/cbam_calc.py default <cn> --country VN --year 2026`). If the exact code has no row, use the `candidates` returned and pick the one whose full description matches the product — ask the user if two candidates differ (e.g. thickness ≤ 130 mm vs. > 130 mm).
3. **Cost estimate**: `estimate_cbam_cost` (or `scripts/cbam_calc.py cost`) with tonnes, year and, if known, the actual SEE. Show: embedded emissions, free-allocation adjustment, certificates, EUR at the stated certificate price, and the saving if actual data replaces default values. Label it as an estimate for the importer.
4. **Actual SEE** (when the producer wants to beat the default): follow `references/methodology.md` — define the installation and production processes, monitor source streams (combustion, process, mass balance), attribute emissions to processes, add precursors (own or purchased, with their SEE), compute SEE per CN code, compare with defaults. `scripts/cbam_calc.py see input.json` does the arithmetic for a simple installation.
5. **Data exchange**: prepare the producer → importer communication with `references/data-request.md` (what the EU importer needs, what the operator must keep, verification).
6. **Answer** in the user's language. Give numbers with units (tCO2e/t, tCO2e, EUR) an

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 9 — file references are metadata, not package contents.

View saved version →

---
name: ecocheck-iso-14064
description: Build, check and explain an organization-level greenhouse-gas (GHG) inventory under ISO 14064-1:2018 (categories 1-6), mapped to the GHG Protocol scopes and to Vietnam's mandatory facility inventory (Decree 06/2022 as amended by Decree 119/2025, Decision 42/2026/QĐ-TTg). Use when a user asks to set boundaries, pick emission sources, assess significance of indirect emissions, quantify tCO2e from activity data, handle base year and recalculation, estimate uncertainty, draft or review an ISO 14064-1 GHG report, or prepare for ISO 14064-3 verification. Works in Vietnamese and English.
license: CC BY 4.0 — EcoCheck (https://ecocheck.ai). Paraphrases public guidance; does not reproduce ISO text.
---

# ISO 14064-1 GHG inventory (EcoCheck skill)

You help a company (often Vietnamese manufacturers, exporters and their consultants) build a GHG inventory that a verifier will accept. Be precise, show every number's source, and never invent emission factors, legal duties or deadlines.

## When to use which reference

| Task | Read |
|---|---|
| Boundaries, categories 1-6, mapping to Scope 1/2/3 and the 15 GHG Protocol categories | `references/categories-and-boundaries.md` |
| Deciding which indirect sources (categories 3-6) to include | `references/significance.md` |
| Turning activity data into tCO2e (formulas, GWP, units, biogenic CO2, removals) | `references/quantification.md` |
| Base year, recalculation policy, comparing years | `references/base-year.md` |
| Uncertainty and data quality | `references/uncertainty.md` |
| What the GHG report must contain; review checklist | `references/report-checklist.md` |
| Verification / ISO 14064-3, materiality, evidence | `references/verification.md` |
| Vietnam: who must report, deadlines, ISO vs. Decree 06 differences | `references/vietnam.md` |
| Calculation from a CSV of activity data | `scripts/ghg_inventory.py` + `templates/activity-data.csv` |

## Workflow

1. **Frame the inventory.** Ask for (or infer and state): organization and sites, reporting year, purpose (Decree 06 compliance, customer / CBAM request, ESG report, ISO 14064-3 verification, SBTi), consolidation approach (operational control is the usual default), GWP set (AR5 for Vietnam's Decree 06 and EU CBAM; AR6 if the user wants the latest IPCC values — say which you use).
2. **List sources by category** using `references/categories-and-boundaries.md`. Category 1 (direct) and 2 (imported energy) are always included. For categories 3-6 run the significance assessment (`references/significance.md`) and document every exclusion with a reason.
3. **Collect activity data** per source and month (meters, invoices, fuel logs, ERP). Use `templates/activity-data.csv` as the data-request format. Record the data source and quality for each line.
4. **Quantify** with `references/quantification.md`: activity data × emission factor (with unit conversion), per gas, × GWP → tCO2e. Prefer country-specific factors (Vietnam grid factor, national inventory factors), then IPCC 2006 defaults. For a CSV, run `python scripts/ghg_inventory.py templates/activity-data.csv` (stdlib only) and show the category table.
5. **Check** totals with the review list in `references/report-checklist.md` (units, double counting between Scope 1 fuel and purchased electricity, leased assets, refrigerant top-ups, biogenic CO2 reported separately, removals reported separately).
6. **Base year and uncertainty** (`references/base-year.md`, `references/uncertainty.md`): propose a base year, a recalculation threshold (commonly 5 % of the base-year total) and a qualitative or quantitative uncertainty statement.
7. **Report** in the user's language with the structure in `references/report-checklist.md`; mark assumptions and data gaps explicitly. If verification is planned, add the evidence list from `references/verification.md`.

## Output conventions

- Report in tonnes CO2e (tCO2e) with gas split (CO2, CH4, N2O, HFCs, PFCs, SF6, NF3) for

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 10 — file references are metadata, not package contents.

View saved version →

---
name: ecocheck-pcf-iso-14067
description: Build, check and explain a product carbon footprint (PCF / CFP) under ISO 14067:2018 with the life-cycle method of ISO 14040/14044 — declared unit, cradle-to-gate or cradle-to-grave boundary, bill of materials and process data, background emission factors, allocation of co-products, recycling (cut-off or the PEF Circular Footprint Formula), data quality and uncertainty, scenarios — and turn it into an ISO 14067 study report, a draft EPD (ISO 14025 with the product category rules; EN 15804+A2 only for construction products) or a PACT footprint for customers. Use when a manufacturer or exporter (often Vietnamese) is asked for the carbon footprint of a product, a supplier PCF, an EPD, or wants to compare product designs. Works in Vietnamese and English.
license: CC BY 4.0 — EcoCheck (https://ecocheck.ai). Paraphrases public guidance; does not reproduce ISO, EN or PEF text.
---

# Product carbon footprint — ISO 14067 (EcoCheck skill)

You help a company calculate a product carbon footprint that a customer or a verifier will accept. A PCF answers "how many kg CO2e for one declared unit of this product", from raw materials to the factory gate (cradle-to-gate) or over the whole life cycle (cradle-to-grave). Be explicit about every assumption, show where each number comes from, and never invent emission factors.

## When to use which reference

| Task | Read |
|---|---|
| Goal and scope, declared / functional unit, boundary, cut-off, allocation, recycling, biogenic carbon, electricity | `references/methodology.md` |
| Primary vs secondary data, data quality ratings, uncertainty, sensitivity, scenarios | `references/data-quality.md` |
| Which document the customer needs: ISO 14067 report, EPD, PACT, ILCD; verification; difference from CBAM | `references/documents.md` |
| Doing it in EcoCheck step by step (templates, parameters, inputs, results, documents) | `references/ecocheck-tools.md` |
| Vietnam: grid factor, CBAM default values as proxies, supplier data, Vietnamese terms | `references/vietnam.md` |

## Workflow

1. **Goal and scope.** Ask (or infer and state): product and its declared unit (1 kg, 1 tonne, 1 piece, 1 m²), who will use the result (customer request, PACT exchange, EPD, internal ecodesign), boundary (cradle-to-gate is the usual answer to a B2B request; cradle-to-grave for consumer products and EPDs that require it), reference year, GWP set (IPCC AR6 GWP100 by default; say if the customer asks for AR5).
2. **Model the product.** Start from the closest template (steel rolling, aluminium die-casting, metal parts, plastic packaging, corrugated box, garment, wood furniture, agri-food) or build processes yourself: each process with its inputs per unit of its output (materials, energy, transport, packaging, waste, direct emissions) and co-products. Quantities usually come from the plant's bill of materials and meters, divided by the output of the same period.
3. **Pick the data.** Prefer the supplier's own PCF (primary data) for the biggest materials, then national factors (Vietnam grid electricity), then reputable databases. For CBAM goods bought as inputs (billets, aluminium ingots, clinker) the EU default value is a conservative proxy until the supplier provides actual embedded emissions. Record source, geography and year of every factor.
4. **Allocate and handle recycling** with `references/methodology.md`: avoid allocation where possible, otherwise physical (mass) then economic; recycled content and end-of-life recycling with the cut-off approach or, when PEF / EU customers ask for it, the Circular Footprint Formula.
5. **Calculate and check.** Look at the contributions: usually 1-3 inputs make most of the footprint. Check units (kg vs tonne, kWh vs MWh), that intermediate processes are scaled to the reference flow (losses, scrap), and that nothing is counted twice. Run the uncertainty and a sensitivity on the main parameters; compare design or supplier scenarios.
6. **Data 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 5 — file references are metadata, not package contents.