Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Salesforce Data360 Data Quality

    1

    Audit Salesforce Data Cloud (Data 360) ingestion and DMO integrity with evidence-based reconciliation and drift detection.

    Free

    Security scanned
    Salesforce Data360 Data Quality

    Salesforce Data360 Data Quality

    Example session with this skill installed

    Audit the 'Sales_Order_Stream' in the 'Production' data space. Reconcile the S3 source counts against the 'SalesOrder_DMO' for the latest run.

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

    I have completed the data quality audit for the Sales_Order_Stream ingestion pipeline. The audit identified a 2.4% record loss during the transformation layer from DLO to DMO.

    Data Quality Audit Report

    Check IDAsset NameGrainThresholdObservedResultMethod / Query
    DQ-001Sales_Order_S3Source100%50,000PASSSELECT COUNT(*) FROM S3_Manifest
    DQ-002Sales_Order_DLOIngestion>99.9%49,985PASS15 records in Problem DLO (Error: 403)
    DQ-003SalesOrder_DMOModeled±0%48,800FAILSELECT COUNT(*) FROM SalesOrder_DMO
    DQ-004SalesOrder_DMOPK Uniqueness0 Duplicates0PASSGROUP BY PrimaryKey HAVING COUNT > 1
    DQ-005SalesOrder_DMOFreshness< 4h6.2hFAILMAX(DataSourceObjectRefreshDate)

    Findings Summary

    Source to DLO: Minimal loss (15 records). Problem DLO indicates Type Mismatch on the TotalAmount field for these records.

    DLO to DMO: Significant variance of 1,185 records. Investigation of the mapping logic shows a JOIN filter on Account_ID is excluding records where the parent Account has not yet been ingested into the Individual DMO.

    • Freshness: The latest refresh exceeded the 4-hour threshold due to a delay in the upstream S3 file arrival.

    Next steps

    1. Update the TotalAmount field mapping to handle scientific notation found in source files.
    2. Review the Account_ID relationship requirements; consider changing the join to a LEFT JOIN or adjusting the ingestion sequence.
    3. Trigger a manual refresh of the SalesOrder_DMO once the parent Account records are processed.

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

    About this skill

    Data quality issues in Salesforce Data Cloud often remain hidden until downstream consumers report broken dashboards or failed identity resolution. This skill provides a systematic framework for inspecting data integrity across the ingestion pipeline from Source to DMO.

    What it does

    • Schema Validation identifies drift in file and stream schemas, checking keys, event times, and refresh modes against approved contracts.
    • Error Analysis inspects Problem Record DLOs to group rejects by error code and field without exposing sensitive personal data.
    • Integrity Auditing detects null or duplicate primary keys, type/length non-conformance, and unexpected volume shifts.
    • Reconciliation traces record counts through filters, transforms, and one-to-many mappings to isolate actual data loss.
    • Relationship Mapping validates foreign keys after transformation to report orphan or ambiguous matches.

    How it works

    1. Initialize by reviewing the project's data contract and recent run history to establish thresholds.
    2. Execute Queries against Source, DLO, and DMO layers to observe actual record states and refresh status.
    3. Trace Failures to the earliest possible layer in the pipeline where evidence of the issue exists.
    4. Report findings using the standard quality contract format, including environment and asset identifiers.

    Frameworks & tools

    This skill is designed for Salesforce Data Cloud (Data 360), focusing on Data Lake Objects (DLO), Data Model Objects (DMO), and ingestion streams.

    Why this beats prompting it yourself

    Generic prompts often miss the nuances of Data Cloud's multi-layer architecture, such as accounting for upsert logic during reconciliation. This skill enforces strict evidence-based reporting, preventing the agent from assuming an "Active" status implies successful record processing.

    Use cases

    • Ingestion Debugging find why specific records are landing in the Problem Record DLO.
    • Schema Drift Detection verify if source system changes broke the stream mapping.
    • Integrity Cleanup identify orphan DMO records before running identity resolution.
    • Audit Reporting generate a reconciliation report for a specific data space or run.

    Known limitations

    Does not perform automated repairs; findings must be routed to owners via governance protocols. Requires existing access to Data Cloud query interfaces.

    Cannot perform automated remediation. Requires pre-existing query access to the Data Cloud environment. Evidence-based only; will not infer status for inaccessible assets.

    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
    Terminal / Shell
    Write Files
    Network Access
    Environment Variables

    Allowed Hosts

    login.salesforce.com
    Listed5 days ago

    What's inside

    Frequently Asked Questions

    This skill audits the entire pipeline from Source to Data Model Objects (DMO), specifically identifying schema drift, orphan records, and hidden ingestion errors that standard Salesforce status dashboards might overlook.

    No, the skill operates in a read-only capacity to detect and report issues; it provides the evidence-based reports necessary for your data engineering team to perform manual or automated remediation.

    You will need an AI agent platform with connectivity to your Salesforce instance and the appropriate permissions to execute queries against Data Lake Objects (DLO) and Data Model Objects (DMO).

    The skill focuses on 'Problem Record DLOs' to group rejects by error code and field, allowing the agent to diagnose failures without needing to extract or display sensitive PII.

    Each purchase includes the production-ready skill definition, a standardized data quality contract template for reporting, and a guide on establishing threshold baselines for your specific environment.

    Yes, the skill is designed to handle complex one-to-many mappings and upsert logic, ensuring record counts are reconciled accurately even when data is transformed between layers.

    New in Data & Databases