New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Quality Check Investigate

by bruin-data in bruin-data/bruin

A skill your agent uses when a Bruin quality check fails or starts warning unexpectedly.

Apache-2.0Auto-check passedDatabases

Install Quality Check Investigate

skills CLI
$ npx skills add bruin-data/bruin --skill quality-check-investigate -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install bruin-data/bruin quality-check-investigate --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/bruin-data/bruin.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/quality-check-investigate .claude/skills/quality-check-investigate && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
quality-check-investigate
GitHub stars
1.8k
Token cost
~1.1k tokens
SKILL.md length
613 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when a Bruin quality check fails or starts warning unexpectedly.

  • A Bruin quality check fails
  • SKILL.md covers When to Use, Inputs, Operating Context and Context to Gather, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Starts warning unexpectedly

What it does

Quality Check Investigate is an agent skill from bruin-data/bruin. Use when a Bruin quality check fails or starts warning unexpectedly.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Databases. It works with SQL. The repository describes itself as: Build data pipelines with SQL and Python, ingest data from different sources, add quality checks, and build end-to-end flows. The licence is Apache-2.0.

When your agent uses it

  • A Bruin quality check fails
  • Starts warning unexpectedly

Example prompts

  • “/quality-check-investigate”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 9b11390. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Quality Check Investigate loads about 1.1k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 613 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bruin-data/bruin at commit 9b11390, republished under its Apache-2.0 licence (© bruin-data). 613 words, ~1,075 tokens.

Download SKILL.mdSave it as .claude/skills/quality-check-investigate/SKILL.md (or your agent's skills folder).
name
quality-check-investigate
description
Use when a Bruin quality check fails or starts warning unexpectedly.
connections
bruin, github

Quality Check Investigate

When to Use

Use this skill when a Bruin quality check fails or starts warning unexpectedly.

Inputs

  • Affected asset and check name.
  • Check SQL or check definition.
  • Failure output and sample rows, if available.

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 an asset instance with bruin cloud instances get --project-id <project-id> --run-id <run-id> --asset <asset-name>, and fetch logs with bruin cloud instances logs --project-id <project-id> --run-id <run-id> --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 run --only checks <path> or a limited bruin query where appropriate.
  • 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 check-result source, log source, and action mechanism before using it.

Context to Gather

  • Inspect the asset definition and check configuration.
  • Determine whether the check tests completeness, uniqueness, freshness, accepted values, ranges, or custom SQL.
  • Compare recent upstream changes with the first failing run.
  • Sample failing rows only when it is safe and allowed by repository policy.
  • Use Bruin MCP docs tools or bruin <command> --help to confirm the current command syntax before running Cloud or local CLI commands.
Show full SKILL.md (294 more words)Show less

Lineage Investigation

  • Find one specific failing example first, then keep every upstream query filtered to that row, key, partition, or time window. Use the full failing set only after the specific example is understood.
  • If the data has bronze, silver, gold, or other tiers, start at the asset where the quality check fails and trace upstream through lineage one asset at a time.
  • Query the filtered example in each upstream asset until you find the first asset where the invalid value, missing row, duplicate, stale timestamp, or unexpected aggregate appears.
  • Once the first bad asset is identified, read its SQL query or Python script and isolate the specific calculation, join, filter, cast, window function, incremental condition, or Python function that likely caused the failure.
  • If the user has allowed fixes, change only that specific logic, then run the smallest asset-level or check-level validation in dev or shadow first. Recheck the same failing example after the fix; only after that passes, run the full quality check.

Decision Tree

  • If the check definition is wrong, identify the intended rule and affected files.
  • If the data violates a valid rule, locate the upstream source or transformation that introduced it.
  • If the threshold is outdated, document why the threshold changed and who should approve it.
  • If the check is flaky, inspect nondeterministic ordering, time windows, and incremental logic.

Actions

Define repository-specific actions here. Until customized, this skill must report findings and stop before changing thresholds, deleting rows, or modifying data.

Verification

  • Re-run the failed quality check or the smallest equivalent query.
  • Re-run bruin validate <path> if files were changed.
  • Confirm whether failing row counts and examples match the diagnosis.

Output

Return:

  • Failed rule.
  • Evidence and sample pattern.
  • Root cause or strongest hypothesis.
  • Recommended fix.
  • Verification commands and results.

© bruin-data, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/quality-check-investigate of bruin-data/bruin.

Open the folder on GitHubat commit 9b11390

Compare with similar skills

Quality Check Investigate next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Quality Check Investigate compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Quality Check Investigate this skillbruin-data/bruin1.8k—~1.1kAutomated safety check: PassApache-2.0
Code Implementationapache/shardingsphere21k—~1.2kAutomated safety check: PassApache-2.0
Basincloudflare/skills3k2 repos~684Automated safety check: PassApache-2.0
Analyzing Dataastronomer/agents451—~1.3kAutomated safety check: PassApache-2.0
VisualizationFrankChen021/datastoria327—~1.2kAutomated safety check: PassCustom licence
Databricks Dbsqldatabricks/databricks-agent-skills3451 repos~2.8kAutomated safety check: PassCustom licence

Similar skills

  • Code Implementation

    apache/shardingsphere

    Implement, fix, refactor, or remove repository code under required scope, non-regression, verification, and review gates.

    21k GitHub stars~1.2k tokensUpdated today
    DatabasesAuto-check passed

  • Basin

    cloudflare/skills

    Official

    Build and troubleshoot Cloudflare Basin analytics workflows with Basin Pipelines, Basin Catalog, and Basin SQL.

    3k GitHub starsUsed in 2 repos~684 tokens
    DatabasesAuto-check passed

  • Analyzing Data

    astronomer/agents

    Queries the data warehouse with SQL and answers business questions about data.

    451 GitHub stars~1.3k tokensUpdated 3 days ago
    DatabasesAuto-check passed

  • Visualization

    FrankChen021/datastoria

    Rules for charts and visualization. An agent skill from FrankChen021/datastoria.

    327 GitHub stars~1.2k tokensUpdated 2 mo ago
    DatabasesAuto-check passed

  • Databricks Dbsql

    databricks/databricks-agent-skills

    Official

    Databricks SQL (DBSQL) advanced features and SQL warehouse capabilities.

    345 GitHub starsUsed in 1 repo~2.8k tokens
    DatabasesAuto-check passed

  • Rocky Dsl Change

    rocky-data/rocky

    Rocky DSL (.rocky file) cross-subproject cascade. An agent skill from rocky-data/rocky.

    304 GitHub stars~1.3k tokensUpdated yesterday
    DatabasesAuto-check passed

More from bruin-data/bruin

All 10 skills in this repo

  • Record Vhs Demo

    bruin-data/bruin

    Create, update, render, and visually verify polished Bruin CLI terminal demos with VHS.

    1.8k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Add Ingestr Source

    bruin-data/bruin

    Add Bruin CLI support for a new ingestr source. An agent skill from bruin-data/bruin.

    1.8k GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • Bruin Semantic Layer

    bruin-data/bruin

    A skill your agent uses when creating, editing, reviewing, or troubleshooting Bruin semantic layer models, semantic query CLI usage, metric and dimension definitions, joins, segments, filters…

    1.8k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Create Dashboard

    bruin-data/bruin

    Create DAC dashboards by writing YAML or TSX dashboard definition files.

    1.8k GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Duplicate Investigate

    bruin-data/bruin

    A skill your agent uses when duplicate rows, unstable primary keys, repeated ingestion, or failed uniqueness checks appear in a Bruin asset.

    1.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed

  • Pipeline Diagnose

    bruin-data/bruin

    A skill your agent uses when a Bruin pipeline, asset, or command fails and the cause is not yet clear.

    1.8k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Quality Check Investigate

What does Quality Check Investigate do?

A skill your agent uses when a Bruin quality check fails or starts warning unexpectedly. Quality Check Investigate is an agent skill from bruin-data/bruin. Use when a Bruin quality check fails or starts warning unexpectedly.

When should I use Quality Check Investigate?

Quality Check Investigate fits situations like: A Bruin quality check fails; starts warning unexpectedly.

How do I install Quality Check Investigate in Claude Code?

Run `npx skills add bruin-data/bruin --skill quality-check-investigate -a claude-code`. Or copy the skill folder (skills/quality-check-investigate in bruin-data/bruin) into .claude/skills/quality-check-investigate in your project. Claude Code loads it when a task matches its description.

How do I install Quality Check Investigate in Codex?

Run `npx skills add bruin-data/bruin --skill quality-check-investigate -a codex`. Or copy the skill folder (skills/quality-check-investigate in bruin-data/bruin) into .agents/skills/quality-check-investigate in your project. Codex loads it when a task matches its description.

Can I use Quality Check Investigate in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bruin-data/bruin --skill quality-check-investigate -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/quality-check-investigate, .gemini/skills/quality-check-investigate, .github/skills/quality-check-investigate and .opencode/skills/quality-check-investigate in your project.

What does Quality Check Investigate need to run?

SKILL.md names no scripts, command-line tools or credentials: Quality Check Investigate is instructions for the agent only. Our summary lists: Python 3.

Does Quality Check Investigate access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Quality Check Investigate safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Quality Check Investigate use?

Quality Check Investigate is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Quality Check Investigate use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Quality Check Investigate?

Skills that share tags, products or a category with Quality Check Investigate: Code Implementation (apache/shardingsphere, 21k stars), Basin (cloudflare/skills, 3k stars), Analyzing Data (astronomer/agents, 451 stars) and Visualization (FrankChen021/datastoria, 327 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Quality Check Investigate?

bruin-data (a GitHub organization) maintains it in bruin-data/bruin, which has 1,777 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 10, 2026.

Source: bruin-data/bruin on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.