lean-report-writer

星标4

分支0

更新时间2026年7月18日 15:25

Turn sustainability audit findings into a polished written report (Word/PDF/markdown) — executive narrative, findings detail, remediation roadmap, with optional ESG/CSRD-flavored framing on request. Use this skill whenever the user wants a written sustainability/efficiency report, documentation of audit results, content for an ESG or engineering report, or a lean-router pipeline ends in a document. Consumes one or more lean-findings.json files from any Lean Agentic AI Skills audit; never audits anything itself.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

来源

navveenb

navveenb/lean-agentic-ai-skills

打开 GitHub 仓库查看创作者相关仓库

下载

Green Report Writer

Pure consumer skill. Input: one or more lean-findings.json files (merge mechanically if multiple: concatenate findings, union passed/out_of_scope, keep all methodology paragraphs). Output: a report document.

Prerequisite (platform-aware): default to markdown unless the user asks for a formal document. For .docx/.pdf output, use your environment's document skills where present (e.g. Claude's docx/pdf skills under /mnt/skills/public/); on other agent platforms use available document tooling (python-docx, reportlab, or equivalent).

Report structure

Write in prose — findings data becomes narrative, not pasted JSON:

Executive summary — scope in one sentence, findings counts by severity, the single biggest lever, one honest sentence on what's already healthy.
Scope & methodology — mandatory, verbatim-faithful to every methodology paragraph and scope_notes. A report without its methodology is greenwashing; this section cannot be cut even if the user asks for "just the findings" (offer a short version that still carries a one-line methodology note).
Findings — high severity as full subsections (issue → evidence → impact → remediation, with pattern citations as links); medium grouped by theme; low as a summary paragraph. Translate SCI terms inline for lay readers.
Remediation roadmap — sequence by effort-vs-severity: quick wins (low effort, ≥medium severity) first with a "week one" framing, then structural items.
What's already working — the passed list as prose; genuine credit, not filler.
Limitations & next steps — out_of_scope items reframed as the follow-up plan, plus pointers to real measurement tooling (CodeCarbon, Cloud Carbon Footprint, Kepler, Impact Framework) for anything the audit could only assess directionally.

ESG/CSRD framing (only when requested)

Findings can inform ESRS E1-style narrative (actions taken, planned resource allocation) but this skill does NOT produce compliance-grade disclosures: no emissions inventories, no Scope 1/2/3 figures, no assurance-ready claims. State this limit in the document itself and recommend the user's sustainability/audit function own final disclosure text.

Numbers discipline

Only figures present in evidence appear in the report. No derived percentages, no CO2 grams, no cost extrapolations beyond what a findings file contains. Where a section feels thin without numbers, the honest sentence is "directional finding — measurement recommended (see Limitations)".

Cost signal rendering

Cost signal integration. Where findings carry cost_signal, weave the counted driver into each finding's paragraph (e.g. "...the driver here is bytes egress per visit, currently ~4.2 GB per page load..."). Never estimate spend without a supplied billing rate. Reports MUST preserve the three-axis honesty split: energy and carbon directional, cost driver counted.

同仓库更多 Skills

同仓库

agentic-loop-auditor

navveenb/lean-agentic-ai-skills

Audit agent frameworks and agentic workflows for token-burning loop pathologies — unbounded retries, excessive planning depth, tool-call thrashing, context snowballing, missing loop budgets and kill switches. Use this skill whenever the user shares agent configs or traces (LangChain/LangGraph, CrewAI, AutoGen, custom loops), complains an agent is slow or expensive, or is designing any autonomous/multi-step agent. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

ai-eval-efficiency-audit

navveenb/lean-agentic-ai-skills

Audit AI evaluation infrastructure for wasted compute — full benchmark suites re-run on unchanged cases, LLM-as-judge grading without caching, oversized judge models, redundant eval passes per commit, and missing result reuse. Use this skill whenever the user shares eval harness configs or CI eval steps, complains that evals are slow or expensive, mentions LLM-as-judge costs, or runs benchmark suites on every change. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

api-efficiency-audit

navveenb/lean-agentic-ai-skills

Audit API design for chattiness and over-fetching — REST endpoints requiring N calls per screen, GraphQL resolvers with N+1 fan-out, default-everything payloads, missing pagination and field selection, provider-side polling where webhooks serve, and uncompressed responses. Use this skill whenever the user shares API schemas (OpenAPI, GraphQL SDL), resolver code, endpoint designs, or asks why clients make too many calls or payloads are heavy. Part of Lean Agentic AI Skills; emits lean-findings.json.

2026-07-184

caching-strategy-designer

navveenb/lean-agentic-ai-skills

Design caching layers so work is done once, not per request — HTTP/CDN caching, application-level caches (Redis/Memcached), computed-result caching, and cache-invalidation strategy. Use this skill whenever the user wants to add caching, asks why the same work is recomputed, designs a read-heavy system, or an audit skill (db-efficiency-audit, web-carbon-audit) flags uncached repeated work. Part of Lean Agentic AI Skills; emits a cache design plus lean-findings.json.

2026-07-184

carbon-aware-scheduler

navveenb/lean-agentic-ai-skills

Design time-shifting of flexible workloads (batch jobs, CI, training, backups, crons) to hours and regions when grid electricity is cleanest, using carbon-intensity signals like Electricity Maps, WattTime, or the Carbon Aware SDK. Use this skill whenever the user mentions carbon-aware computing, scheduling flexible/deferrable jobs, demand shifting, running workloads when energy is clean, or asks how to reduce the carbon intensity (not just amount) of their compute. Part of Lean Agentic AI Skills; emits schedule designs plus lean-findings.json.

2026-07-184

carbon-budget-designer

navveenb/lean-agentic-ai-skills

Design per-feature and per-service efficiency budgets — page-weight budgets, token budgets per AI feature, query budgets per endpoint, GPU-hour budgets per training project — with owners, review checkpoints, and enforcement hooks. Use this skill whenever the user wants sustainability targets for teams, asks how to keep efficiency from regressing organizationally, mentions performance-budget-style governance for carbon/energy, or is setting engineering standards. Part of Lean Agentic AI Skills; an advisor emitting budget definitions plus lean-findings.json.

2026-07-184

name

lean-report-writer

description

Green Report Writer

Report structure

Write in prose — findings data becomes narrative, not pasted JSON:

Executive summary — scope in one sentence, findings counts by severity, the single biggest lever, one honest sentence on what's already healthy.
Scope & methodology — mandatory, verbatim-faithful to every methodology paragraph and scope_notes. A report without its methodology is greenwashing; this section cannot be cut even if the user asks for "just the findings" (offer a short version that still carries a one-line methodology note).
Findings — high severity as full subsections (issue → evidence → impact → remediation, with pattern citations as links); medium grouped by theme; low as a summary paragraph. Translate SCI terms inline for lay readers.
Remediation roadmap — sequence by effort-vs-severity: quick wins (low effort, ≥medium severity) first with a "week one" framing, then structural items.
What's already working — the passed list as prose; genuine credit, not filler.
Limitations & next steps — out_of_scope items reframed as the follow-up plan, plus pointers to real measurement tooling (CodeCarbon, Cloud Carbon Footprint, Kepler, Impact Framework) for anything the audit could only assess directionally.