OpenLogi macOS Permissions Triage
AprilNEA/OpenLogi
Decides whether an OpenLogi device problem on macOS is a privacy-permission (TCC) problem, using agent log lines, and says which identity needs which grant.
Checks a failing Pilot executor against four known failure patterns from the v2.149.x fixes before the agent explores anything else.
Install Pilot Failure Triage
$ npx skills add qf-studio/pilot --skill pilot-debug -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qf-studio/pilot pilot-debug --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/qf-studio/pilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/pilot-debug .claude/skills/pilot-debug && 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 "pilot-debug" agent skill from https://github.com/qf-studio/pilot/tree/main/.claude/skills/pilot-debug into .claude/skills/pilot-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pilot-debug", 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/qf-studio/pilot/tree/main/.claude/skills/pilot-debugType 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 qf-studio/pilot --skill pilot-debug -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qf-studio/pilot pilot-debug --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qf-studio/pilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/pilot-debug .agents/skills/pilot-debug && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pilot-debug" agent skill from https://github.com/qf-studio/pilot/tree/main/.claude/skills/pilot-debug into .agents/skills/pilot-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pilot-debug", 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 qf-studio/pilot --skill pilot-debug -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qf-studio/pilot pilot-debug --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qf-studio/pilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/pilot-debug .cursor/skills/pilot-debug && 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 "pilot-debug" agent skill from https://github.com/qf-studio/pilot/tree/main/.claude/skills/pilot-debug into .cursor/skills/pilot-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pilot-debug", 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/qf-studio/pilot.git --path .claude/skills/pilot-debug--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 qf-studio/pilot --skill pilot-debug -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qf-studio/pilot pilot-debug --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qf-studio/pilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/pilot-debug .gemini/skills/pilot-debug && 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 "pilot-debug" agent skill from https://github.com/qf-studio/pilot/tree/main/.claude/skills/pilot-debug into .gemini/skills/pilot-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pilot-debug", 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 qf-studio/pilot pilot-debugInstalls 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 qf-studio/pilot --skill pilot-debug -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/qf-studio/pilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/pilot-debug .github/skills/pilot-debug && 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 "pilot-debug" agent skill from https://github.com/qf-studio/pilot/tree/main/.claude/skills/pilot-debug into .github/skills/pilot-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pilot-debug", 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 qf-studio/pilot --skill pilot-debug -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install qf-studio/pilot pilot-debug --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qf-studio/pilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/pilot-debug .opencode/skills/pilot-debug && 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 "pilot-debug" agent skill from https://github.com/qf-studio/pilot/tree/main/.claude/skills/pilot-debug into .opencode/skills/pilot-debug/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pilot-debug", 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
pilot-debug- GitHub stars
- 722
- Token cost
- ~548 tokens
- SKILL.md length
- 206 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checks a failing Pilot executor against four known failure patterns from the v2.149.x fixes before the agent explores anything else.
- Works in 4 steps: Silent autopilot gate (v2.149.1, commit… → Worktree path equality (v2.149.2, commit… → Vacuous-truth empty children (v2.149.3,… → …
- A Pilot executor run has failed or hung
- SKILL.md covers Triage order, Output, Anti-patterns and Related memories
- Calls git
What it does
When someone reports that pilot failed, an executor or epic is stuck, or autopilot did not fire, the agent states a hypothesis first, in a fixed order, before running any investigation tool. The four patterns each have a diagnostic and a code location: a silent autopilot gate, worktree path equality, vacuous truth for epics with no children, and a missing IsEpic guard that marks epic parents with empty commit or PR fields as failed.
The agent ends with either a match, naming the pattern and following its diagnostic, or a novel result with a one-line reason none fit, in which case it writes a failing regression test first and then escalates. The skill warns against wandering into session directories, daemon config, queue state or the database until all four patterns are ruled out, and it lists memory files that describe each pitfall.
When your agent uses it
- A Pilot executor run has failed or hung
- An epic is stuck and its children look finished
- Autopilot did not start after startup
Example prompts
- “The pilot executor is stuck on this epic. Triage it against the known patterns.”
- “Autopilot didn't fire after the last restart; check the startup logs first.”
- “Pilot failed on a task whose worktree is under /tmp. Check whether it matches a known pattern.”
Requirements
- The Pilot codebase and its startup logs
- Pre-approved tools (allowed-tools): Read, Grep, Bash
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Silent autopilot gate (v2.149.1, commit f032689b)
- Worktree path equality (v2.149.2, commit aac6de5f, TASK-286)
- Vacuous-truth empty children (v2.149.3, commit fd0f7b69)
- Missing IsEpic guard (v2.149.3, commit fd0f7b69)
What it can do on your machine
Read from SKILL.md and the folder at commit 6f9b629. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGrepBash
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, 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
Pilot Failure Triage loads about 548 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 206 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Read, Grep, Bash
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 206 words (~548 tokens).
“When invoked, state the hypothesis FIRST in this exact order before running any investigation tool. Each pattern was patched in v2.149.1–.3 and has high prior probability of recurring.”
- name
- pilot-debug
- allowed-tools
- Read, Grep, Bash
Files
Just SKILL.md in .claude/skills/pilot-debug of qf-studio/pilot.
Open the folder on GitHubat commit 6f9b629
Compare with similar skills
Pilot Failure Triage 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 |
|---|---|---|---|---|---|---|
| Pilot Failure Triage this skillqf-studio/pilot | 722 | — | ~548 | Automated safety check: Notes | Custom licence | |
| OpenLogi macOS Permissions TriageAprilNEA/OpenLogi | 23k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| Bug Finder for daisyUIsaadeghi/daisyui | 43k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Root Cause Debugginggarrytan/gstack | 136k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Graph-Based Bug Tracingtirth8205/code-review-graph | 32k | 1 repos | ~287 | Automated safety check: Pass | MIT | |
| Systematic DebuggingChrisWiles/claude-code-showcase | 6.1k | 3 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Bug Finder for daisyUI
saadeghi/daisyui
Investigates suspected bugs in the daisyUI monorepo through read-only analysis, then writes a decision-ready fix plan in tmp/bugs without changing any product code.
Root Cause Debugging
garrytan/gstack
Investigates bugs, errors and stack traces in phases and requires a root-cause hypothesis to be confirmed before any fix is written.
Graph-Based Bug Tracing
tirth8205/code-review-graph
Traces a bug through a code knowledge graph, following callers, callees and execution flow before opening source files, within a small token budget.
Systematic Debugging
ChrisWiles/claude-code-showcase
Applies a four-phase debugging routine that finds the root cause of a bug or failing test before any fix is written.
Debugging and Error Recovery
addyosmani/agent-skills
Applies a stop-the-line rule and a step-by-step triage when tests fail, builds break or something stops working, aiming at the root cause instead of guesses.
More from qf-studio/pilot
Pilot AWS Daemon Operations
qf-studio/pilot
Checks status, tails logs, queries the task queue, and starts, stops or restarts the Pilot daemon running on a specific AWS EC2 instance over SSM.
Related
Categories
Questions about Pilot Failure Triage
What does Pilot Failure Triage do?
Checks a failing Pilot executor against four known failure patterns from the v2.149.x fixes before the agent explores anything else. When someone reports that pilot failed, an executor or epic is stuck, or autopilot did not fire, the agent states a hypothesis first, in a fixed order, before running any investigation tool. The four patterns each have a diagnostic and a code location: a silent autopilot gate, worktree path equality, vacuous truth for epics with no children, and a missing IsEpic guard that marks epic parents with empty commit or PR fields as failed.
When should I use Pilot Failure Triage?
Pilot Failure Triage fits situations like: A Pilot executor run has failed or hung; an epic is stuck and its children look finished; autopilot did not start after startup.
How do I install Pilot Failure Triage in Claude Code?
Run `npx skills add qf-studio/pilot --skill pilot-debug -a claude-code`. Or copy the skill folder (.claude/skills/pilot-debug in qf-studio/pilot) into .claude/skills/pilot-debug in your project. Claude Code loads it when a task matches its description.
How do I install Pilot Failure Triage in Codex?
Run `npx skills add qf-studio/pilot --skill pilot-debug -a codex`. Or copy the skill folder (.claude/skills/pilot-debug in qf-studio/pilot) into .agents/skills/pilot-debug in your project. Codex loads it when a task matches its description.
Can I use Pilot Failure Triage 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 qf-studio/pilot --skill pilot-debug -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pilot-debug, .gemini/skills/pilot-debug, .github/skills/pilot-debug and .opencode/skills/pilot-debug in your project.
What does Pilot Failure Triage need to run?
Going by SKILL.md and its folder, Pilot Failure Triage needs the command-line tools its instructions call (git). Our summary lists: The Pilot codebase and its startup logs. Its frontmatter pre-approves these tools: Read, Grep, Bash.
Does Pilot Failure Triage access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Pilot Failure Triage safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Pilot Failure Triage use?
Pilot Failure Triage 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 Pilot Failure Triage use?
About 548 tokens (SKILL.md is roughly 2.2k 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 Pilot Failure Triage?
Skills that share tags, products or a category with Pilot Failure Triage: OpenLogi macOS Permissions Triage (AprilNEA/OpenLogi, 23k stars), Bug Finder for daisyUI (saadeghi/daisyui, 43k stars), Root Cause Debugging (garrytan/gstack, 136k stars) and Graph-Based Bug Tracing (tirth8205/code-review-graph, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Pilot Failure Triage?
qf-studio (a GitHub organization) maintains it in qf-studio/pilot, which has 722 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: qf-studio/pilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.