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:
- Grouping fields in columns — Fields in
<groupingsDown>or<groupingsAcross>must NEVER also appear in<columns> - 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>inreferences/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_CITYall fail (useCASE_NUMBER, aSTATUSfilter,PHONE1,ADDRESS2_CITY) - Wrong scope — LeadList uses
org, notorganization - Filter column dot notation — Filter
<column>values use FLAT names (INDUSTRY,TYPE) NOT dot notation (ACCOUNT.INDUSTRYis INVALID) - Multi-value picklist filters — Use ONE
<criteriaItems>with comma-separated<value>(e.g.,Technology,Financial Services). Do NOT split into multiple criteriaItems with booleanFilter - Report
<name>over 40 characters — Count the characters before writing.Opportunities by Stage with Avg Deal Size(41 characters) fails withValue too long for field: Name maximum length is:40; use something likeOpps by Stage - Avg Deal Size - Bare
NAME/USERS.NAME— Never use a bareNAMEorUSERS.NAMEin columns or groupings; they are invalid on every standard report type. Look up the name column for the report type inreferences/column-names.md(e.g.OPPORTUNITY_NAME,FULL_NAMEfor the opportunity owner,OWNERfor Case/Lead owner,FIRST_NAME+LAST_NAME) - Unrequested or invalid
<params>— Do NOT add<params>the request didn't ask for. On Opportunity reports the only acceptedprobabilityvalue is>0(0,all,>50fail withis not one of the picklist choices); for a probability threshold, filter onPROBABILITYinstead RowCountas a column —RowCountis NOT a report column:<columns><field>RowCount</field></columns>fails withcolumns-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 withRowCountin<chartSummaries>if a chart is requested