Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Salesforce Data360 Lineage Impact

    1

    Trace Salesforce Data Cloud lineage from source contracts to activations to prevent downstream breakages.

    Free

    Security scanned
    Salesforce Data360 Lineage Impact

    Salesforce Data360 Lineage Impact

    Example session with this skill installed

    Trace the impact of changing the 'Loyalty_Tier__c' field type from String to Integer in the 'Customer_API' source stream.

    • Read your context and instructions
    • Compiled the salesforce data360 lineage

    I have traced the lineage for Loyalty_Tier__c from the Customer_API source through to all downstream activations. The change from String to Integer creates a type mismatch in two Calculated Insights and one Identity Resolution ruleset.

    Lineage & Impact Analysis: Loyalty_Tier__c

    Edge IDSource ObjectDestination ObjectEdge TypeExpression/JoinStatusImpact
    E-001Customer_APIDLO_Loyalty_DataDirect MapLoyalty_Tier__cDeployedType Mismatch
    E-002DLO_Loyalty_DataDMO_IndividualRelationshipIndividualIdActiveNone
    E-003DMO_IndividualCI_Member_ValueTransformationAVG(Loyalty_Tier)ActiveBroken Formula
    E-004DMO_IndividualIR_Ruleset_MainMatch RuleExact(Loyalty_Tier)ActiveLogic Failure
    E-005CI_Member_ValueSeg_High_ValueSegmentMember_Value > 500ActiveData Stale

    Observed Gaps & Risks

    Identity Resolution: The IR_Ruleset_Main uses this field for exact matching. Converting to Integer may cause match failures if the source sends leading zeros or non-numeric characters.

    Calculated Insight: CI_Member_Value expects a numeric input for AVG(). The current DLO mapping is set to Text; a deployment error will occur unless the DLO schema is updated first.

    • Activation: The Email_Marketing_Target expects the legacy String format.

    Next steps

    1. Update DLO_Loyalty_Data schema to Integer before deploying source changes.
    2. Refactor CI_Member_Value to handle the new numeric grain.
    3. Run $data360-refresh-orchestration for the DLO_Loyalty_Data stream to re-sync historical values.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Salesforce Data Cloud implementations often break because field changes in the source contract ripple silently through complex DLO to DMO mappings. This skill maps every hop from source API to final activation to ensure schema changes don't crash segments or downstream systems.

    What it does

    • Lineage mapping traces fields across streams, Data Lake Objects, Data Model Objects, and Calculated Insights.
    • Impact analysis identifies downstream consumers like segments and activations affected by schema or logic changes.
    • Gap detection compares project manifests against live org configurations to find unverified edges.
    • Root cause tracing traverses upstream from null or duplicated values to find the first broken transformation.
    • Test scope definition generates a minimal set of refresh actions and quality checks for the affected subgraph.

    How it works

    1. Name a specific asset or field to trace its path across the Data 360 landscape.
    2. Review the directed graph of edges, including join keys, expressions, and data types.
    3. Analyze the impact report for proposed changes, identifying potential breakages in identity resolution or CI grains.
    4. Execute ordered checks to verify live mappings against intended project contracts.

    Frameworks & tools

    This skill works with Salesforce Data Cloud (Data 360), including DLO, DMO, Calculated Insights, Identity Resolution rulesets, and Activation targets.

    Why this beats prompting it yourself

    Generic prompts fail to distinguish between a manifest entry and a live mapping. This skill enforces a strict evidence-backed approach that treats formulas and many-to-one resolutions as transformations rather than direct copies, preventing false positives in lineage reports.

    Use cases

    • Map the downstream impact of a source system schema change.
    • Verify that a Data Model Object field is correctly populated from the source contract.
    • Plan the safe retirement of a legacy data stream without breaking active segments.
    • Troubleshoot why a Calculated Insight is producing null values.

    Known limitations

    Requires access to project contracts and manifests. Does not execute deletions or replacements automatically; it flags them for manual scope review.

    Requires project contracts/manifests. Does not auto-execute deletions. Best paired with refresh orchestration and data quality skills for full automation.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 5 days ago

    • Free with an Agensi account

    Requires

    Salesforce
    Node.js
    Salesforce CLI

    Permissions

    Read Files
    Environment Variables
    Network Access
    Write Files
    Terminal / Shell

    Allowed Hosts

    login.salesforce.com
    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This skill provides full visibility into the Salesforce Data Cloud 'hop' sequence—from source DLOs through DMO mappings and Identity Resolution—allowing you to predict exactly how a field change will break downstream segments or activations before you hit 'save'.

    The skill requires read-access to your Salesforce Data Cloud environment metadata and your project's data contracts or manifests to compare live configurations against your intended design.

    Unlike general AI prompts, this skill understands the specific logic of Calculated Insights and many-to-one mapping rules, treating them as complex transformations rather than simple data copies to ensure 100% lineage accuracy.

    You receive the data360 lineage impact skill, a guide for integrating it with your AI agent, and a template for structuring your data contracts to ensure the most accurate gap detection.

    Yes, the skill is designed to analyze the entire Data 360 landscape, making it ideal for auditing legacy streams and identifying which specific dependencies can be safely removed without crashing active downstream systems.

    New in Data & Databases