Official agent skill

gh-aw Workflow Diagnosis

by github in github/gh-aw

Guides your agent through diagnosing failed GitHub Agentic Workflows by downloading run logs, auditing individual runs and reading the artifacts they leave behind.

OfficialMITAuto-check passedDevelopment

Install gh-aw Workflow Diagnosis

skills CLI
$ npx skills add github/gh-aw --skill debugging-workflows -a claude-code

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

GitHub CLI
$ gh skill install github/gh-aw debugging-workflows --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/github/gh-aw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/debugging-workflows .claude/skills/debugging-workflows && 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
debugging-workflows
GitHub stars
5.3k
Token cost
~3.9k tokens
SKILL.md length
1,063 words
Files
1
Skills in repo
52
Repo updated
First seen
Licence
MIT

At a glance

Guides your agent through diagnosing failed GitHub Agentic Workflows by downloading run logs, auditing individual runs and reading the artifacts they leave behind.

  • A gh-aw workflow run failed and you need to find the cause from its logs
  • SKILL.md covers Table of Contents, Quick Start, Downloading Workflow Logs and Auditing Specific Runs, plus 2 more sections
  • Calls gh and jq; reaches github.com
  • Auditing a single agentic workflow run by its run ID

What it does

This is an evidence and command reference for working out why a gh-aw workflow failed. The agent uses `gh aw logs` to pull artifacts and logs from GitHub Actions runs, with filters for date ranges and options for a JSON summary, and `gh aw audit` to examine one run by its ID.

It lists what each download contains: engine configuration in `aw_info.json`, the agent's final output in `safe_output.jsonl`, agent stdio logs, the git patch of changes made during the run, per-job Actions logs and a `summary.json` with metrics for all runs. The page defers to a separate shared debugging strategy for any reproduction, fix or live test, and says that diagnosis should never dispatch a run just to collect evidence.

When your agent uses it

  • A gh-aw workflow run failed and you need to find the cause from its logs
  • Auditing a single agentic workflow run by its run ID
  • Collecting recent failed runs across workflows to look for a pattern
  • Checking what an agent produced in a run, from its output file and patch

Example prompts

  • “Download the gh-aw logs from the past week and tell me which workflows keep failing.”
  • “Audit run 1234567890 and explain where the agent went wrong.”
  • “Why did the daily triage workflow produce an empty safe output? Check the artifacts.”
  • “Read the agent-stdio log from the latest failed run and summarize the error.”

Requirements

  • The GitHub CLI with the `gh aw` extension
  • Access to existing GitHub Actions run logs for the workflows

What it can do on your machine

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

    Shell commands in SKILL.md call:

    • gh
    • jq

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    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

gh-aw Workflow Diagnosis loads about 3.9k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 1,063 words of instructions outside code blocks.

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

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 github/gh-aw at commit eb63040, republished under its MIT licence (© github). 1,063 words, ~3,853 tokens.

Download SKILL.mdSave it as .claude/skills/debugging-workflows/SKILL.md (or your agent's skills folder).
name
debugging-workflows
description
Diagnose gh-aw failures using logs and audits; follow the shared strategy for patches and permitted active debug loops.

Workflow Diagnosis and Debugging Evidence

Use this reference to diagnose workflows: download/analyze existing logs, audit runs, and trace failures. These reads are not an active debug loop.

Follow the shared local-first strategy for all reproduction, fixes, uploads, and live tests. This page is an evidence and CLI reference, not a separate execution policy. Respect explicit no-dispatch contexts. Apply its live-outcome table, credential triage and untrusted-evidence rules. Without accessible existing logs, use source/fixtures; never dispatch for evidence.

Table of Contents

Quick Start

Download Logs from Recent Runs
bash
# Download logs from the last 24 hours
gh aw logs --start-date -1d -o .github/aw/logs/recent

# Download logs for a specific workflow
gh aw logs weekly-research --start-date -1d

# Download logs with JSON output for programmatic analysis
gh aw logs --json
Audit a Specific Run
bash
# Audit by run ID
gh aw audit 1234567890

# Audit from a GitHub Actions URL
gh aw audit https://github.com/owner/repo/actions/runs/1234567890

# Audit with JSON output
gh aw audit 1234567890 --json

Downloading Workflow Logs

The gh aw logs command downloads workflow run artifacts and logs from GitHub Actions for analysis.

Basic Usage
bash
# Download logs for all workflows (last 10 runs)
gh aw logs

# Download logs for a specific workflow
gh aw logs <workflow-name>

# Download with custom output directory
gh aw logs -o .github/aw/logs/custom
Filter Options
bash
# Filter by date range
gh aw logs --start-date 2024-01-01 --end-date 2024-01-31
gh aw logs --start-date -1w                    # Last week
gh aw logs --start-date -1mo                   # Last month

# Filter by AI engine
gh aw logs --engine copilot
gh aw logs --engine claude
gh aw logs --engine codex

# Filter by count
gh aw logs -c 5                                # Last 5 runs

# Filter by branch/tag
gh aw logs --ref main
gh aw logs --ref feature-xyz

# Filter by run ID range
gh aw logs --after-run-id 1000 --before-run-id 2000

# Filter firewall-enabled runs
gh aw logs --firewall                          # Only firewall-enabled
gh aw logs --no-firewall                       # Only non-firewall
Output Options
bash
# Generate JSON summary
gh aw logs --json

# Parse agent logs and generate Markdown reports
gh aw logs --parse

# Generate Mermaid tool sequence graph
gh aw logs --tool-graph

# Set download timeout
gh aw logs --timeout 300                       # 5 minute timeout
Downloaded Artifacts

When you run gh aw logs, the following artifacts are downloaded for each run:

FileDescription
aw_info.jsonEngine configuration and workflow metadata
safe_output.jsonlAgent's final output content (when non-empty)
agent_output/Agent logs directory
agent-stdio.logAgent standard output/error logs
aw.patchGit patch of changes made during execution
workflow-logs/GitHub Actions job logs (organized by job)
summary.jsonComplete metrics and run data for all runs
Example: Analyze Recent Failures
bash
# Download failed runs from last week
gh aw logs --start-date -1w -o .github/aw/logs/debug

# Check the summary for patterns
cat .github/aw/logs/debug/summary.json | jq '.runs[] | select(.conclusion == "failure")'

Auditing Specific Runs

The gh aw audit command investigates a single workflow run in detail, downloading artifacts, detecting errors, and generating a report.

Basic Usage
bash
# Audit by numeric run ID
gh aw audit 1234567890

# Audit from GitHub Actions URL
gh aw audit https://github.com/owner/repo/actions/runs/1234567890

# Audit from job URL (extracts first failing step)
gh aw audit https://github.com/owner/repo/actions/runs/1234567890/job/9876543210

# Audit from job URL with specific step
gh aw audit https://github.com/owner/repo/actions/runs/1234567890/job/9876543210#step:7:1
Output Options
bash
# JSON output for programmatic analysis
gh aw audit 1234567890 --json

# Custom output directory
gh aw audit 1234567890 -o ./audit-reports

# Parse agent logs and firewall logs
gh aw audit 1234567890 --parse

# Verbose output
gh aw audit 1234567890 -v
Check Whether an Error Recurs
bash
# Compare existing runs, without dispatching new ones
gh aw audit 1234567890 1234567891 1234567892 --group --json

Use grouped per-run finding codes/counts, then cached individual reports/logs for exact signatures. Plain multi-run diffs focus on metrics/firewall/tools; absent findings or skipped runs do not prove the error disappeared. Match the first failing boundary and normalized error/tool/status signature across comparable workflows, revisions, triggers/inputs and configurations. Count each matching run once, report matching/inspectable runs and IDs, and keep missing evidence unknown. Repeated HTTP 403 alone does not establish one root cause.

Audit Report Contents

The audit command provides:

  • Error Detection: Errors and warnings from workflow logs
  • MCP Tool Usage: Statistics on tool calls by the AI agent
  • Missing Tools: Tools the agent tried to use but weren't available
  • Execution Metrics: Duration, token usage, and cost information
  • Safe Output Analysis: What GitHub operations were attempted
Example: Investigate a Failed Run
bash
# Get detailed audit report
gh aw audit 1234567890 --json > audit.json

# Extract key information
cat audit.json | jq '{
  status: .overview.status,
  conclusion: .overview.conclusion,
  errors: .errors,
  missing_tools: .missing_tools,
  tool_usage: .tool_usage
}'

How Agentic Workflows Work

Understanding the workflow architecture helps in debugging.

Workflow Structure

Agentic workflows use a markdown + YAML frontmatter format:

markdown
---
on:
  issues:
    types: [opened]
permissions:
  contents: read
timeout-minutes: 10
engine: copilot
tools:
  github:
    mode: remote
    toolsets: [default]
safe-outputs:
  staged: true
  create-issue:
    labels: [ai-generated]
---

# Workflow Title

Natural language instructions for the AI agent.

Use GitHub context like ${{ github.event.issue.number }}.
Execution Flow
1. Trigger Event (issue opened, PR created, schedule, etc.)
     ↓
2. Activation Job
   - Validates permissions
   - Processes mcp-scripts
   - Sanitizes context
     ↓
3. AI Agent Job
   - Loads MCP servers and tools
   - Executes AI agent with prompt
   - Agent makes tool calls
   - Agent produces output
     ↓
4. Safe Outputs Job
   - Processes agent output
   - Creates GitHub resources (issues, PRs, etc.)
   - Applies labels, comments
     ↓
5. Completion
   - Workflow summary generated
   - Artifacts uploaded
Key Components
ComponentPurposeConfiguration
EngineAI model to useengine: copilot, claude, codex
ToolsAPIs available to agenttools: section with MCP servers
MCP ScriptsContext passed to agentmcp-scripts: with GitHub expressions
Safe-OutputsResources agent can createsafe-outputs: with allowed operations
PermissionsGitHub token permissionspermissions: block
NetworkAllowed network accessnetwork: with domain/ecosystem lists
Compilation Process
bash
# Compile workflow to GitHub Actions YAML
gh aw compile <workflow-name>

# Result: .github/workflows/<name>.md → .github/workflows/<name>.lock.yml

The .lock.yml file is the actual GitHub Actions workflow that runs.

Common Issues and Solutions

Missing Tool Errors

Symptoms:

  • Error: "Tool 'github:read_issue' not found"
  • Agent cannot access GitHub APIs

Solution: Add GitHub MCP server configuration:

yaml
tools:
  github:
    mode: remote
    toolsets: [default]
Permission Errors

Symptoms:

  • HTTP 403 (Forbidden) errors
  • "Resource not accessible" errors

Solution: First distinguish SAML/token-source denial from missing permissions using the shared credential triage. Grant required read permissions to the agent and configure writes through safe outputs. Keep debugging outputs staged; inspect individual job/token permissions rather than adding write permissions to the agent:

yaml
permissions:
  contents: read
safe-outputs:
  staged: true
  create-issue: {}
Safe-Input Errors

Symptoms:

  • "missing tool configuration for mcpscripts-gh"
  • Environment variable not available

Solution: Configure mcp-scripts:

yaml
mcp-scripts:
  issue:
    script: |
      return { title: process.env.ISSUE_TITLE, body: process.env.ISSUE_BODY };
    env:
      ISSUE_TITLE: ${{ github.event.issue.title }}
      ISSUE_BODY: ${{ github.event.issue.body }}
Safe-Output Errors

Symptoms:

  • Agent tries to create resources but fails
  • "Safe output not enabled" errors

Solution: Enable safe-outputs:

yaml
safe-outputs:
  staged: true  # Preview safe outputs while debugging
  create-issue:
    labels: [ai-generated]
Show full SKILL.md (495 more words)Show less
Cascading Safe-Output Message Failures (Process Safe Outputs step)

Symptoms:

  • Process Safe Outputs reports multiple failed messages in one run
  • One failed update_pull_request message includes a 403 workflows-permission warning
  • Other failed messages (for example add_comment) include Bad credentials

What this means:

  • Do not assume all safe-output failures share one root cause.
  • A 403 workflows-permission error on update_pull_request can be expected/non-fatal in some workflows.
  • A 401-style Bad credentials error on other messages is a separate authentication failure that needs its own fix.

Diagnostic steps:

bash
# Summarize failed safe-output messages and types
gh aw audit <run-id>

# Include additional artifacts when diagnosis needs more context
gh aw audit <run-id> --artifacts usage,github-api,mcp,agent

# Escalate to full artifact collection for hard-to-classify failures
gh aw audit <run-id> --artifacts all

# Inspect full failing job logs to classify each message failure
gh run view <run-id> --job=<job-id> --log
  • Triage each failed message by its own HTTP status code and tool/action name.
  • Check permissions: for missing scopes when 403 errors appear.
  • Compare the "failed message count" against the individual failed message lines to confirm whether there are multiple independent failures.
  • If several credential failures cluster together in time, investigate token freshness/expiry and token source for the run.
Network Access Errors

Symptoms:

  • Firewall denials
  • URLs appearing as "(redacted)"

Solution: Configure network access:

yaml
network:
  allowed:
    - defaults
    - python    # For PyPI
    - node      # For npm
    - "api.example.com"  # Custom domains
Timeout Errors

Symptoms:

  • Workflow exceeds time limit
  • Agent loops or hangs

Solution: Increase timeout or optimize prompt:

yaml
timeout-minutes: 30  # Increase from default

Advanced Debugging Techniques

Polling In-Progress Runs

Classify command exit separately from workflow outcome. A nonzero audit exit may mean artifacts are not ready: confirm the same run with gh run view <run-id> --json status,headSha,conclusion, then poll within the approved interval/deadline. Audit/log permission denial blocks further live iteration; report evidence unavailable, not workflow failure. Follow the shared outcome table for dispatch timeouts and SHA mismatches; never redispatch for logs.

Inspecting MCP Configuration

Preflight declarations, startup effects and isolated test bindings using the shared strategy before commands that can start/connect servers.

bash
# Inspect MCP servers for a workflow
gh aw mcp inspect <workflow-name>

# List all workflows with MCP servers
gh aw mcp list
Checking Workflow Status
bash
# Show status of all agentic workflows
gh aw status
Downloading Specific Artifacts
bash
# Download only the agent log artifact
GH_REPO=owner/repo gh run download <run-id> -n agent-stdio.log
Inspecting Job Logs
bash
# View specific job logs
gh run view <run-id>
gh run view --job <job-id> --log
Analyzing Firewall Logs
bash
# Parse firewall logs for network issues
gh aw logs --parse

# Check firewall-enabled runs
gh aw logs --firewall
Diagnostic and Development Compilation
bash
# Strict/staged development compilation with checks and warnings as errors
gh aw compile <workflow> --dry-run

# Recommended when using a reviewed test environment
gh aw compile <workflow> --dry-run --environment gh-aw-debug

Reference Commands

Log Analysis Commands
CommandDescription
gh aw logsDownload logs for all workflows
gh aw logs <workflow>Download logs for specific workflow
gh aw logs --jsonOutput as JSON
gh aw logs --start-date -1dFilter by date
gh aw logs --engine copilotFilter by engine
gh aw logs --parseGenerate Markdown reports
Audit Commands
CommandDescription
gh aw audit <run-id>Audit specific run
gh aw audit <url>Audit from GitHub URL
gh aw audit <run-id> --jsonOutput as JSON
gh aw audit <run-id> --parseParse logs to Markdown
gh aw audit <id1> <id2> ... --group --jsonGroup existing-run findings for recurrence
MCP Commands
CommandDescription
gh aw mcp listList workflows with MCP servers
gh aw mcp inspect <workflow>Inspect MCP configuration
Status Commands
CommandDescription
gh aw statusShow all workflow status
gh aw compileCompile all workflows
gh aw compile <workflow>Compile specific workflow
gh aw compile <workflow> --dry-runEnforce shared development-testing checks
Active Debugging Commands (Permitted Contexts Only)
CommandDescription
gh aw run <workflow> --ref <reviewed-ref>Only after shared human-validation gates; explicit no-dispatch rules take precedence
gh run view <run-id> --json status,headSha,conclusionSame-run monitoring within approved bounds

Additional Resources

© github, MIT. 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 .github/skills/debugging-workflows of github/gh-aw.

Open the folder on GitHubat commit eb63040

Compare with similar skills

gh-aw Workflow Diagnosis 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.

gh-aw Workflow Diagnosis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
gh-aw Workflow Diagnosis this skillgithub/gh-aw5.3k—~3.9kAutomated safety check: PassMIT
GitHub Actions Failure Analysisykdojo/claude-code-tips10k—~639Automated safety check: PassCustom licence
CI/CD Failure Troubleshootingruby-git/ruby-git1.8k—~1.9kAutomated safety check: PassMIT
Debugging Workflowsgithub/gh-aw-firewall148—~2.7kAutomated safety check: NotesMIT
Authoring CI WorkflowsPostHog/posthog-foss721—~11kAutomated safety check: PassMIT
Megatron-LM CI Failure TriageNVIDIA/Megatron-LM18k—~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • GitHub Actions Failure Analysis

    ykdojo/claude-code-tips

    Investigates a failed GitHub Actions run from its URL: pinpoints the real failure, checks the job's history for flakiness, and finds the breaking commit and any existing fix PR.

    10k GitHub stars~639 tokensUpdated 12 days ago
    DevOps & CloudAuto-check passed
  • Diagnoses and fixes failing GitHub Actions runs by identifying the failure, fetching only the relevant logs, finding the root cause and reproducing it locally.

    1.8k GitHub stars~1.9k tokensUpdated 5 days ago
    DevOps & CloudAuto-check passed
  • Debugging Workflows

    github/gh-aw-firewall

    Official

    Debug GitHub Actions workflows by downloading logs, analyzing summaries, and understanding how agentic workflows and the AWF firewall work together.

    148 GitHub stars~2.7k tokensUpdated today
    DevelopmentAuto-check: notes
  • Authoring CI Workflows

    PostHog/posthog-foss

    Official

    A skill your agent uses when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action…

    721 GitHub stars~11k tokensUpdated today
    DevelopmentAuto-check passed
  • Official

    Investigates a failing GitHub Actions run or job for Megatron-LM, finds the root cause plus the PR and test author involved, and files a structured bug issue.

    18k GitHub stars~1.6k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Debugging CI Failures

    PostHog/posthog-foss

    Official

    Debugs failing GitHub Actions CI runs for PostHog PRs, commits, and branches, and answers broad CI-health questions ("is CI red?", "is master green today?", "what's broken right now?").

    721 GitHub stars~5.7k tokensUpdated today
    Testing & QAAuto-check passed

More from github/gh-aw

All 52 skills in this repo
  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.3k GitHub starsUsed in 23 repos~2.8k tokens
    Auto-check passed
  • Official

    Designs and verifies a deterministic grader that measures whether a GitHub Agentic Workflow run reached its real-world or repository outcome.

    5.3k GitHub stars~6.8k tokensUpdated today
    Auto-check passed
  • Official

    Scaffolds, edits, reloads and debugs a canvas extension that the GitHub Copilot CLI can open in its side panel.

    5.3k GitHub stars~3.7k tokensUpdated today
    Auto-check passed
  • Official

    Drives an open pull request to merge-ready from inside a GitHub Copilot cloud agent, resolving review threads and local checks concurrently, without merging or retriggering CI.

    5.3k GitHub stars~3.8k tokensUpdated today
    Auto-check: warnings
  • Official

    Bumps gh-aw's pinned gh-aw-firewall version, rebuilds generated artifacts, and flags upstream spec or schema changes that need follow-up work.

    5.3k GitHub stars~899 tokensUpdated today
    Auto-check passed
  • Official

    Guide to the console struct tag system in gh-aw: headers, titles, number and cost formats, omitempty, and how structs, slices and maps render in the terminal.

    5.3k GitHub stars~736 tokensUpdated today
    Auto-check passed

Questions about gh-aw Workflow Diagnosis

What does gh-aw Workflow Diagnosis do?

Guides your agent through diagnosing failed GitHub Agentic Workflows by downloading run logs, auditing individual runs and reading the artifacts they leave behind. This is an evidence and command reference for working out why a gh-aw workflow failed. The agent uses `gh aw logs` to pull artifacts and logs from GitHub Actions runs, with filters for date ranges and options for a JSON summary, and `gh aw audit` to examine one run by its ID.

When should I use gh-aw Workflow Diagnosis?

gh-aw Workflow Diagnosis fits situations like: A gh-aw workflow run failed and you need to find the cause from its logs; auditing a single agentic workflow run by its run ID; collecting recent failed runs across workflows to look for a pattern; checking what an agent produced in a run, from its output file and patch.

How do I install gh-aw Workflow Diagnosis in Claude Code?

Run `npx skills add github/gh-aw --skill debugging-workflows -a claude-code`. Or copy the skill folder (.github/skills/debugging-workflows in github/gh-aw) into .claude/skills/debugging-workflows in your project. Claude Code loads it when a task matches its description.

How do I install gh-aw Workflow Diagnosis in Codex?

Run `npx skills add github/gh-aw --skill debugging-workflows -a codex`. Or copy the skill folder (.github/skills/debugging-workflows in github/gh-aw) into .agents/skills/debugging-workflows in your project. Codex loads it when a task matches its description.

Can I use gh-aw Workflow Diagnosis 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 github/gh-aw --skill debugging-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-workflows, .gemini/skills/debugging-workflows, .github/skills/debugging-workflows and .opencode/skills/debugging-workflows in your project.

What does gh-aw Workflow Diagnosis need to run?

Going by SKILL.md and its folder, gh-aw Workflow Diagnosis needs the command-line tools its instructions call (gh and jq). Our summary lists: The GitHub CLI with the `gh aw` extension; Access to existing GitHub Actions run logs for the workflows.

Does gh-aw Workflow Diagnosis access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is gh-aw Workflow Diagnosis 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 gh-aw Workflow Diagnosis use?

gh-aw Workflow Diagnosis is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does gh-aw Workflow Diagnosis use?

About 3.9k tokens (SKILL.md is roughly 15k 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 gh-aw Workflow Diagnosis?

Skills that share tags, products or a category with gh-aw Workflow Diagnosis: GitHub Actions Failure Analysis (ykdojo/claude-code-tips, 10k stars), CI/CD Failure Troubleshooting (ruby-git/ruby-git, 1.8k stars), Debugging Workflows (github/gh-aw-firewall, 148 stars) and Authoring CI Workflows (PostHog/posthog-foss, 721 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains gh-aw Workflow Diagnosis?

github (a GitHub organization, an official publisher) maintains it in github/gh-aw, which has 5,350 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 7, 2026.

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