platform-report-generate

Installation
SKILL.md

Overview

Lightning Reports define how Salesforce data is queried, grouped, filtered, and displayed. Each report is a single .report-meta.xml file placed under reports/<FolderName>/ within the project's source directory (check sfdx-project.json → packageDirectories[].path for the source root).

Critical Rules (Read First)

REQUIRED before authoring XML: Invoke platform-metadata-api-context-get and consume only the required sections of its Report entry (fields, relevant sub_types, and targeted schema/examples as needed). These assets describe XML structure, not the target org's report-type columns; use references/column-names.md or its report-type lookup for column names.

TOP DEPLOYMENT KILLERS — check these BEFORE generating any report:

  1. Grouping fields in columns — Fields in <groupingsDown> or <groupingsAcross> must NEVER also appear in <columns>
  2. Wrong column names (REQUIRED lookup) — Before writing any <columns>, <groupingsDown>, <groupingsAcross>, filter <column>, or chart <groupingColumn>, take every name from the table for the chosen <reportType> in references/column-names.md, or confirm it with the report-type lookup documented there. NEVER derive a column name from the field's API name: CASENUMBER, ISCLOSED, PHONE, MAILING_CITY all fail (use CASE_NUMBER, a STATUS filter, PHONE1, ADDRESS2_CITY)
  3. Wrong scope — LeadList uses org, not organization
  4. Filter column dot notation — Filter <column> values use FLAT names (INDUSTRY, TYPE) NOT dot notation (ACCOUNT.INDUSTRY is INVALID)
  5. Multi-value picklist filters — Use ONE <criteriaItems> with comma-separated <value> (e.g., Technology,Financial Services). Do NOT split into multiple criteriaItems with booleanFilter
  6. Report <name> over 40 characters — Count the characters before writing. Opportunities by Stage with Avg Deal Size (41 characters) fails with Value too long for field: Name maximum length is:40; use something like Opps by Stage - Avg Deal Size
  7. Bare NAME / USERS.NAME — Never use a bare NAME or USERS.NAME in columns or groupings; they are invalid on every standard report type. Look up the name column for the report type in references/column-names.md (e.g. OPPORTUNITY_NAME, FULL_NAME for the opportunity owner, OWNER for Case/Lead owner, FIRST_NAME + LAST_NAME)
  8. Unrequested or invalid <params> — Do NOT add <params> the request didn't ask for. On Opportunity reports the only accepted probability value is >0 (0, all, >50 fail with is not one of the picklist choices); for a probability threshold, filter on PROBABILITY instead
  9. RowCount as a column — RowCount is NOT a report column: <columns><field>RowCount</field></columns> fails with columns-field: Invalid value specified: RowCount. It is valid ONLY as <chartSummaries><column>RowCount</column>, as a <sortByName> value, or inside a custom summary formula's <calculatedFormula> (e.g. AMOUNT:SUM / RowCount). When the request asks for a record count, a Summary/Matrix report already shows the count per grouping — add no column; chart it with RowCount in <chartSummaries> if a chart is requested
Installs
3.1K
GitHub Stars
1.2K
First Seen
Jul 31, 2026