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

Pipeline Diagnose

by bruin-data in bruin-data/bruin

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

Apache-2.0Auto-check passedDatabases

Install Pipeline Diagnose

skills CLI
$ npx skills add bruin-data/bruin --skill pipeline-diagnose -a claude-code

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

GitHub CLI
$ gh skill install bruin-data/bruin pipeline-diagnose --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/pipeline-diagnose .claude/skills/pipeline-diagnose && 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
pipeline-diagnose
GitHub stars
1.8k
Token cost
~1k tokens
SKILL.md length
595 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 pipeline, asset, or command fails and the cause is not yet clear.

  • A Bruin pipeline
  • 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
  • Command fails and the cause is not yet clear

What it does

Pipeline Diagnose is an agent skill from bruin-data/bruin. Use when a Bruin pipeline, asset, or command fails and the cause is not yet clear.

Its SKILL.md is about 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. 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 pipeline
  • Command fails and the cause is not yet clear

Example prompts

  • “/pipeline-diagnose”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit d56f9d3. 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

Pipeline Diagnose loads about 1k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 595 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~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 d56f9d3, republished under its Apache-2.0 licence (© bruin-data). 595 words, ~1,046 tokens.

Download SKILL.mdSave it as .claude/skills/pipeline-diagnose/SKILL.md (or your agent's skills folder).
name
pipeline-diagnose
description
Use when a Bruin pipeline, asset, or command fails and the cause is not yet clear.
connections
bruin, github

Pipeline Diagnose

When to Use

Use this skill when a Bruin pipeline, asset, or command fails and the cause is not yet clear.

Inputs

  • Failing command and full error output.
  • Pipeline or asset path.
  • Environment name, if one was used.
  • Recent code or configuration changes, if known.

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, prefer bruin cloud runs diagnose --project-id <project-id> --pipeline <pipeline-name> --latest, bruin cloud runs get --project-id <project-id> --run-id <run-id>, bruin cloud instances logs --project-id <project-id> --run-id <run-id> --asset <asset-name>, and bruin cloud instances failed-logs --project-id <project-id> --run-id <run-id> for logs and run context.
  • In local development, inspect terminal output and the local logs/ folder, especially logs/runs, query logs, and export logs when they exist. Create local runs with bruin run <path> rather than Bruin Cloud run commands.
  • 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 and action mechanism before using it to read logs or trigger changes.

Context to Gather

  • Run bruin validate <path> for the affected pipeline or asset.
  • Check pipeline.yml, asset definitions, and connection names referenced by the failing task.
  • Inspect recent logs, stack traces, and changed files.
  • Use Bruin MCP docs tools or bruin <command> --help to confirm the current command syntax before running Cloud or local CLI commands.
  • Confirm whether the failure is parse-time, compile-time, connection-time, or execution-time.
Show full SKILL.md (264 more words)Show less

Data Failure Investigation

  • If the failure is caused by bad data and there are bronze, silver, gold, or other tiers, start at the asset where the problem appears and trace upstream through lineage one asset at a time.
  • Find one specific failing row, key, partition, or timestamp first, then keep every upstream query filtered to that instance.
  • Query the filtered instance in upstream assets until you find the first asset where the problem appears.
  • Once the first bad asset is identified, read its SQL query or Python script and isolate the specific function, join, filter, cast, incremental condition, or transformation step that likely caused the problem.
  • If the user has allowed fixes, change only that specific logic, then run the smallest asset-level validation in dev or shadow first. Recheck the same failing instance after the fix; only after that passes, run the broader failing command or check.

Decision Tree

  • If validation fails, fix the configuration or asset definition first.
  • If the connection is missing or invalid, report the missing connection and required fields.
  • If rendering fails, inspect Jinja variables, macros, and included files.
  • If execution fails after rendering, isolate the failing query or script and summarize the warehouse/runtime error.

Actions

Define repository-specific actions here. Until customized, this skill must report findings and stop before modifying data, source systems, or repo files.

Verification

  • Re-run the smallest failing command.
  • Run bruin validate <path> when files were changed.
  • Capture the final command output or remaining error.

Output

Return a concise diagnosis with:

  • Root cause or strongest hypothesis.
  • Evidence used.
  • Recommended next action.
  • Commands run and their result.

© 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/pipeline-diagnose of bruin-data/bruin.

Open the folder on GitHubat commit d56f9d3

Compare with similar skills

Pipeline Diagnose 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.

Pipeline Diagnose compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Pipeline Diagnose this skillbruin-data/bruin1.8k—~1kAutomated safety check: PassApache-2.0
Code Implementationapache/shardingsphere21k—~1.2kAutomated safety check: PassApache-2.0
Implement Commandredis/node-redis18k—~5kAutomated safety check: PassMIT
Clickhouse IohellangleZ/burn-in-cceverywhere-ralph11214 repos~2.5kAutomated safety check: PassNone
Basincloudflare/skills3k2 repos~684Automated safety check: PassApache-2.0
Analyzing Dataastronomer/agents451—~1.3kAutomated safety check: PassApache-2.0

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

  • Implement Command

    redis/node-redis

    Official

    Add a new Redis command (or command variant) to node-redis end-to-end — the <NAME.ts Command file, its registration with JSDoc in the package commands/index.ts, and a co-located <NAME.spec.ts with…

    18k GitHub stars~5k tokensUpdated yesterday
    DatabasesAuto-check passed

  • Clickhouse Io

    hellangleZ/burn-in-cceverywhere-ralph

    ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.

    112 GitHub starsUsed in 14 repos~2.5k tokens
    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 2 days ago
    DatabasesAuto-check passed

  • Migration Helper

    waynesutton/markdown-site

    Plan and execute Convex schema migrations safely, including adding fields, creating tables, and data transformations.

    627 GitHub starsUsed in 1 repo~958 tokens
    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

  • Schema Drift Check

    bruin-data/bruin

    A skill your agent uses when a pipeline fails because source, destination, or declared asset columns may have changed.

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

Categories

Questions about Pipeline Diagnose

What does Pipeline Diagnose do?

A skill your agent uses when a Bruin pipeline, asset, or command fails and the cause is not yet clear. Pipeline Diagnose is an agent skill from bruin-data/bruin. Use when a Bruin pipeline, asset, or command fails and the cause is not yet clear.

When should I use Pipeline Diagnose?

Pipeline Diagnose fits situations like: A Bruin pipeline; command fails and the cause is not yet clear.

How do I install Pipeline Diagnose in Claude Code?

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

How do I install Pipeline Diagnose in Codex?

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

Can I use Pipeline Diagnose 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 pipeline-diagnose -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pipeline-diagnose, .gemini/skills/pipeline-diagnose, .github/skills/pipeline-diagnose and .opencode/skills/pipeline-diagnose in your project.

What does Pipeline Diagnose need to run?

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

Does Pipeline Diagnose 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 Pipeline Diagnose 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 Pipeline Diagnose use?

Pipeline Diagnose 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 Pipeline Diagnose use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Pipeline Diagnose?

Skills that share tags, products or a category with Pipeline Diagnose: Code Implementation (apache/shardingsphere, 21k stars), Implement Command (redis/node-redis, 18k stars), Clickhouse Io (hellangleZ/burn-in-cceverywhere-ralph, 112 stars) and Basin (cloudflare/skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Pipeline Diagnose?

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 9, 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.