@salesforce/afv-skills 1.32.0 → 1.34.0

package/skills/platform-report-generate/examples/AccountsCreatedThisYear.report-meta.xml

@@ -0,0 +1,48 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Report xmlns="http://soap.sforce.com/2006/04/metadata">
+    <name>Accounts Created This Year</name>
+    <reportType>AccountList</reportType>
+    <format>Summary</format>
+    <scope>organization</scope>
+    <description>Shows accounts created in the current fiscal year, grouped by industry. Demonstrates a filtered report with timeFrameFilter, row-level filter, and date-based scoping on a non-Opportunity report type.</description>
+    <showDetails>true</showDetails>
+    <showGrandTotal>true</showGrandTotal>
+    <showSubTotals>true</showSubTotals>
+    <columns>
+        <field>ACCOUNT_NAME</field>
+    </columns>
+    <columns>
+        <field>INDUSTRY</field>
+    </columns>
+    <columns>
+        <field>TYPE</field>
+    </columns>
+    <columns>
+        <field>ANNUAL_REVENUE</field>
+        <aggregateTypes>Sum</aggregateTypes>
+        <aggregateTypes>Average</aggregateTypes>
+    </columns>
+    <columns>
+        <field>CREATED_DATE</field>
+    </columns>
+    <columns>
+        <field>OWNER_FULL_NAME</field>
+    </columns>
+    <groupingsDown>
+        <field>INDUSTRY</field>
+        <dateGranularity>None</dateGranularity>
+        <sortOrder>Asc</sortOrder>
+    </groupingsDown>
+    <filter>
+        <criteriaItems>
+            <column>TYPE</column>
+            <isUnlocked>true</isUnlocked>
+            <operator>notEqual</operator>
+            <value>Analyst,Press</value>
+        </criteriaItems>
+    </filter>
+    <timeFrameFilter>
+        <dateColumn>CREATED_DATE</dateColumn>
+        <interval>INTERVAL_CURY</interval>
+    </timeFrameFilter>
+</Report>

package/skills/platform-report-generate/examples/OpportunitiesByStageAndQuarter.report-meta.xml

@@ -0,0 +1,53 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Report xmlns="http://soap.sforce.com/2006/04/metadata">
+    <name>Opportunities Stage x Quarter</name>
+    <reportType>Opportunity</reportType>
+    <format>Matrix</format>
+    <scope>organization</scope>
+    <description>Cross-tabulates opportunities by stage (rows) and close date quarter (columns) with sum of amount. Demonstrates a Matrix report with both row and column groupings and aggregates.</description>
+    <showDetails>false</showDetails>
+    <showGrandTotal>true</showGrandTotal>
+    <showSubTotals>true</showSubTotals>
+    <columns>
+        <field>OPPORTUNITY_NAME</field>
+    </columns>
+    <columns>
+        <field>ACCOUNT_NAME</field>
+    </columns>
+    <columns>
+        <field>STAGE_NAME</field>
+    </columns>
+    <columns>
+        <field>AMOUNT</field>
+        <aggregateTypes>Sum</aggregateTypes>
+    </columns>
+    <columns>
+        <field>CLOSE_DATE</field>
+    </columns>
+    <groupingsDown>
+        <field>STAGE_NAME</field>
+        <dateGranularity>None</dateGranularity>
+        <sortOrder>Asc</sortOrder>
+    </groupingsDown>
+    <groupingsAcross>
+        <field>CLOSE_DATE</field>
+        <dateGranularity>FiscalQuarter</dateGranularity>
+        <sortOrder>Asc</sortOrder>
+    </groupingsAcross>
+    <params>
+        <name>open</name>
+        <value>all</value>
+    </params>
+    <params>
+        <name>probability</name>
+        <value>&gt;0</value>
+    </params>
+    <params>
+        <name>co</name>
+        <value>1</value>
+    </params>
+    <timeFrameFilter>
+        <dateColumn>CLOSE_DATE</dateColumn>
+        <interval>INTERVAL_CURY</interval>
+    </timeFrameFilter>
+</Report>

package/skills/platform-report-generate/examples/OpportunitiesByStageReport.report-meta.xml

@@ -0,0 +1,75 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Report xmlns="http://soap.sforce.com/2006/04/metadata">
+    <name>Opportunities by Stage</name>
+    <reportType>Opportunity</reportType>
+    <format>Summary</format>
+    <scope>organization</scope>
+    <description>Groups open opportunities by stage with a sum of amount, and includes a vertical bar chart. Demonstrates a Summary report with one grouping, an aggregate column, and an embedded chart.</description>
+    <showDetails>true</showDetails>
+    <showGrandTotal>true</showGrandTotal>
+    <showSubTotals>true</showSubTotals>
+    <columns>
+        <field>OPPORTUNITY_NAME</field>
+    </columns>
+    <columns>
+        <field>ACCOUNT_NAME</field>
+    </columns>
+    <columns>
+        <field>STAGE_NAME</field>
+    </columns>
+    <columns>
+        <field>AMOUNT</field>
+        <aggregateTypes>Sum</aggregateTypes>
+    </columns>
+    <columns>
+        <field>CLOSE_DATE</field>
+    </columns>
+    <columns>
+        <field>PROBABILITY</field>
+        <aggregateTypes>Average</aggregateTypes>
+    </columns>
+    <columns>
+        <field>FULL_NAME</field>
+    </columns>
+    <groupingsDown>
+        <field>STAGE_NAME</field>
+        <dateGranularity>None</dateGranularity>
+        <sortOrder>Asc</sortOrder>
+    </groupingsDown>
+    <filter>
+        <criteriaItems>
+            <column>STAGE_NAME</column>
+            <isUnlocked>true</isUnlocked>
+            <operator>notEqual</operator>
+            <value>Closed Won,Closed Lost</value>
+        </criteriaItems>
+    </filter>
+    <params>
+        <name>open</name>
+        <value>all</value>
+    </params>
+    <params>
+        <name>probability</name>
+        <value>&gt;0</value>
+    </params>
+    <params>
+        <name>co</name>
+        <value>1</value>
+    </params>
+    <timeFrameFilter>
+        <dateColumn>CLOSE_DATE</dateColumn>
+        <interval>INTERVAL_CURY</interval>
+    </timeFrameFilter>
+    <chart>
+        <chartType>VerticalColumn</chartType>
+        <groupingColumn>STAGE_NAME</groupingColumn>
+        <chartSummaries>
+            <aggregate>Sum</aggregate>
+            <column>AMOUNT</column>
+        </chartSummaries>
+        <enableHoverLabels>true</enableHoverLabels>
+        <location>CHART_TOP</location>
+        <size>Medium</size>
+        <title>Pipeline by Stage</title>
+    </chart>
+</Report>

package/skills/platform-report-generate/examples/TabularOpportunitiesReport.report-meta.xml

@@ -0,0 +1,49 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<Report xmlns="http://soap.sforce.com/2006/04/metadata">
+    <name>New Opportunities Report</name>
+    <reportType>Opportunity</reportType>
+    <format>Tabular</format>
+    <scope>organization</scope>
+    <description>Lists all new opportunities with key fields for pipeline review. Demonstrates a simple tabular report — no groupings, no chart.</description>
+    <showDetails>true</showDetails>
+    <columns>
+        <field>OPPORTUNITY_NAME</field>
+    </columns>
+    <columns>
+        <field>ACCOUNT_NAME</field>
+    </columns>
+    <columns>
+        <field>STAGE_NAME</field>
+    </columns>
+    <columns>
+        <field>AMOUNT</field>
+    </columns>
+    <columns>
+        <field>CLOSE_DATE</field>
+    </columns>
+    <columns>
+        <field>PROBABILITY</field>
+    </columns>
+    <columns>
+        <field>LEAD_SOURCE</field>
+    </columns>
+    <columns>
+        <field>FULL_NAME</field>
+    </columns>
+    <params>
+        <name>open</name>
+        <value>all</value>
+    </params>
+    <params>
+        <name>probability</name>
+        <value>&gt;0</value>
+    </params>
+    <params>
+        <name>co</name>
+        <value>1</value>
+    </params>
+    <timeFrameFilter>
+        <dateColumn>CLOSE_DATE</dateColumn>
+        <interval>INTERVAL_CURRENT</interval>
+    </timeFrameFilter>
+</Report>

package/skills/platform-report-generate/references/chart-types.md

@@ -0,0 +1,31 @@
+# Chart Types Reference
+
+Charts can only be added to Summary or Matrix reports. A Tabular report with a `<chart>` element will fail deployment.
+
+## Available Chart Types
+
+| Chart Type | Category | Notes |
+|-----------|----------|-------|
+| `HorizontalBar` | Bar | Single-series horizontal bar |
+| `HorizontalBarGrouped` | Bar | Grouped horizontal bars (requires secondaryGroupingColumn) |
+| `HorizontalBarStacked` | Bar | Stacked horizontal bars |
+| `HorizontalBarStackedTo100` | Bar | Stacked to 100% |
+| `VerticalColumn` | Column | Single-series vertical column |
+| `VerticalColumnGrouped` | Column | Grouped vertical columns |
+| `VerticalColumnStacked` | Column | Stacked vertical columns |
+| `VerticalColumnStackedTo100` | Column | Stacked to 100% |
+| `Line` | Line | Single-series line |
+| `LineGrouped` | Line | Grouped line chart |
+| `LineCumulative` | Line | Cumulative line chart |
+| `LineCumulativeGrouped` | Line | Grouped cumulative line |
+| `Pie` | Circular | Pie chart |
+| `Donut` | Circular | Donut chart |
+| `Funnel` | Other | Funnel chart |
+| `Scatter` | Other | Scatter chart |
+| `ScatterGrouped` | Other | Grouped scatter chart |
+
+## legendPosition
+
+Only use `legendPosition` with grouped/stacked chart types (e.g., `VerticalColumnGrouped`, `HorizontalBarStacked`). Do NOT include it for simple single-series charts like `VerticalColumn`, `HorizontalBar`, `Pie`, `Donut`.
+
+Valid values: `Right`, `Bottom`, `OnChart`

package/skills/platform-report-generate/references/column-names.md

@@ -0,0 +1,80 @@
+# Column Names by Report Type
+
+Report metadata uses **platform report column names**, NOT raw API field names. These names are report-type-specific — ALWAYS verify using MCP tools (`get_metadata_type_sections` or `get_metadata_type_context`).
+
+## Opportunity
+
+| Object.Field | Report Column Name |
+|-------------|-------------------|
+| Opportunity.Name | `OPPORTUNITY_NAME` |
+| Opportunity.Amount | `AMOUNT` |
+| Opportunity.CloseDate | `CLOSE_DATE` |
+| Opportunity.StageName | `STAGE_NAME` |
+| Opportunity.Owner | `FULL_NAME` (NOT `OWNER_FULL_NAME` or `OWNER_NAME`) |
+| Account.Name | `ACCOUNT_NAME` |
+| Opportunity.CreatedDate | `CREATED_DATE` |
+| Opportunity.Probability | `PROBABILITY` |
+| Opportunity.Type | `TYPE` |
+| Opportunity.LeadSource | `LEAD_SOURCE` |
+
+## CaseList
+
+| Object.Field | Report Column Name |
+|-------------|-------------------|
+| Case.CaseNumber | `CASE_NUMBER` |
+| Case.Subject | `SUBJECT` |
+| Case.Status | `STATUS` |
+| Case.Priority | `PRIORITY` |
+| Case.Owner | `OWNER` (NOT `OWNER_NAME` or `OWNER_FULL_NAME`) |
+| Case.CreatedDate | `CREATED_DATE` |
+
+## LeadList
+
+| Object.Field | Report Column Name |
+|-------------|-------------------|
+| Lead.FirstName | `FIRST_NAME` |
+| Lead.LastName | `LAST_NAME` |
+| Lead.Company | `COMPANY` |
+| Lead.Status | `STATUS` |
+| Lead.LeadSource | `LEAD_SOURCE` |
+| Lead.CreatedDate | `CREATED_DATE` |
+
+## AccountList
+
+| Object.Field | Report Column Name |
+|-------------|-------------------|
+| Account.Name | `ACCOUNT_NAME` |
+| Account.Id | `ACCOUNT_ID` |
+
+## AccountContactRole
+
+| Object.Field | Report Column Name |
+|-------------|-------------------|
+| Contact.FirstName | `FIRST_NAME` (NOT `FULL_NAME` or `CONTACT_NAME`) |
+| Contact.LastName | `LAST_NAME` |
+| Contact.Title | `TITLE` (NOT `CONTACT_TITLE`) |
+| Contact.Email | `EMAIL` (NOT `CONTACT_EMAIL`) |
+| Contact.Phone | `PHONE1` (NOT `CONTACT_PHONE`) |
+| Contact.MailingCity | `ADDRESS2_CITY` (NOT `CONTACT_MAILINGCITY`) |
+| Account.Name | `ACCOUNT.NAME` (NOT `ACCOUNT_NAME` — uses dot notation) |
+| AccountContactRole.Role | `ROLE` |
+
+### AccountContactRole FILTER columns
+
+Filter `<column>` values use plain names for Account fields — NOT dot notation:
+- Use `INDUSTRY` (not `ACCOUNT.INDUSTRY`)
+- Use `TYPE` (not `ACCOUNT.TYPE`)
+- Use `ACCOUNT_ID` (not `ACCOUNT.ID`)
+- Only `ACCOUNT.NAME` uses dot notation (for display columns and groupings only)
+
+## Common Mistakes
+
+- `OWNER_FULL_NAME` → Use `FULL_NAME` (Opportunity) or `OWNER` (Case/Lead)
+- `OWNER_NAME` → Use `OWNER` (CaseList) or `FULL_NAME` (Opportunity)
+- `CONTACT_NAME` → Verify per report type; some use `FIRST_NAME` + `LAST_NAME`
+- `ACCOUNT_NAME` → For AccountContactRole, use `ACCOUNT.NAME` (dot notation)
+- `FULL_NAME` → NOT valid for AccountContactRole; use `FIRST_NAME` + `LAST_NAME`
+
+## Custom Fields
+
+Custom fields use the format `<ObjectApiName>.<FieldApiName__c>` (e.g., `Opportunity.Custom_Field__c`).

package/skills/platform-report-generate/references/date-intervals.md

@@ -0,0 +1,56 @@
+# Date Intervals Reference
+
+Only use values from this table. Do NOT invent interval names like `INTERVAL_CURQ` — they will cause deployment failures.
+
+## Fiscal Intervals (use when org has fiscal year configured)
+| Interval | Description |
+|----------|-------------|
+| `INTERVAL_CURRENT` | **Current fiscal quarter** — use this for "this quarter" or "current quarter" |
+| `INTERVAL_CURNEXT1` | Current + next fiscal quarter |
+| `INTERVAL_CURPREV1` | Previous + current fiscal quarter |
+| `INTERVAL_NEXT1` | Next fiscal quarter |
+| `INTERVAL_PREV1` | Previous fiscal quarter |
+| `INTERVAL_CURNEXT3` | Current + next 3 fiscal quarters |
+| `INTERVAL_CURFY` | Current fiscal year |
+| `INTERVAL_PREVFY` | Previous fiscal year |
+| `INTERVAL_NEXTFY` | Next fiscal year |
+| `INTERVAL_PREVCURFY` | Previous + current fiscal year |
+
+## Calendar Intervals
+| Interval | Description |
+|----------|-------------|
+| `INTERVAL_CURRENTQ` | Current calendar quarter |
+| `INTERVAL_NEXTQ` | Next calendar quarter |
+| `INTERVAL_PREVQ` | Previous calendar quarter |
+| `INTERVAL_CURY` | Current calendar year |
+| `INTERVAL_PREVY` | Previous calendar year |
+| `INTERVAL_NEXTY` | Next calendar year |
+| `INTERVAL_PREVCURY` | Previous + current calendar year |
+| `INTERVAL_THISMONTH` | This month |
+| `INTERVAL_LASTMONTH` | Last month |
+| `INTERVAL_NEXTMONTH` | Next month |
+| `INTERVAL_THISWEEK` | This week |
+| `INTERVAL_LASTWEEK` | Last week |
+| `INTERVAL_NEXTWEEK` | Next week |
+
+## Day-Based Intervals
+| Interval | Description |
+|----------|-------------|
+| `INTERVAL_YESTERDAY` | Yesterday |
+| `INTERVAL_TODAY` | Today |
+| `INTERVAL_TOMORROW` | Tomorrow |
+| `INTERVAL_LAST7` | Last 7 days |
+| `INTERVAL_LAST30` | Last 30 days |
+| `INTERVAL_LAST60` | Last 60 days |
+| `INTERVAL_LAST90` | Last 90 days |
+| `INTERVAL_LAST120` | Last 120 days |
+| `INTERVAL_NEXT7` | Next 7 days |
+| `INTERVAL_NEXT30` | Next 30 days |
+| `INTERVAL_NEXT60` | Next 60 days |
+| `INTERVAL_NEXT90` | Next 90 days |
+| `INTERVAL_NEXT120` | Next 120 days |
+
+## Custom
+| Interval | Description |
+|----------|-------------|
+| `INTERVAL_CUSTOM` | Custom date range — requires `<startDate>` and `<endDate>` |

package/skills/platform-report-generate/references/errors-and-troubleshooting.md

@@ -0,0 +1,71 @@
+# Common Authoring Errors
+
+Read this when a generated `.report-meta.xml` is rejected during deployment or fields don't appear in the report. Use these to validate the authored XML before handing it off; deployment itself is outside this skill's scope.
+
+| Error | Cause | Fix |
+|-------|-------|-----|
+| `Invalid report type 'X'` | Report type doesn't exist or isn't deployed in the target org | Verify the report type API name. For custom report types, ensure `<deployed>true</deployed>` is set. Use `platform-custom-report-type-generate` skill to create if missing |
+| `Invalid field 'X' for report type 'Y'` | Column name not recognized for the report type — used raw field API name instead of platform column name | Use platform column names (e.g. `ACCOUNT_NAME` not `Account.Name`). For custom fields, use `ObjectApiName.FieldApiName__c`. Use `get_metadata_type_shape` MCP tool to discover valid column names |
+| `Grouping field 'X' not found in columns` | A `<groupingsDown>` or `<groupingsAcross>` field is not also listed as a `<columns>` entry | Add the grouping field as a `<columns>` block |
+| `Chart not valid for Tabular format` | `<chart>` element present on a Tabular report | Remove the chart or change format to `Summary` or `Matrix` |
+| `Summary report requires at least one grouping` | Format is `Summary` but no `<groupingsDown>` is defined | Add at least one `<groupingsDown>` block or change format to `Tabular` |
+| `Matrix report requires row and column groupings` | Format is `Matrix` but `<groupingsDown>` or `<groupingsAcross>` is missing | Add both row and column groupings |
+| `Tabular report cannot have groupings` | `<groupingsDown>` or `<groupingsAcross>` present on a Tabular report | Remove groupings or change format to `Summary`/`Matrix` |
+| `Invalid filter operation 'X'` | Typo or unsupported operation value | Use a valid operation from `filter-operations.md` |
+| `Filter logic references filter N but only M filters exist` | `<filterLogic>` references more filters than defined | Ensure filter numbers in the logic match the actual filter count |
+| `Report folder not found` | Report file not inside a valid folder directory, or folder metadata file missing | Ensure the file is under `<sourceDir>/reports/<FolderName>/` (check sfdx-project.json for source path) and a `<FolderName>-meta.xml` exists |
+| `Too many cross filters` | More than 3 `<crossFilters>` elements | Reduce to 3 or fewer cross-filters |
+| `Joined report requires at least 2 blocks` | `<format>` is `Joined` but fewer than 2 `<block>` elements | Add at least 2 block elements |
+| `Block format cannot be Tabular` | A `<block>` inside a Joined report has `<format>Tabular</format>` | Change block format to `Summary` or `Matrix` |
+| `Aggregate types not valid for Tabular format` | `<aggregateTypes>` specified on a column in a Tabular report | Remove aggregates or change format to `Summary`/`Matrix` |
+| `Invalid date interval 'X'` | Typo in `<interval>` value inside `<timeFrameFilter>` | Use a valid interval constant (e.g. `INTERVAL_CURRENT`, `INTERVAL_CURY`) |
+| `Custom start/end date required for INTERVAL_CUSTOM` | Interval is `INTERVAL_CUSTOM` but `<startDate>` or `<endDate>` is missing | Add both `<startDate>` and `<endDate>` in `YYYY-MM-DD` format |
+
+## Common Pitfalls
+
+### Pitfall 1: Using API Field Names Instead of Platform Column Names
+
+**Wrong:**
+```xml
+<columns>
+    <field>Account.Name</field>  <!-- raw API name -->
+</columns>
+```
+
+**Right:**
+```xml
+<columns>
+    <field>ACCOUNT_NAME</field>  <!-- platform column name -->
+</columns>
+```
+
+Standard fields have specific platform column names (e.g. `OPPORTUNITY_NAME`, `STAGE_NAME`, `CLOSE_DATE`). Custom fields use the format `ObjectApiName.FieldApiName__c`.
+
+### Pitfall 2: Forgetting Grouping Fields in Columns
+
+Every field used in `<groupingsDown>` or `<groupingsAcross>` must also be present as a `<columns>` entry. Missing the column causes the grouping to fail.
+
+### Pitfall 3: Mismatched Format and Structure
+
+| If you want... | Use format | Must have |
+|----------------|------------|-----------|
+| Flat list | `Tabular` | Only `<columns>`, NO groupings |
+| Grouped rows | `Summary` | `<columns>` + `<groupingsDown>` |
+| Cross-tab | `Matrix` | `<columns>` + `<groupingsDown>` + `<groupingsAcross>` |
+| Multi-source | `Joined` | `<block>` elements (2-5), each with own columns/groupings |
+
+### Pitfall 4: Chart Summary Column Syntax
+
+The `<summaryColumn>` in a chart uses a special syntax for aggregate references:
+- `s!AMOUNT` — Sum of Amount
+- `a!AMOUNT` — Average of Amount
+- `m!AMOUNT` — Max of Amount
+- `x!AMOUNT` — Min of Amount
+- `RowCount` — Record count
+
+### Pitfall 5: Joined Report Restrictions
+
+- Joined reports do NOT support top-level `<chart>`, `<columns>`, or `<groupingsDown>` — everything goes inside `<block>` elements
+- Each block must have its own `<reportType>` — blocks can use different report types
+- Blocks align on common grouping fields for cross-block comparison
+- Block format must be `Summary` or `Matrix`, never `Tabular`

package/skills/platform-report-generate/references/filter-operations.md

@@ -0,0 +1,92 @@
+# Filter Operations Reference
+
+The `<operation>` element in a `<filter>` block determines how the field value is compared. Use these values exactly as shown.
+
+## Text & Picklist Operations
+
+| Operation | Description | `<value>` Required | Example |
+|-----------|-------------|-------------------|---------|
+| `equals` | Exact match (case-insensitive for text) | Yes | `<value>Closed Won</value>` |
+| `notEqual` | Does not equal | Yes | `<value>Closed Lost</value>` |
+| `contains` | Contains substring | Yes | `<value>Enterprise</value>` |
+| `notContain` | Does not contain substring | Yes | `<value>Test</value>` |
+| `startsWith` | Starts with prefix | Yes | `<value>Acme</value>` |
+
+## Numeric & Currency Operations
+
+| Operation | Description | `<value>` Required | Example |
+|-----------|-------------|-------------------|---------|
+| `equals` | Equal to | Yes | `<value>100000</value>` |
+| `notEqual` | Not equal to | Yes | `<value>0</value>` |
+| `lessThan` | Less than | Yes | `<value>50000</value>` |
+| `greaterThan` | Greater than | Yes | `<value>100000</value>` |
+| `lessOrEqual` | Less than or equal to | Yes | `<value>50000</value>` |
+| `greaterOrEqual` | Greater than or equal to | Yes | `<value>100000</value>` |
+
+## Multi-Select Picklist Operations
+
+| Operation | Description | `<value>` Required | Example |
+|-----------|-------------|-------------------|---------|
+| `includes` | Includes any of the specified values | Yes | `<value>Web;Phone</value>` (semicolon-separated) |
+| `excludes` | Excludes all of the specified values | Yes | `<value>Other;Unknown</value>` |
+
+## Blank / Null Operations
+
+| Operation | Description | `<value>` Required | Example |
+|-----------|-------------|-------------------|---------|
+| `isBlank` | Field is null or empty | No | (no `<value>` element needed) |
+| `notBlank` | Field is not null and not empty | No | (no `<value>` element needed) |
+
+```xml
+<filter>
+    <field>ACCOUNT_NAME</field>
+    <operation>notBlank</operation>
+</filter>
+```
+
+## Geolocation Operations
+
+| Operation | Description | `<value>` Required | Example |
+|-----------|-------------|-------------------|---------|
+| `within` | Within specified distance | Yes | `<value>DISTANCE(BillingAddress, GEOLOCATION(37.7749,-122.4194), 'mi') < 50</value>` |
+
+## Multiple Values in a Single Filter
+
+For `equals` and `notEqual` operations on picklist fields, separate multiple values with commas:
+```xml
+<filter>
+    <field>STAGE_NAME</field>
+    <operation>notEqual</operation>
+    <value>Closed Won,Closed Lost</value>
+</filter>
+```
+
+## Filter Logic
+
+Use `<filterLogic>` to combine filters with AND/OR/NOT logic. Filters are numbered starting from 1 in the order they appear in the XML.
+
+```xml
+<filter>
+    <field>STAGE_NAME</field>
+    <operation>equals</operation>
+    <value>Prospecting</value>
+</filter>
+<filter>
+    <field>AMOUNT</field>
+    <operation>greaterThan</operation>
+    <value>10000</value>
+</filter>
+<filter>
+    <field>LEAD_SOURCE</field>
+    <operation>equals</operation>
+    <value>Web</value>
+</filter>
+<filterLogic>1 AND (2 OR 3)</filterLogic>
+```
+
+**Rules:**
+- Every filter must be referenced in the logic expression
+- Parentheses control evaluation order
+- Supported operators: `AND`, `OR`, `NOT`
+- Maximum 20 filters per report
+- Without `<filterLogic>`, all filters are combined with AND

package/skills/platform-report-generate/references/verification-checklist.md

@@ -0,0 +1,47 @@
+# Verification Checklist
+
+Run through these checks before deploying any generated report metadata.
+
+## Universal Checks
+- [ ] File extension is `.report-meta.xml`
+- [ ] File is placed under `<sourceDir>/reports/<FolderName>/` (check sfdx-project.json for source path)
+- [ ] Folder metadata file exists at `<sourceDir>/reports/<FolderName>-meta.xml`
+- [ ] `<name>` is human-readable and under 40 characters
+- [ ] `<reportType>` is a valid, deployed report type API name
+- [ ] `<format>` is one of: `Tabular`, `Summary`, `Matrix`, `Joined`
+- [ ] `<scope>` is set (default `organization`; LeadList uses `org`)
+- [ ] `<description>` explains the business purpose (max 255 chars)
+- [ ] All column `<field>` values use correct platform column names
+- [ ] Custom field columns use `<ObjectApiName>.<FieldApiName__c>` format
+
+## Format-Specific Checks
+- [ ] Tabular: no `<groupingsDown>`, no `<groupingsAcross>`, no `<chart>`, no `<aggregateTypes>`
+- [ ] Summary: at least 1 `<groupingsDown>` (max 3), no `<groupingsAcross>`
+- [ ] Matrix: at least 1 `<groupingsDown>` AND at least 1 `<groupingsAcross>` (max 3 each)
+- [ ] Joined: at least 2 `<block>` elements (max 5), no top-level columns/groupings
+
+## Filter Checks
+- [ ] Each `<filter>` contains `<criteriaItems>` with a valid `<operator>`
+- [ ] Each `<criteriaItems>` has a `<column>` using the correct platform column name
+- [ ] `<value>` is present when required by the operator
+- [ ] `<filterLogic>` references all filters by number if used
+- [ ] `<timeFrameFilter>` uses a valid `<interval>` value from `references/date-intervals.md`
+- [ ] Date columns use platform column names (e.g. `CLOSE_DATE`, not `CloseDate`)
+- [ ] Multi-value picklist uses ONE criteriaItem with comma-separated values
+
+## Grouping Checks
+- [ ] `<dateGranularity>` is set for every grouping (use `None` for non-date fields)
+- [ ] `<sortOrder>` is `Asc` or `Desc`
+- [ ] Grouping fields do NOT also appear in `<columns>`
+
+## Chart Checks (if applicable)
+- [ ] Chart is only on Summary or Matrix report
+- [ ] `<chartType>` is a valid type from `references/chart-types.md`
+- [ ] `<groupingColumn>` matches a grouping field
+- [ ] `<chartSummaries>` contains valid `<aggregate>` + `<column>` (or just `<column>RowCount</column>`)
+- [ ] `legendPosition` only used with grouped/stacked charts
+
+## Cross-Filter Checks (if applicable)
+- [ ] Maximum 3 cross-filters per report
+- [ ] Maximum 5 criteria items per cross-filter
+- [ ] `<operation>` is `with` or `without`