@salesforce/afv-skills 1.32.0 → 1.34.0

package/skills/platform-data-and-tooling-api-context-get/assets/tooling_api/WorkflowRule.json

@@ -0,0 +1,52 @@
+{
+  "sections": [
+    "title",
+    "description",
+    "supported_soap_calls",
+    "supported_rest_api_http_methods",
+    "fields",
+    "wsdl_segment"
+  ],
+  "title": "WorkflowRule - Tooling API",
+  "description": "Represents a workflow rule that is used to fire off a specific workflow action when the specified criteria is met. Includes access to the associated WorkflowRule object in Salesforce Metadata API.",
+  "supported_soap_calls": "`create()`, `delete()`, `query()`, `retrieve()`, `search()`, `update()`, `upsert()`",
+  "supported_rest_api_http_methods": "`Query`, `DELETE`, `GET`, `PATCH`, `POST`",
+  "fields_columns": [
+    "type",
+    "properties",
+    "description"
+  ],
+  "fields": {
+    "FullName": {
+      "type": "string",
+      "properties": "Create, Group, Nillable",
+      "description": "The full name of the associated metadata object in Metadata API. Query this field only if the query result contains no more than one record. Otherwise, an error is returned. If more than one record exists, use multiple queries to retrieve the records. This limit protects performance."
+    },
+    "ManageableState": {
+      "type": "ManageableState enumerated list",
+      "properties": "Filter, Group, Nillable, Restricted picklist, Sort",
+      "description": "Indicates the manageable state of the specified component that is contained in a package: beta deleted deprecated deprecatedEditable installed installedEditable released unmanaged"
+    },
+    "Metadata": {
+      "type": "mns:WorkflowRule",
+      "properties": "Create, Nillable, Update",
+      "description": "Workflow rule metadata. Query this field only if the query result contains no more than one record. Otherwise, an error is returned. If more than one record exists, use multiple queries to retrieve the records. This limit protects performance."
+    },
+    "Name": {
+      "type": "string",
+      "properties": "Filter, Group, Sort",
+      "description": "The enum name or ID of entity this rule is associated with."
+    },
+    "NamespacePrefix": {
+      "type": "string",
+      "properties": "Filter, Group, idLookup, Sort",
+      "description": "The namespace of the package containing the workflow rule object."
+    },
+    "TableEnumOrId": {
+      "type": "picklist",
+      "properties": "Filter, Group, Restricted picklist, Sort",
+      "description": "The enum (for example, Account) or ID of the object for this workflow rule."
+    }
+  },
+  "wsdl_segment": "```xml\n<xsd:complexType name=\"WorkflowRule\">\n  <xsd:complexContent>\n    <xsd:extension base=\"ens:sObject\">\n      <xsd:sequence>\n        <xsd:element name=\"FullName\" minOccurs=\"0\" type=\"xsd:string\" nillable=\"true\"/>\n        <xsd:element name=\"Metadata\" minOccurs=\"0\" type=\"mns:WorkflowRule\" nillable=\"true\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n\n\n<xsd:complexType name=\"WorkflowRule\">\n  <xsd:complexContent>\n    <xsd:extension base=\"mns:Metadata\">\n      <xsd:sequence>\n        <xsd:element name=\"actions\" minOccurs=\"0\" maxOccurs=\"unbounded\" type=\"mns:WorkflowActionReference\"/>\n        <xsd:element name=\"active\" type=\"xsd:boolean\"/>\n        <xsd:element name=\"booleanFilter\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"criteriaItems\" minOccurs=\"0\" maxOccurs=\"unbounded\" type=\"mns:FilterItem\"/>\n        <xsd:element name=\"description\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"failedMigrationToolVersion\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"formula\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"triggerType\" type=\"tns:WorkflowTriggerTypes\"/>\n        <xsd:element name=\"workflowTimeTriggers\" minOccurs=\"0\" maxOccurs=\"unbounded\" type=\"mns:WorkflowTimeTrigger\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n<xsd:simpleType name=\"WorkflowTriggerTypes\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"onCreateOnly\"/>\n    <xsd:enumeration value=\"onCreateOrTriggeringUpdate\"/>\n    <xsd:enumeration value=\"onAllChanges\"/>\n    <xsd:enumeration value=\"OnRecursiveUpdate\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n```"
+}

package/skills/platform-data-and-tooling-api-context-get/assets/tooling_api/WorkflowTask.json

@@ -0,0 +1,68 @@
+{
+  "sections": [
+    "title",
+    "description",
+    "supported_soap_calls",
+    "supported_rest_api_http_methods",
+    "fields",
+    "wsdl_segment"
+  ],
+  "title": "WorkflowTask - Tooling API",
+  "description": "Represents a workflow task that is used to fire off a specific workflow action when the specified criteria is met. Includes access to the associated WorkflowRule object in Salesforce Metadata API.",
+  "supported_soap_calls": "`create()`, `delete()`, `query()`, `retrieve()`, `search()`, `update()`, `upsert()`",
+  "supported_rest_api_http_methods": "`Query`, `DELETE`, `GET`, `PATCH`, `POST`",
+  "fields_columns": [
+    "type",
+    "properties",
+    "description"
+  ],
+  "fields": {
+    "EntityDefinition": {
+      "type": "EntityDefinition",
+      "properties": "Filter, Group, Sort.",
+      "description": "The entity definition for the object associated with the validation rule.",
+      "required": true
+    },
+    "EntityDefinitionId": {
+      "type": "string",
+      "properties": "Filter, Group, Sort",
+      "description": "The ID of the entity containing the workflow task."
+    },
+    "FullName": {
+      "type": "string",
+      "properties": "Create, Group, Nillable",
+      "description": "The full name of the associated metadata object in Metadata API. Query this field only if the query result contains no more than one record. Otherwise, an error is returned. If more than one record exists, use multiple queries to retrieve the records. This limit protects performance."
+    },
+    "ManageableState": {
+      "type": "ManageableState enumerated list",
+      "properties": "Filter, Group, Nillable, Restricted picklist, Sort",
+      "description": "Indicates the manageable state of the specified component that is contained in a package: beta deleted deprecated deprecatedEditable installed installedEditable released unmanaged"
+    },
+    "Metadata": {
+      "type": "mns:WorkflowTask",
+      "properties": "Create, Nillable, Update",
+      "description": "Workflow task metadata. Query this field only if the query result contains no more than one record. Otherwise, an error is returned. If more than one record exists, use multiple queries to retrieve the records. This limit protects performance."
+    },
+    "NamespacePrefix": {
+      "type": "string",
+      "properties": "Filter, Group, Nillable, Sort",
+      "description": "The namespace of the package containing the workflow task object."
+    },
+    "Priority": {
+      "type": "picklist",
+      "properties": "Filter, Group, Sort",
+      "description": "The task’s priority. Values are: High Normal Low"
+    },
+    "Status": {
+      "type": "picklist",
+      "properties": "Filter, Group, Sort",
+      "description": "The task’s status. Values are: Not Started In Progress Completed Waiting on someone else Deferred"
+    },
+    "Subject": {
+      "type": "string",
+      "properties": "Filter, Group, idLookup, Sort",
+      "description": "A subject for the workflow task. It is used if an email notification is sent when the task is assigned."
+    }
+  },
+  "wsdl_segment": "```xml\n<xsd:simpleType name=\"ActionTaskAssignedToTypes\">\n  <xsd:restriction base=\"xsd:string\">\n    <xsd:enumeration value=\"user\"/>\n    <xsd:enumeration value=\"role\"/>\n    <xsd:enumeration value=\"opportunityTeam\"/>\n    <xsd:enumeration value=\"accountTeam\"/>\n    <xsd:enumeration value=\"owner\"/>\n    <xsd:enumeration value=\"accountOwner\"/>\n    <xsd:enumeration value=\"creator\"/>\n    <xsd:enumeration value=\"accountCreator\"/>\n    <xsd:enumeration value=\"partnerUser\"/>\n    <xsd:enumeration value=\"portalRole\"/>\n  </xsd:restriction>\n</xsd:simpleType>\n<xsd:complexType name=\"WorkflowTask\">\n  <xsd:complexContent>\n    <xsd:extension base=\"ens:sObject\">\n      <xsd:sequence>\n        <xsd:element name=\"FullName\" minOccurs=\"0\" type=\"xsd:string\" nillable=\"true\"/>\n        <xsd:element name=\"Metadata\" minOccurs=\"0\" type=\"mns:WorkflowTask\" nillable=\"true\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n\n\n<xsd:complexType name=\"WorkflowTask\">\n  <xsd:complexContent>\n    <xsd:extension base=\"mns:WorkflowAction\">\n      <xsd:sequence>\n        <xsd:element name=\"assignedTo\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"assignedToType\" type=\"tns:ActionTaskAssignedToTypes\"/>\n        <xsd:element name=\"description\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"dueDateOffset\" type=\"xsd:int\"/>\n        <xsd:element name=\"notifyAssignee\" type=\"xsd:boolean\"/>\n        <xsd:element name=\"offsetFromField\" minOccurs=\"0\" type=\"xsd:string\"/>\n        <xsd:element name=\"priority\" type=\"xsd:string\"/>\n        <xsd:element name=\"protected\" type=\"xsd:boolean\"/>\n        <xsd:element name=\"status\" type=\"xsd:string\"/>\n        <xsd:element name=\"subject\" type=\"xsd:string\"/>\n      </xsd:sequence>\n    </xsd:extension>\n  </xsd:complexContent>\n</xsd:complexType>\n```"
+}

package/skills/platform-data-and-tooling-api-context-get/examples/README.md

@@ -0,0 +1,93 @@
+# Salesforce Data + Tooling API - Section-Specific Loading Examples
+
+This directory contains working code examples demonstrating how to
+programmatically load only the sections you need from the enterprise
+(SOQL/DML sObject) and Tooling (developer record) JSON files, and how to
+traverse this skill's surface-specific structure.
+
+## Critical Warning
+
+**NEVER load these JSON files whole (Read, cat, whole-file `JSON.parse`)!**
+
+Enterprise sObjects like `Account.json` carry a large `wsdl_segment` and a
+separate `field_reference` catalog. Loading the entire file wastes 60-80% of
+tokens. Extract only the section you need.
+
+## Structure this skill exposes
+
+- **`assets/enterprise_api/`** — standard sObjects you query with SOQL
+  and modify with DML (custom `__c` objects are not included — describe the
+  live org for those). `fields` entries carry `properties`
+  (Create/Filter/Sort/Group/Nillable/Update) plus relationship metadata
+  (`relationship_name`, `refers_to`, `relationship_type`).
+- **`assets/tooling_api/`** — developer/diagnostics records (ApexClass,
+  TraceFlag, EntityDefinition, ...). Expose `supported_rest_api_http_methods`
+  / `supported_soap_calls`; queried via `/services/data/vXX.0/tooling/query`.
+- **`fields` vs `field_reference`** — `field_reference` is a SEPARATE catalog,
+  **not a subset** of `fields`. System/audit fields (Id, CreatedDate, ...)
+  frequently live ONLY in `field_reference`. If a field isn't in `fields`,
+  check `field_reference` before concluding it doesn't exist.
+
+## Available Examples
+
+### 1. Python Example
+**File**: [`python_section_loading.py`](./python_section_loading.py)
+
+**Usage**:
+```bash
+python3 examples/python_section_loading.py
+```
+
+**Key Pattern** (respect field properties before writing SOQL):
+```python
+import json
+with open('assets/enterprise_api/Opportunity.json') as f:
+    data = json.load(f)
+filterable = [n for n, m in data['fields'].items()
+              if 'filter' in (m.get('properties', '') or '').lower()]
+```
+
+### 2. JavaScript/Node.js Example
+**File**: [`javascript_section_loading.js`](./javascript_section_loading.js)
+
+**Usage**:
+```bash
+node examples/javascript_section_loading.js
+```
+
+### 3. Bash + jq Example
+**File**: [`bash_section_loading.sh`](./bash_section_loading.sh)
+
+**Usage**:
+```bash
+bash examples/bash_section_loading.sh
+```
+
+**Key Pattern** (check BOTH catalogs):
+```bash
+# Fields present ONLY in field_reference (not in fields):
+jq -r '[(.field_reference | keys[]) as $k
+         | select((.fields | has($k)) | not) | $k][:5][]' \
+   assets/enterprise_api/Account.json
+```
+
+## What every example demonstrates
+
+1. Load only the `fields` section from an enterprise sObject
+2. Find **filterable** fields (WHERE-safe) via the `properties` string
+3. Traverse a relationship (`relationship_name` / `refers_to`)
+4. Check **both** `fields` and `field_reference` (dual catalog)
+5. Read a Tooling record's `supported_rest_api_http_methods`
+
+## Property → SOQL/DML capability
+
+| `properties` token | Enables |
+|--------------------|---------|
+| `Filter`           | `WHERE` clause |
+| `Sort`             | `ORDER BY` |
+| `Group`            | `GROUP BY` |
+| `Create`           | `insert` DML |
+| `Update`           | `update` DML |
+| `Nillable`         | may be null (else required on insert) |
+
+A field without the needed token fails at runtime — verify before querying.

package/skills/platform-data-and-tooling-api-context-get/examples/bash_section_loading.sh

@@ -0,0 +1,126 @@
+#!/bin/bash
+#
+# Salesforce Data + Tooling API - Section-Specific Loading Examples (Bash + jq)
+#
+# Demonstrates how to programmatically load only the sections you need from the
+# enterprise (SOQL/DML sObject) and Tooling (developer record) JSON files, and
+# how to traverse this skill's surface-specific structure:
+#   - enterprise fields carry query/DML `properties` (Create/Filter/Sort/Group/
+#     Nillable/Update) plus relationship metadata (relationship_name / refers_to)
+#   - `field_reference` is a SEPARATE catalog, not a subset of `fields`
+#   - Tooling records expose supported_rest_api_http_methods / supported_soap_calls
+#
+# Prerequisites: jq
+#   - macOS: brew install jq   Linux: apt-get install jq
+#
+# CRITICAL: Do NOT Read/cat these JSON files whole — Account.json etc. carry a
+# huge wsdl_segment. Extract only the section you need.
+#
+
+ENTERPRISE_DIR="assets/enterprise_api"
+TOOLING_DIR="assets/tooling_api"
+
+
+# Example 1: Load ONLY the 'fields' section from an enterprise sObject
+load_fields_section() {
+    echo "Example 1: enterprise fields section"
+
+    local f="$ENTERPRISE_DIR/Account.json"
+    local field_count=$(jq '.fields | length' "$f")
+
+    echo "Account has $field_count fields in the 'fields' section"
+    # Skip: wsdl_segment (verbose), field_reference (load separately if needed)
+}
+
+
+# Example 2: Find filterable fields (usable in a SOQL WHERE clause)
+#
+# The `properties` string controls capability: Filter -> WHERE, Sort -> ORDER BY,
+# Group -> GROUP BY, Create/Update -> DML. Verify before writing the query.
+find_filterable_fields() {
+    echo -e "\nExample 2: filterable fields (WHERE-safe)"
+
+    local f="$ENTERPRISE_DIR/Opportunity.json"
+
+    echo "First 5 filterable Opportunity fields:"
+    jq -r '.fields | to_entries[]
+             | select(.value.properties // "" | test("Filter"))
+             | .key' "$f" | head -5
+}
+
+
+# Example 3: Traverse a relationship (reference field -> parent object)
+#
+# For a reference field, relationship_name is the SOQL traversal path and
+# refers_to names the target object(s): SELECT Owner.Name FROM Account.
+traverse_relationship() {
+    echo -e "\nExample 3: relationship traversal"
+
+    local f="$ENTERPRISE_DIR/Contact.json"
+
+    # Show the relationship metadata for the AccountId lookup
+    jq -r '.fields.AccountId
+             | "AccountId -> relationship_name=\(.relationship_name) refers_to=\(.refers_to)"' "$f"
+    echo "SOQL: SELECT Id, Account.Name FROM Contact"
+}
+
+
+# Example 4: Check BOTH catalogs — field_reference is NOT a subset of fields
+#
+# System/audit fields (Id, CreatedDate, ...) frequently live ONLY in
+# field_reference. If a field isn't in `fields`, check `field_reference` before
+# concluding it doesn't exist.
+check_both_catalogs() {
+    echo -e "\nExample 4: fields vs field_reference (dual catalog)"
+
+    local f="$ENTERPRISE_DIR/Account.json"
+
+    local fields_n=$(jq '.fields | length' "$f")
+    local ref_n=$(jq '.field_reference | length' "$f")
+    echo "Account: fields=$fields_n  field_reference=$ref_n"
+
+    echo "Fields present ONLY in field_reference (first 5):"
+    jq -r '[(.field_reference | keys[]) as $k
+             | select((.fields | has($k)) | not) | $k][:5][]' "$f"
+}
+
+
+# Example 5: Tooling record — check supported HTTP methods before querying
+#
+# Tooling objects are queried against /services/data/vXX.0/tooling/query, not the
+# regular Data API. Many are read-only; check the supported methods first.
+tooling_supported_methods() {
+    echo -e "\nExample 5: Tooling API supported methods"
+
+    local f="$TOOLING_DIR/ApexClass.json"
+
+    local methods=$(jq -r '.supported_rest_api_http_methods' "$f")
+    echo "ApexClass REST methods: $methods"
+    echo "First 5 ApexClass fields:"
+    jq -r '.fields | keys[:5][]' "$f"
+}
+
+
+# WRONG APPROACH - DO NOT USE
+#
+#   Read assets/enterprise_api/Account.json   # loads the huge wsdl_segment!
+#   cat  assets/enterprise_api/Account.json   # loads the entire file!
+#
+# Extract only the section you need instead.
+
+
+main() {
+    echo "Salesforce Data + Tooling API - Section-Specific Loading (Bash)"
+    echo "=============================================================="
+    echo ""
+
+    load_fields_section
+    find_filterable_fields
+    traverse_relationship
+    check_both_catalogs
+    tooling_supported_methods
+}
+
+if [[ "${BASH_SOURCE[0]}" == "${0}" ]]; then
+    main
+fi

package/skills/platform-data-and-tooling-api-context-get/examples/javascript_section_loading.js

@@ -0,0 +1,97 @@
+/**
+ * Salesforce Data + Tooling API - Section-Specific Loading Examples (Node.js)
+ *
+ * Demonstrates loading only the sections you need from the enterprise (SOQL/DML
+ * sObject) and Tooling (developer record) JSON files, and how to traverse this
+ * skill's surface-specific structure:
+ *   - enterprise `fields` carry query/DML `properties` (Create/Filter/Sort/Group/
+ *     Nillable/Update) plus relationship metadata (relationship_name / refers_to)
+ *   - `field_reference` is a SEPARATE catalog, not a subset of `fields`
+ *   - Tooling records expose supported_rest_api_http_methods / supported_soap_calls
+ *
+ * CRITICAL: Do NOT Read/cat these JSON files whole — Account.json etc. carry a
+ * huge wsdl_segment. Extract only the section you need.
+ */
+
+const fs = require('fs');
+const path = require('path');
+
+const ENTERPRISE_DIR = ['assets', 'enterprise_api'];
+const TOOLING_DIR = ['assets', 'tooling_api'];
+
+function load(dirParts, file) {
+  return JSON.parse(fs.readFileSync(path.join(...dirParts, file), 'utf-8'));
+}
+
+// Example 1: Load ONLY the 'fields' section from an enterprise sObject
+function loadFieldsSection() {
+  console.log('Example 1: enterprise fields section');
+  const data = load(ENTERPRISE_DIR, 'Account.json');
+  const fields = data.fields || {};
+  // Skip wsdl_segment (verbose) and field_reference (load separately if needed)
+  console.log(`Account has ${Object.keys(fields).length} fields in the 'fields' section`);
+}
+
+// Example 2: Find filterable fields (usable in a SOQL WHERE clause)
+//
+// The `properties` string controls capability: Filter -> WHERE, Sort ->
+// ORDER BY, Group -> GROUP BY, Create/Update -> DML. Compare case-insensitively.
+function findFilterableFields() {
+  console.log('\nExample 2: filterable fields (WHERE-safe)');
+  const data = load(ENTERPRISE_DIR, 'Opportunity.json');
+  const filterable = Object.entries(data.fields || {})
+    .filter(([, meta]) => (meta.properties || '').toLowerCase().includes('filter'))
+    .map(([name]) => name);
+  console.log(`Opportunity has ${filterable.length} filterable fields; first 5: ${filterable.slice(0, 5).join(', ')}`);
+}
+
+// Example 3: Traverse a relationship (reference field -> parent object)
+//
+// relationship_name is the SOQL traversal path; refers_to names the target.
+function traverseRelationship() {
+  console.log('\nExample 3: relationship traversal');
+  const data = load(ENTERPRISE_DIR, 'Contact.json');
+  const account = (data.fields || {}).AccountId || {};
+  console.log(`AccountId -> relationship_name=${account.relationship_name} refers_to=${account.refers_to}`);
+  console.log('SOQL: SELECT Id, Account.Name FROM Contact');
+}
+
+// Example 4: Check BOTH catalogs — field_reference is NOT a subset of fields
+//
+// System/audit fields (Id, CreatedDate, ...) frequently live ONLY in
+// field_reference. If a field isn't in `fields`, check `field_reference`.
+function checkBothCatalogs() {
+  console.log('\nExample 4: fields vs field_reference (dual catalog)');
+  const data = load(ENTERPRISE_DIR, 'Account.json');
+  const fields = new Set(Object.keys(data.fields || {}));
+  const ref = Object.keys(data.field_reference || {});
+  const onlyInRef = ref.filter((k) => !fields.has(k));
+  console.log(`Account: fields=${fields.size} field_reference=${ref.length}`);
+  console.log(`Only in field_reference (first 5): ${onlyInRef.slice(0, 5).join(', ')}`);
+}
+
+// Example 5: Tooling record — check supported HTTP methods before querying
+//
+// Tooling objects query against /services/data/vXX.0/tooling/query, not the
+// regular Data API. Many are read-only; check the methods first.
+function toolingSupportedMethods() {
+  console.log('\nExample 5: Tooling API supported methods');
+  const data = load(TOOLING_DIR, 'ApexClass.json');
+  console.log(`ApexClass REST methods: ${data.supported_rest_api_http_methods || ''}`);
+  console.log(`First 5 ApexClass fields: ${Object.keys(data.fields || {}).slice(0, 5).join(', ')}`);
+}
+
+// WRONG APPROACH - DO NOT USE
+//   fs.readFileSync('assets/enterprise_api/Account.json')  // then use whole object
+// loads the huge wsdl_segment into memory. Extract only the section you need.
+
+if (require.main === module) {
+  console.log('Salesforce Data + Tooling API - Section-Specific Loading (Node.js)');
+  console.log('==================================================================');
+  console.log('');
+  loadFieldsSection();
+  findFilterableFields();
+  traverseRelationship();
+  checkBothCatalogs();
+  toolingSupportedMethods();
+}

package/skills/platform-data-and-tooling-api-context-get/examples/python_section_loading.py

@@ -0,0 +1,109 @@
+#!/usr/bin/env python3
+"""
+Salesforce Data + Tooling API - Section-Specific Loading Examples (Python)
+
+Demonstrates loading only the sections you need from the enterprise (SOQL/DML
+sObject) and Tooling (developer record) JSON files, and how to traverse this
+skill's surface-specific structure:
+  - enterprise `fields` carry query/DML `properties` (Create/Filter/Sort/Group/
+    Nillable/Update) plus relationship metadata (relationship_name / refers_to)
+  - `field_reference` is a SEPARATE catalog, not a subset of `fields`
+  - Tooling records expose supported_rest_api_http_methods / supported_soap_calls
+
+CRITICAL: Do NOT Read/cat these JSON files whole — Account.json etc. carry a
+huge wsdl_segment. Extract only the section you need.
+"""
+
+import json
+from pathlib import Path
+
+ENTERPRISE_DIR = Path('assets/enterprise_api')
+TOOLING_DIR = Path('assets/tooling_api')
+
+
+def _load(path):
+    with open(path, 'r', encoding='utf-8') as f:
+        return json.load(f)
+
+
+def load_fields_section():
+    """Example 1: Load ONLY the 'fields' section from an enterprise sObject."""
+    data = _load(ENTERPRISE_DIR / 'Account.json')
+    fields = data.get('fields', {})
+    # Skip wsdl_segment (verbose) and field_reference (load separately if needed)
+    print(f"Account has {len(fields)} fields in the 'fields' section")
+    return fields
+
+
+def find_filterable_fields():
+    """Example 2: Find filterable fields (usable in a SOQL WHERE clause).
+
+    The `properties` string controls capability: Filter -> WHERE, Sort ->
+    ORDER BY, Group -> GROUP BY, Create/Update -> DML. Compare case-insensitively.
+    """
+    data = _load(ENTERPRISE_DIR / 'Opportunity.json')
+    filterable = [
+        name for name, meta in data.get('fields', {}).items()
+        if 'filter' in (meta.get('properties', '') or '').lower()
+    ]
+    print(f"Opportunity has {len(filterable)} filterable fields; first 5: {filterable[:5]}")
+    return filterable
+
+
+def traverse_relationship():
+    """Example 3: Traverse a relationship (reference field -> parent object).
+
+    relationship_name is the SOQL traversal path; refers_to names the target.
+    """
+    data = _load(ENTERPRISE_DIR / 'Contact.json')
+    account = data.get('fields', {}).get('AccountId', {})
+    print(f"AccountId -> relationship_name={account.get('relationship_name')} "
+          f"refers_to={account.get('refers_to')}")
+    print("SOQL: SELECT Id, Account.Name FROM Contact")
+    return account
+
+
+def check_both_catalogs():
+    """Example 4: Check BOTH catalogs — field_reference is NOT a subset of fields.
+
+    System/audit fields (Id, CreatedDate, ...) frequently live ONLY in
+    field_reference. If a field isn't in `fields`, check `field_reference`.
+    """
+    data = _load(ENTERPRISE_DIR / 'Account.json')
+    fields = set(data.get('fields', {}))
+    ref = set(data.get('field_reference', {}))
+    only_in_ref = sorted(ref - fields)
+    print(f"Account: fields={len(fields)} field_reference={len(ref)}")
+    print(f"Only in field_reference (first 5): {only_in_ref[:5]}")
+    return only_in_ref
+
+
+def tooling_supported_methods():
+    """Example 5: Tooling record — check supported HTTP methods before querying.
+
+    Tooling objects query against /services/data/vXX.0/tooling/query, not the
+    regular Data API. Many are read-only; check the methods first.
+    """
+    data = _load(TOOLING_DIR / 'ApexClass.json')
+    methods = data.get('supported_rest_api_http_methods', '')
+    field_names = list(data.get('fields', {}).keys())[:5]
+    print(f"ApexClass REST methods: {methods}")
+    print(f"First 5 ApexClass fields: {field_names}")
+    return methods
+
+
+if __name__ == '__main__':
+    print("Example 1: enterprise fields section")
+    load_fields_section()
+
+    print("\nExample 2: filterable fields (WHERE-safe)")
+    find_filterable_fields()
+
+    print("\nExample 3: relationship traversal")
+    traverse_relationship()
+
+    print("\nExample 4: fields vs field_reference (dual catalog)")
+    check_both_catalogs()
+
+    print("\nExample 5: Tooling API supported methods")
+    tooling_supported_methods()