Semantic Analyst
sidequery/sidemantic
Answer analytical, KPI, metric, trend, cohort, and business-performance questions through a Sidemantic semantic layer.
Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the…
Install Debug Failed Run
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add activepieces/activepieces --skill debug-failed-run -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install activepieces/activepieces debug-failed-run --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/debug-failed-run .claude/skills/debug-failed-run && rm -rf skills-srcUse ~/.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/
Install the "debug-failed-run" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-run into .claude/skills/debug-failed-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-failed-run", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-runType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add activepieces/activepieces --skill debug-failed-run -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install activepieces/activepieces debug-failed-run --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/debug-failed-run .agents/skills/debug-failed-run && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debug-failed-run" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-run into .agents/skills/debug-failed-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-failed-run", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add activepieces/activepieces --skill debug-failed-run -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install activepieces/activepieces debug-failed-run --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/debug-failed-run .cursor/skills/debug-failed-run && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debug-failed-run" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-run into .cursor/skills/debug-failed-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-failed-run", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/activepieces/activepieces.git --path .agents/skills/debug-failed-run--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add activepieces/activepieces --skill debug-failed-run -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install activepieces/activepieces debug-failed-run --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/debug-failed-run .gemini/skills/debug-failed-run && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debug-failed-run" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-run into .gemini/skills/debug-failed-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-failed-run", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install activepieces/activepieces debug-failed-runInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add activepieces/activepieces --skill debug-failed-run -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/debug-failed-run .github/skills/debug-failed-run && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debug-failed-run" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-run into .github/skills/debug-failed-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-failed-run", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add activepieces/activepieces --skill debug-failed-run -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install activepieces/activepieces debug-failed-run --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/activepieces/activepieces.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/debug-failed-run .opencode/skills/debug-failed-run && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debug-failed-run" agent skill from https://github.com/activepieces/activepieces/tree/main/.agents/skills/debug-failed-run into .opencode/skills/debug-failed-run/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debug-failed-run", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debug-failed-run- GitHub stars
- 25k
- Token cost
- ~3.7k tokens
- SKILL.md length
- 1,889 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the…
- Works in 5 steps: Pull the job/run report (SSH) → Correlate with ClickHouse logs… → Trace the failure into this repo → …
- Tasks that involve MCP servers
- SKILL.md covers Inputs, Step 1 — Pull the job/run…, Step 2 — Correlate with… and Step 3 — Trace the failure…, plus 3 more sections
- Calls ssh, node and docker
What it does
Debug Failed Run is an agent skill from activepieces/activepieces. Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the centralized ClickHouse logs (ClickStack MCP), and the code in this repo, then categorize the failed-job backlog on request.
Its SKILL.md is about 3.7k 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, covering MCP servers, Data warehousing and Workflow automation. It works with Model Context Protocol, ClickHouse and PostgreSQL. The repository describes itself as: AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents.
When your agent uses it
- Tasks that involve MCP servers
- Tasks that involve Data warehousing
- Tasks that involve Workflow automation
Example prompts
- “/debug-failed-run”
Requirements
- Docker
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Pull the job/run report (SSH)
- Correlate with ClickHouse logs (ClickStack MCP)
- Trace the failure into this repo
- Aggregate the failed backlog (only when asked)
- When the fault is on a worker's disk, not in the job
What it can do on your machine
Read from SKILL.md and the folder at commit 566f00e. 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:
sshnodedockerbun
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use ssh and docker, which can reach the network depending on how they are called.
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
Debug Failed Run loads about 3.7k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 1,889 words of instructions outside code blocks.
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: warnings
The automated check found patterns that need a careful read before installing.
- WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:16
read it from their local SSH config / `~/.ssh/config` alias) — never assume one. The examples below use `<host>` as a p - NoteMentions a .env fileSKILL.md:23
dis, Postgres, S3) the server uses, via `.env`. Run with plain `node` (matches how the box invokes them):
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,889 words (~3,726 tokens).
“Investigate why a flow run failed by combining two sources of truth:”
- name
- debug-failed-run
Files
Just SKILL.md in .agents/skills/debug-failed-run of activepieces/activepieces.
Open the folder on GitHubat commit 566f00e
Compare with similar skills
Debug Failed Run 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debug Failed Run this skillactivepieces/activepieces | 25k | — | ~3.7k | Automated safety check: Warn | Custom licence | |
| Semantic Analystsidequery/sidemantic | 129 | — | ~982 | Automated safety check: Pass | AGPL-3.0 | |
| Pytorch Clickhousepytorch/test-infra | 113 | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Moraine Sandbox QAeric-tramel/moraine | 117 | — | ~668 | Automated safety check: Pass | Apache-2.0 | |
| Triaging Warehouse Sync TicketsPostHog/posthog | 40k | — | ~6.3k | Automated safety check: Warn | Custom licence | |
| Use Gfs MCPGuepard-Corp/gfs | 158 | — | ~4k | Automated safety check: Pass | MIT |
Similar skills
Pytorch Clickhouse
pytorch/test-infra
Load this FIRST whenever working with PyTorch CI data (any pytorch/ org repo), the torchci/HUD codebase, or the PyTorch HUD ClickHouse database.
Moraine Sandbox QA
eric-tramel/moraine
Run isolated Moraine dev sandbox validation. An agent skill from eric-tramel/moraine.
- Official
Triaging Warehouse Sync Tickets
PostHog/posthog
Debug a customer's data warehouse source, schema, or table from a support ticket, using PostHog's own production data.
Use Gfs MCP
Guepard-Corp/gfs
GFS MCP Server for AI agent integration. An agent skill from Guepard-Corp/gfs.
- Official
Clickhouse Logs Queries
supabase/supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint).
More from activepieces/activepieces
All 14 skills in this repoAnalyze Logs
activepieces/activepieces
Analyze application logs from the .evlog/logs/ directory. An agent skill from activepieces/activepieces.
Activepieces Design System
activepieces/activepieces
Design system for Activepieces (open-source AI automation platform, "open source replacement for Zapier").
Piece Builder
activepieces/activepieces
Build and edit Activepieces pieces (integrations) — creating new pieces, adding actions or triggers, or fixing bugs in existing ones.
Profile App Cpu
activepieces/activepieces
Find what is burning CPU in a live app container without restarting it: separate the JS thread from GC and libuv, open the V8 inspector in place with SIGUSR1, take a CPU profile over CDP, and…
Profile Worker Memory
activepieces/activepieces
Diagnose a worker that is growing memory or being OOM-killed: separate a JS-heap leak from native growth, take a V8 heap snapshot of a live worker in place (never uploading it), and walk the…
Triage Dependabot Alerts
activepieces/activepieces
Triage Dependabot dependency vulnerability alerts for the Activepieces repo — pull open alerts, dedupe to distinct (package, advisory), confirm the vulnerable package + API is actually used, and…
Related
Categories
Questions about Debug Failed Run
What does Debug Failed Run do?
Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the…. Debug Failed Run is an agent skill from activepieces/activepieces. Debug a failed Activepieces flow run end-to-end: given a flow run id (or BullMQ job id), find why it failed, cross-referencing the live BullMQ job + Postgres rows (SSH script on the DevOps box), the centralized ClickHouse logs (ClickStack MCP), and the code in this repo, then categorize the failed-job backlog on request.
When should I use Debug Failed Run?
Debug Failed Run fits situations like: tasks that involve MCP servers; tasks that involve Data warehousing; tasks that involve Workflow automation.
How do I install Debug Failed Run in Claude Code?
Run `npx skills add activepieces/activepieces --skill debug-failed-run -a claude-code`. Or copy the skill folder (.agents/skills/debug-failed-run in activepieces/activepieces) into .claude/skills/debug-failed-run in your project. Claude Code loads it when a task matches its description.
How do I install Debug Failed Run in Codex?
Run `npx skills add activepieces/activepieces --skill debug-failed-run -a codex`. Or copy the skill folder (.agents/skills/debug-failed-run in activepieces/activepieces) into .agents/skills/debug-failed-run in your project. Codex loads it when a task matches its description.
Can I use Debug Failed Run 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 activepieces/activepieces --skill debug-failed-run -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debug-failed-run, .gemini/skills/debug-failed-run, .github/skills/debug-failed-run and .opencode/skills/debug-failed-run in your project.
What does Debug Failed Run need to run?
Going by SKILL.md and its folder, Debug Failed Run needs the command-line tools its instructions call (ssh, node, docker and bun). Our summary lists: Docker.
Does Debug Failed Run access the network?
SKILL.md contains no URLs. Its commands use ssh and docker, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Debug Failed Run safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Debug Failed Run use?
Debug Failed Run has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Debug Failed Run use?
About 3.7k 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 Debug Failed Run?
Skills that share tags, products or a category with Debug Failed Run: Semantic Analyst (sidequery/sidemantic, 129 stars), Pytorch Clickhouse (pytorch/test-infra, 113 stars), Moraine Sandbox QA (eric-tramel/moraine, 117 stars) and Triaging Warehouse Sync Tickets (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debug Failed Run?
activepieces (a GitHub organization) maintains it in activepieces/activepieces, which has 24,961 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 9, 2026.
Source: activepieces/activepieces on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.