Duplicate Investigate

When to Use

Use this skill when duplicate rows, unstable primary keys, repeated ingestion, or failed uniqueness checks appear in a Bruin asset.

Inputs

• Affected asset name or table.
• Key columns or uniqueness checks.
• Error output, sample duplicate keys, or row counts.

Operating Context

• These starter skills can be used by Bruin Cloud agents, local agents, and external assistants connected to Bruin Cloud.
• In Bruin Cloud, use Cloud CLI access when the agent has it enabled. Use the bruin cloud CLI when the assistant has shell access and a configured API key or .bruin.yml; use Bruin Cloud MCP only when the assistant is configured for MCP tool calls or does not have direct CLI access. If using the CLI, inspect failures with bruin cloud runs diagnose --project-id <project-id> --pipeline <pipeline-name> --latest, fetch failed logs with bruin cloud instances failed-logs --project-id <project-id> --run-id <run-id>, and inspect a specific asset with bruin cloud assets get --project-id <project-id> --pipeline <pipeline-name> --asset <asset-name>.
• In local development, inspect terminal output and the local logs/ folder, especially logs/runs, query logs, and export logs when they exist. Use bruin query with existing .bruin.yml connections for read-only duplicate checks.
• If investigation or fix verification requires running an asset or pipeline, prefer a dev or shadow environment. If none exists, ask whether to run in production or create temporary copies of the affected tables to reproduce and test the issue.
• For other agent runtimes or orchestrators, customize this skill with the correct log source, query mechanism, and action mechanism before using it.