What problem does it solve? Building Salesforce OmniStudio document templates involves opaque token syntax, strict Extract/Transform ODT wiring, and silent failure modes (blank output, phantom rows, engine crashes) that are hard to diagnose without deep platform knowledge. ## Core Features & Use Cases - Template authoring and token mapping: Create and modify .docx templates with scalar, repeating-section, conditional, image, hyperlink, and rich-text tokens, then wire them to Extract and Transform OmniDataTransforms. - Lifecycle and generation automation: Use canonical docgen_template_* scripts to build templates, extract tokens, activate/deactivate, upload binaries, and run end-to-end generation smoke tests. - Troubleshooting and validation: Diagnose blank output, cartesian-product explosions, mixed-depth phantom rows, and dynamic image failures using live-verified engine behavior references and static lint/diff helpers. - Use Case: You need an invoice template that lists line items with per-product usage grants and a dynamic company logo; this skill guides the Extract hierarchy, Transform formulas, IMG_ token contract, and verification pipeline. ## Quick Start Ask the agent to create a Salesforce OmniStudio invoice .docx template wired to Extract and Transform ODTs and verify it with an end-to-end generation test.