skills.rest
Mossaka
MossakaCOMMUNITY
Explore all skills by this author →
Website𝕏@jiaxiao_zhouGitHub

debug-workflow

Diagnose GitHub Actions workflow failures by aggregating logs and MCP gateway status.

Updated Jan 14, 2026
Search Tags:#workflow#debugging#logs#audit#mcp#github-actions#tools
One-click install
npx skills add https://github.com/Mossaka/skills --skill debug-workflow-mossaka
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-workflow
Source: https://github.com/Mossaka/skills/tree/main/debug-workflow
Command: npx skills add https://github.com/Mossaka/skills --skill debug-workflow-mossaka

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams quickly diagnose why GitHub Actions workflows fail by aggregating logs, MCP gateway statuses, and tool availability in a single view.

Core Features & Use Cases

  • Audits workflow runs with detailed reports and error detection using gh aw tools.
  • Analyzes logs including agent-stdio.log and MCP gateway logs to identify root causes.
  • Detects common issues like DNS/mcp failures, OAuth warnings, and firewall blocks.

Quick Start

Run the quick scan on the target run logs to surface MCP, gateway, and firewall issues.

Frequently Asked Questions about debug-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I debug failed GitHub Actions workflows using MCP gateway logs?▼

To debug failed GitHub Actions workflows, you aggregate MCP gateway logs and agent-stdio.log to identify root causes like DNS failures, OAuth warnings, and firewall blocks. This process surfaces MCP connectivity issues in a single view for analysis.

How do I analyze agent-stdio.log to find the root cause of a workflow failure?▼

Analyzing agent-stdio.log involves parsing workflow run logs to detect specific errors like MCP connectivity drops or firewall restrictions. This log analysis identifies the exact failure point and generates a Markdown report for root-cause documentation.

What is the best way to document GitHub Actions workflow failures for root-cause analysis?▼

The best way to document workflow failures is by generating Markdown reports that aggregate logs, MCP gateway status, and tool availability. This provides a single view for root-cause analysis and tracks common issues like DNS failures and OAuth warnings.

Can I detect MCP connectivity and firewall issues from GitHub Actions run logs?▼

Yes, you can detect MCP connectivity and firewall issues from GitHub Actions run logs by running a quick scan on the target run. This audit checks gateway.md and firewall logs to surface common network failures and OAuth warnings.

Do I need specific log formats to troubleshoot MCP gateway status during a workflow run?▼

You need specific log formats like agent-stdio.log and gateway.md to troubleshoot MCP gateway status during a workflow run. Parsing these logs allows you to detect tool availability issues and verify MCP connectivity.

Related Skills

Explore More Software Engineering Skills→
benzwickbenzwick

download-ci-artifacts

Download GitHub Actions CI artifacts using gh CLI commands.

Community
Intermediate
Xinm123Xinm123

systematic-debugging

Enforce root-cause investigation before applying fixes in debugging workflows.

Community
Basic
Cogni-AI-OUCogni-AI-OU
3

github-aw-troubleshooting

Audit GitHub Agentic Workflow runs and logs to diagnose failures.

Official
Advanced
fabnfabn
1

datadog:logs

Search and aggregate Datadog logs for a service, time range, and status level.

Community
Intermediate