lean-deck-builder

name

lean-deck-builder

description

Turn sustainability audit findings into a polished stakeholder presentation (.pptx). Use this skill whenever the user wants a deck, slides, or presentation from any Lean Agentic AI Skills audit (web-carbon-audit, cloud-waste-audit, green-code-review, etc.), asks to "present the findings", needs a leadership/board/client-facing summary of a green or efficiency audit, or a lean-router pipeline ends in a presentation. Consumes one or more lean-findings.json files — never audits anything itself.

Green Deck Builder

Consumes one or more lean-findings.json files (schema copy in references/lean-findings.schema.json) and produces a stakeholder-ready .pptx. This skill is a pure consumer: it never generates findings, and if handed a subject instead of findings, it asks the router/audit skill to run first.

Prerequisite (platform-aware): if your environment provides a document-creation skill for presentations (e.g. Claude's pptx skill at /mnt/skills/public/pptx/SKILL.md), read and follow it before generating the file. On other agent platforms (Codex, Copilot, Antigravity, Cursor, etc.), use the platform's available tooling for .pptx generation (python-pptx or equivalent). Either way, this skill's content structure and sustainability rules apply on top.

Inputs

1. One or more findings files (paths from the user or the router). Validate the essentials: findings[] entries with severity, sci_term, issue, fix. If multiple files, they arrive pre-merged from the router or merge them mechanically (concatenate findings, union passed/out_of_scope, keep every methodology).
2. Audience, if stated (leadership / engineering / client). Default: mixed leadership. Audience changes emphasis, not honesty.

Deck structure

Use this skeleton; drop sections that would be empty rather than padding them:

1. Title — subject + date + "Sustainability findings" framing.
2. Executive summary — one slide: findings count by severity, the single biggest lever, one sentence on what is already healthy (from passed). No jargon; "SCI" gets a footnote, not a headline.
3. What we checked & how — the methodology paragraph(s), lightly edited, plus scope_notes. This slide is mandatory. A findings deck without methodology is a greenwashing deck.
4. Quick wins — findings where effort = low and severity ≥ medium. These make the deck actionable in week one.
5. Findings by severity — high first. One slide per high finding (issue → evidence → fix); group mediums 2–3 per slide; lows as a single summary list.
6. Effort vs impact — a simple 2×2 placing findings by effort (x) against severity (y). This is usually the slide leadership screenshots.
7. What's already good — the passed list. Genuine credit builds trust in the criticism.
8. Out of scope / next steps — out_of_scope items reframed as the follow-up plan (e.g. "server region assessment needs infra input → schedule with ops").

Content rules

• Numbers discipline is absolute. Only figures present in evidence may appear on slides. Never add percentages, CO₂ grams, or cost savings the findings don't contain. If a slide feels weak without a number, the honest fix is the phrase "directional estimate — measurement recommended", not a made-up figure.
• Every finding slide carries its pattern.url as a small source citation when present.
• Translate SCI terms for lay audiences: E → "energy/compute", M → "hardware footprint", I → "grid carbon", R → "efficiency per user/request".
• Keep per-slide text lean; the findings file remains the detailed record and the deck should say so on the final slide.

Design rules (practice what the deck preaches)

• Light backgrounds, restrained accent palette, no full-bleed photographic backgrounds — the deck should be cheap to project, share, and print (ink-light).
• No decorative stock imagery; simple shapes and native charts only. Embedded images bloat the file every time it is emailed.
• System-safe or single embedded font; no autoplaying media.
• Target a compact file. If the .pptx exceeds a few MB with no images, something is wrong — investigate before delivering.

Delivery

Save the deck to the outputs directory and present it with a 2–3 sentence summary: slide count, the headline finding, and a pointer to the methodology slide. Offer (do not auto-run) a matching written report via lean-report-writer if the suite has it installed.

Cost signal rendering

Cost & carbon column. Where findings carry a cost_signal, include one small column or row per finding naming the driver and observed value (e.g. "370 tokens/call"). Never render a currency amount unless the findings file supplies one. Slides must respect the split: energy and carbon impact directional, cost driver counted.