
Product
Introducing Socket Scanning for VS Code Marketplace Extensions
Socket now scans VS Code extensions, giving teams early detection of risky behaviors, hidden capabilities, and supply chain threats in developer tools.
@htekdev/actions-debugger
Advanced tools
65+ real GitHub Actions errors, queryable by agents. MCP server + Copilot skills + error database.
65+ real GitHub Actions errors, queryable by agents. MCP server + Copilot skills + error database.
Stop debugging the same CI failures over and over. This repo packages 65+ real-world GitHub Actions error scenarios — with regex-matchable patterns, root causes, and copy-paste fixes — into formats that both humans and AI agents can consume.
errors/ → Structured YAML error database (65+ entries)
src/ → MCP server (TypeScript + @modelcontextprotocol/sdk)
.github/skills/ → Copilot CLI skills for CI debugging
.github/agents/ → Copilot agent definition
npx @htekdev/actions-debugger
Add to your MCP client config:
{
"mcpServers": {
"actions-debugger": {
"command": "npx",
"args": ["@htekdev/actions-debugger"]
}
}
}
Client config locations:
~/Library/Application Support/Claude/claude_desktop_config.json (macOS) / %APPDATA%\Claude\claude_desktop_config.json (Windows).cursor/mcp.json (project) or ~/.cursor/mcp.json (global).vscode/mcp.json.github/mcp.json (repo-level)~/.codeium/windsurf/mcp_config.jsonCopy .github/skills/actions-debugging/SKILL.md to your repo's .github/skills/ directory. Reference it in your agent:
> **Skill reference:** For CI debugging, use the `actions-debugging` skill.
import { loadErrorDatabase, lookupError, diagnoseWorkflow } from "@htekdev/actions-debugger";
const db = await loadErrorDatabase();
// Lookup by error message
const matches = lookupError(db, "Permission to org/repo.git denied");
console.log(matches[0].fix);
// Analyze a workflow
const issues = diagnoseWorkflow(db, workflowYamlString);
| Tool | Description |
|---|---|
lookup_error | Match an error message against 65+ known issues |
diagnose_workflow | Static analysis of workflow YAML for common mistakes |
suggest_fix | Contextual fix suggestions from error context |
search_errors | Full-text search by keyword, category, severity |
list_categories | Browse error categories with counts |
| Category | Description |
|---|---|
yaml-syntax | YAML validation, key typos, expression errors |
silent-failures | No error shown, but wrong behavior |
runner-environment | Runner issues, disk space, Docker, PATH |
permissions-auth | GITHUB_TOKEN, OIDC, secrets, 403s |
caching-artifacts | Cache misses, artifact v4 changes, corruption |
triggers | Workflow not running, cron issues, dispatch |
concurrency-timing | Job cancellation, matrix, timeouts |
known-unsolved | Platform limitations with no fix |
See CONTRIBUTING.md for how to add new error entries. It's easy:
errors/{category}/ directoryerrors/_schema.jsonAll error scenarios sourced from: The Definitive GitHub Actions Debugging Guide
MIT — Hector Flores (htekdev)
FAQs
65+ real GitHub Actions errors, queryable by agents. CLI + MCP server + Copilot skills + error database.
The npm package @htekdev/actions-debugger receives a total of 14 weekly downloads. As such, @htekdev/actions-debugger popularity was classified as not popular.
We found that @htekdev/actions-debugger demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.

Product
Socket now scans VS Code extensions, giving teams early detection of risky behaviors, hidden capabilities, and supply chain threats in developer tools.

Research
/Security News
Socket uncovered two malicious VS Code themes in a GlassWorm-linked cluster with thousands of installs across VS Code Marketplace and Open VSX.

Security News
/Company News
Capital One is partnering with Socket to proactively secure its open source supply chain.