epd-compare
Compare EPD products on normalized GWP and other impacts while checking declared units, system boundaries, and LEED eligibility. Use for side-by-side EPD comparison.
AlpacaLabsLLC · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add AlpacaLabsLLC/skills-for-architects --skill epd-compare技能说明
name: epd-compare description: Compare EPD products on normalized GWP and other impacts while checking declared units, system boundaries, and LEED eligibility. Use for side-by-side EPD comparison. allowed-tools:
- Read
- Write
- Edit
- Bash
- Glob
- Grep
- AskUserQuestion
/as:epd-compare — EPD Comparator
Harness note: use
/as:<skill>on Claude Code and$<skill>on Codex. Resolve<skill-root>as the directory containing this loadedSKILL.mdand<plugin-root>as the plugin root that containsskills/, and use equivalent native tools when host tool names differ.
Compare 2 or more products side-by-side on environmental impact metrics. Validates comparability (declared units, system boundaries, PCR alignment), generates comparison tables with percentage deltas, and checks LEED v4.1 MRc2 eligibility.
This skill reads EPD records but does not persist or modify them. Fields follow schema/epd-schema.md, which is distinct from the FF&E product schema. Output is a markdown comparison report.
Input
The user provides EPD data in one of these ways:
- Inline data — pasted product names with GWP values
- File path — a canonical
epd-library.csvor markdown file with EPD data - From prior skills — "compare the EPDs I just parsed/found" (uses structured data from the current conversation)
- Mixed — combine pasted, prior, and canonical local CSV records
If the user doesn't specify a source, first use structured EPD data from the current conversation. Otherwise ask for pasted values or an EPD CSV path. When reading epd-library.csv, validate it with python3 "<plugin-root>/skills/master-schedule/scripts/csv-library.py" validate epd; reject FF&E-shaped or malformed files. Validation is read-only; never invoke init, import, append, or update.
Workflow
Step 1: Collect data
Gather EPD data from the specified source. For each product, you need at minimum:
- Product name and manufacturer
- GWP (A1-A3) value
- Declared unit
Additional fields improve the comparison: ODP, AP, EP, POCP, energy use, water use, system boundary, PCR, validity dates, LEED eligibility.
Step 2: Validate comparability
Before comparing, run these checks and report findings:
Declared unit alignment:
- Are all products using the same declared unit (e.g., all per m3, all per kg)?
- If units differ, attempt normalization where possible:
- kg ↔ ton (multiply/divide by 1000)
- m2 at different thicknesses (if thickness is known, normalize to same thickness)
- If normalization is impossible, warn: "Product A reports per m2, Product B reports per kg. Direct comparison requires density or thickness data. Provide conversion factors, or I'll compare only within matching units."
- Never silently compare products with different declared units.
System boundary alignment:
- Flag if some are cradle-to-gate (A1-A3) and others cradle-to-grave (A1-A3 + C1-C4 + D).
- Note: "A1-A3 comparison is still valid across both types. Full life cycle comparison is only valid for cradle-to-grave EPDs."
PCR alignment:
- Flag if products use different PCRs. Products under the same PCR are most directly comparable.
- Note the PCR names if they differ.
EN 15804 version:
- Flag if some use +A1 and others +A2. Impact indicator units may differ (AP in kg SO2e vs. mol H+ eq).
- GWP in kg CO2e is comparable across versions.
Validity:
- Flag any expired EPDs with their expiration date.
EPD type:
- Flag mix of product-specific and industry-average EPDs. Note that industry-average EPDs are less precise.
Report all findings before proceeding:
## Comparability Check
✓ Declared unit: All products use 1 m3
✓ System boundary: All cradle-to-gate (A1-A3)
⚠ PCR: Products 1-2 use NRMCA PCR, Product 3 uses NSF PCR — results are comparable but not identical methodology
⚠ Validity: Product 2 expired 2025-12-01
✓ EPD type: All product-specific
Step 3: Generate comparison
Produce three outputs:
a. Side-by-side impact table
## Environmental Impact Comparison
| Metric | ECOPact (Holcim) | ProPaving (CEMEX) | ReadyMix (Buzzi) | Unit |
|--------|-----------------|-------------------|------------------|------|
| **GWP-total (A1-A3)** | **242** | 298 | 385 | kg CO2e/m3 |
| GWP-fossil (A1-A3) | 238 | 291 | — | kg CO2e/m3 |
| GWP-biogenic (A1-A3) | 4 | 7 | — | kg CO2e/m3 |
| ODP (A1-A3) | 1.2e-6 | 1.5e-6 | 1.8e-6 | kg CFC-11e/m3 |
| AP (A1-A3) | 0.45 | 0.52 | 0.61 | kg SO2e/m3 |
| EP (A1-A3) | 0.08 | 0.11 | 0.14 | kg PO4e/m3 |
| PERE (A1-A3) | 180 | 95 | 72 | MJ/m3 |
| PENRE (A1-A3) | 1,450 | 1,890 | 2,340 | MJ/m3 |
| FW (A1-A3) | 0.32 | 0.41 | 0.55 | m3/m3 |
| Recycled Content | 35% | 22% | 12% | % |
Bold the best value in each row (lowest for impacts, highest for recycled content/renewable energy).
Use — for missing data. Never fill in missing values.
b. Percentage comparison (relative to lowest)
## GWP Comparison (relative to lowest)
| Product | GWP (A1-A3) | vs. Lowest | vs. Industry Avg |
|---------|-------------|------------|-------------------|
| ECOPact (Holcim) | 242 kg CO2e/m3 | — baseline — | -40% |
| ProPaving (CEMEX) | 298 kg CO2e/m3 | +23% | -26% |
| ReadyMix (Buzzi) | 385 kg CO2e/m3 | +59% | -4% |
| *Industry average (NRMCA Industry-Wide Member EPD v3.2, 2022)* | *~400 kg CO2e/m3* | — | — |
Include an industry average baseline only if it is citable — either the user provides one (e.g., an industry-average EPD or a published baseline document) or you can attach a named source and publication year, per the GWP Baseline Policy below. Label the baseline row with its source and year.
If no citable baseline is at hand, ask: **"Do you have an industry-average EPD or published baseline for this material category? If so, share it and I'll include it in the comparison. We're working on EC3 API integration that will automate ba
阅读完整来源 ↗