Skip to content
TrustedSkillsbeta
Back to all skills

Debugging Dags

Checked
rory-data·vlatest·testing

Helps with data, debugging as part of testing, debugging, and quality assurance workflows.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add rory-data/copilot --skill debugging-dags -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

rory-data

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned rory-data/copilot at d56f8590b7.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 98 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps debug Directed Acyclic Graphs (DAGs), which are common in data processing pipelines. It identifies errors and inefficiencies within DAG structures, providing insights into potential bottlenecks or incorrect task ordering. The tool can analyze dependencies between tasks, pinpoint failing steps, and suggest improvements for optimized execution.

When to use it

  • You're encountering unexpected behavior or failures in a data pipeline represented as a DAG.
  • A data processing job is taking longer than expected, and you suspect inefficiencies within the DAG structure.
  • You need to understand the dependencies between tasks in a complex workflow to troubleshoot an issue.
  • You want to proactively identify potential problems in a newly designed or modified DAG.

Key capabilities

  • DAG analysis
  • Error identification
  • Dependency mapping
  • Performance bottleneck detection
  • Optimization suggestions

Example prompts

  • "Analyze this DAG and tell me why job X failed."
  • "Identify any performance bottlenecks in this data processing workflow."
  • "Show me the dependencies between task A and task C in this DAG."

Tips & gotchas

The skill requires a clear representation of the DAG, typically as a JSON or similar structured format. Ensure the input accurately reflects the intended workflow for reliable analysis.