sustainability-reporting
Producing regulatory and voluntary sustainability disclosures from Salesforce Net Zero Cloud (formerly Sustainability Cloud) — the native ESRS / CSRD / SASB / GRI / CDP report builders, the Carbon Accounting Manager data model (Stationary Asset, Vehicle Asset, Scope 3 procurement items, Energy Use Records), the double-materiality assessment prerequisite for CSRD, the MSESRSMainDataraptor Data Mapper for ESRS reports, and the Sustainability Scorecard. NOT for Net Zero Cloud feature setup / emissions-source configuration (see integration/net-zero-cloud-setup), NOT for general CRM Analytics dashboards (Net Zero Cloud's report builders are a separate surface).
Best use case
sustainability-reporting is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Producing regulatory and voluntary sustainability disclosures from Salesforce Net Zero Cloud (formerly Sustainability Cloud) — the native ESRS / CSRD / SASB / GRI / CDP report builders, the Carbon Accounting Manager data model (Stationary Asset, Vehicle Asset, Scope 3 procurement items, Energy Use Records), the double-materiality assessment prerequisite for CSRD, the MSESRSMainDataraptor Data Mapper for ESRS reports, and the Sustainability Scorecard. NOT for Net Zero Cloud feature setup / emissions-source configuration (see integration/net-zero-cloud-setup), NOT for general CRM Analytics dashboards (Net Zero Cloud's report builders are a separate surface).
Teams using sustainability-reporting should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/sustainability-reporting/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How sustainability-reporting Compares
| Feature / Agent | sustainability-reporting | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Producing regulatory and voluntary sustainability disclosures from Salesforce Net Zero Cloud (formerly Sustainability Cloud) — the native ESRS / CSRD / SASB / GRI / CDP report builders, the Carbon Accounting Manager data model (Stationary Asset, Vehicle Asset, Scope 3 procurement items, Energy Use Records), the double-materiality assessment prerequisite for CSRD, the MSESRSMainDataraptor Data Mapper for ESRS reports, and the Sustainability Scorecard. NOT for Net Zero Cloud feature setup / emissions-source configuration (see integration/net-zero-cloud-setup), NOT for general CRM Analytics dashboards (Net Zero Cloud's report builders are a separate surface).
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Sustainability Reporting (Net Zero Cloud) Salesforce Net Zero Cloud (formerly "Sustainability Cloud") is the industry product for carbon accounting and regulatory sustainability disclosure. It ships a Carbon Accounting Manager data model and a set of native report builders for the major frameworks: **ESRS** (European Sustainability Reporting Standards under CSRD), **SASB**, **GRI**, **CDP**. This skill covers the **reporting / disclosure output layer** — which framework to use, how to drive the native report builders, the data prerequisites, and the common pitfalls. Configuring emissions sources and ingesting energy data is a separate skill. ## The Carbon Accounting Manager data model (briefly) Net Zero Cloud organizes emissions data into typed source objects that map to the GHG Protocol's three scopes: | Scope | Source category | Net Zero Cloud objects | |---|---|---| | Scope 1 | Direct emissions (owned facilities, fleet) | `StationaryAssetCarbonInventory`, `VehicleAssetCarbonInventory` | | Scope 2 | Purchased energy | `StationaryAssetEnergyUse`, electricity / heating purchases | | Scope 3 | Value-chain (procurement, travel, waste) | `ScopeThreeCarbonInventory`, procurement / travel / waste records | The unit-of-measure inputs are **Energy Use Records** — typed source records that the platform converts into CO2-equivalent emissions via emission factors. ## Report builders | Framework | Output format | Builder name | |---|---|---| | ESRS (CSRD) | Word document via Data Mapper | ESRS Report Builder, MSESRSMainDataraptor | | SASB | Sector-specific structured output | SASB Report Builder (sector applicability matters) | | GRI | Disclosure-aligned structured output | GRI Report Builder | | CDP | Submission-aligned questionnaire output | CDP Report Builder | The ESRS path uses an OmniScript / Data Mapper combination that generates a Microsoft Word disclosure. CSRD compliance specifically requires that a **double-materiality assessment** has been completed before the report is generated — skipping this prerequisite produces a non-compliant CSRD output even if the report builder runs without error. ## Double-materiality (CSRD prerequisite) Double materiality has two axes: - **Impact materiality** — how the business impacts society and the environment. - **Financial materiality** — how sustainability matters affect the business's financial performance. CSRD requires both. The assessment is a discrete project step, not something the report builder produces. Net Zero Cloud has tooling to capture the assessment results; the work itself is human and stakeholder-driven. ## Sustainability Scorecard The Sustainability Scorecard is Net Zero Cloud's snapshot view of emissions performance against targets. It aggregates Scope 1 / 2 / 3 data into a single readable summary; it is a different surface from the framework-specific report builders. Scorecard is for internal monitoring; report builders are for external disclosure. ## Recommended Workflow 1. **Confirm Net Zero Cloud is licensed and provisioned.** It is a separately purchased industry cloud; presence is not implied by an Enterprise / Unlimited license. 2. **Select the target framework.** CSRD / ESRS for EU regulated entities; SASB for sector-aligned investor disclosures; GRI for general voluntary disclosure; CDP for CDP submission. More than one is common; report builders run independently. 3. **Verify double-materiality assessment** if CSRD is in scope. Without it, the ESRS output is structurally correct but compliance-deficient. 4. **Validate the underlying emissions data.** Energy Use Records, asset coverage, supplier coverage. Gaps in input data produce gaps in disclosure. 5. **Run the framework-specific report builder.** ESRS goes through MSESRSMainDataraptor and produces a Word document; SASB / GRI / CDP have their own outputs. 6. **Reconcile against the Sustainability Scorecard.** Scorecard and report-builder numbers should agree for the same scope and period; a mismatch means a configuration drift. 7. **Track disclosure-readiness gaps.** SASB sector applicability, CDP submission workflow, and supplier-data coverage are common gap areas. Document for the next reporting cycle. ## What This Skill Does Not Cover | Topic | See instead | |---|---| | Net Zero Cloud feature setup / emissions-source config | `integration/net-zero-cloud-setup` | | CRM Analytics general dashboards | `data/crm-analytics-patterns` | | Sustainability Cloud (legacy product name) before rebrand | (Same product; treat the name as Net Zero Cloud) | | ESG performance benchmarking | App-layer (CDP, MSCI, etc.) |
Related Skills
sales-reporting-data-model
Use when designing or troubleshooting Salesforce sales reporting — covers Historical Trend Reporting, Reporting Snapshots, and Custom Report Types for pipeline and opportunity analysis. Trigger keywords: historical trending, opportunity snapshot, reporting snapshot, pipeline history, custom report type join, point-in-time reporting. NOT for CRM Analytics (Tableau CRM / Einstein Analytics) or Marketing Cloud reports. NOT for general SOQL optimization.
omni-channel-reporting-data
Omni-Channel analytics data: agent work records, queue metrics, capacity utilization, wait time reporting. NOT for admin routing setup.
fsl-reporting-data-model
Use this skill when building Salesforce reports and dashboards on FSL operational data: job completion metrics, travel time analytics, first-time fix rate, utilization, and service performance. Trigger keywords: FSL reporting, ServiceAppointment reports, ActualDuration ActualTravelTime, first-time fix rate custom field, FSL utilization metrics. NOT for CRM Analytics / Field Service Intelligence (Einstein Analytics), ServiceReport PDF generation, or non-FSL service reporting.
marketing-reporting-requirements
Use this skill when gathering and documenting Salesforce marketing reporting requirements: defining KPIs, choosing an attribution model (First Touch / Last Touch / Even Distribution / Multi-Touch), selecting the correct Campaign Influence configuration, and mapping business questions to Salesforce report types and dashboard features. NOT for building the dashboards themselves, configuring CRM Analytics datasets, writing SOQL for marketing reports, or setting up Marketing Cloud Engagement journeys.
xss-and-injection-prevention
Use when writing or reviewing Visualforce pages, Apex controllers, or LWC components that output user-supplied data, build dynamic queries, or construct HTTP responses. Triggers: 'XSS in Visualforce', 'SOQL injection vulnerability', 'how to encode output in Apex', 'JSENCODE Visualforce', 'open redirect prevention'. NOT for Apex CRUD/FLS enforcement (use soql-security or apex-crud-and-fls), NOT for Shield encryption (use shield-encryption-key-management), NOT for AppExchange security review process (use secure-coding-review-checklist).
visualforce-security-and-modernization
Use when hardening or modernizing legacy Visualforce pages — covers the platform CSRF token model and when disabling it is a security regression, view state encryption guarantees and the 170 KB ceiling, FLS/CRUD enforcement gaps on `<apex:outputField>` and on getters that return sObjects, `<apex:includeScript>` interaction with the org Content Security Policy, hosting LWC inside a VF page via `lightning:container` / `lightning-out`, and the retire-vs-harden-vs-leave-alone decision for an inventory of legacy pages. Triggers: 'should I rewrite this Visualforce page in LWC', 'CSRF protection disabled on Visualforce page is that safe', 'community user sees a field they should not on a Visualforce page', 'view state encryption is that enough for sensitive data', 'how do I host an LWC inside a Visualforce page', 'apex:dynamicComponent and apex:actionFunction safe to keep'. NOT for greenfield Visualforce architecture (use apex/visualforce-fundamentals — controller types, view state pattern selection, PDF rendering); NOT for Visualforce email template authoring (use apex/visualforce-email-templates if/when that skill is authored); NOT for general Apex security review across triggers and async (use apex/soql-security and security/secure-coding-review-checklist).
transaction-security-policies
Transaction Security policy creation and configuration: condition builder, enhanced policies, enforcement actions (block, MFA, notification, end session), real-time monitoring mode, and policy troubleshooting. NOT for Event Monitoring log analysis or Shield Event Monitoring setup (use event-monitoring). NOT for Apex testing or debug-log analysis.
sso-saml-troubleshooting
Diagnosing broken SAML SSO into Salesforce — IdP-initiated vs SP-initiated flows, signing-certificate validity / expiry, NameID format mismatches, RelayState handling, audience / entityId / issuer mismatches, clock skew, the SAML Assertion Validator in Setup, the Login History debug log, and the My Domain prerequisite for SSO. Covers the standard diagnostic loop: read the SAML response, identify which check failed, fix at the IdP or SP. NOT for OAuth / OpenID Connect SSO (see security/oauth-openid-troubleshooting), NOT for setting up SSO from scratch (see security/sso-saml-setup).
shield-kms-byok-setup
Configure Shield Platform Encryption with customer-supplied (BYOK) or customer-held (Cache-Only Key Service) tenant secrets, rotate them, and recover. NOT for Classic Encryption or field masking.
shield-event-log-retention-strategy
Use when designing Salesforce Shield Event Monitoring retention, SIEM routing, and storage-tier strategy — which event types to keep, for how long, where, and how to answer audit queries across hot/warm/cold tiers. Triggers: 'shield event log retention', 'route event monitoring to splunk', 'how long to keep login history', 'siem salesforce integration', 'event monitoring storage tier'. NOT for enabling Shield (see salesforce-shield-deployment).
session-management-and-timeout
Use this skill when configuring session timeout values, concurrent session limits, session IP locking, or logout behavior in Salesforce. Covers org-wide session settings, profile-level overrides, Connected App session policies, and Metadata API SecuritySettings deployment. NOT for OAuth token refresh flows, login IP ranges, or MFA/identity-provider configuration.
session-high-assurance-policies
Enforce step-up authentication for sensitive pages/objects using High Assurance session level and login flow policies. NOT for initial MFA enrollment UX.