Agent skill

Nav Pilot

Dispatch a Navigator task doc to Pilot as a labeled GitHub issue.

Install Nav Pilot

skills CLI

$ npx skills add qf-studio/navigator --skill nav-pilot -a claude-code

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

GitHub CLI

$ gh skill install qf-studio/navigator nav-pilot --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/qf-studio/navigator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nav-pilot .claude/skills/nav-pilot && 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/

Paste into Claude Code

Install the "nav-pilot" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot into .claude/skills/nav-pilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-pilot", 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

$skill-installer install https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot

Type 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.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-pilot -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-pilot --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/nav-pilot .agents/skills/nav-pilot && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "nav-pilot" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot into .agents/skills/nav-pilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-pilot", 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.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-pilot -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-pilot --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/nav-pilot .cursor/skills/nav-pilot && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "nav-pilot" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot into .cursor/skills/nav-pilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-pilot", 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

$ gemini skills install https://github.com/qf-studio/navigator.git --path skills/nav-pilot

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-pilot -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-pilot --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/nav-pilot .gemini/skills/nav-pilot && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "nav-pilot" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot into .gemini/skills/nav-pilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-pilot", 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.

GitHub CLI

$ gh skill install qf-studio/navigator nav-pilot

Installs 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).

skills CLI

$ npx skills add qf-studio/navigator --skill nav-pilot -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/nav-pilot .github/skills/nav-pilot && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "nav-pilot" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot into .github/skills/nav-pilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-pilot", 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.

skills CLI

$ npx skills add qf-studio/navigator --skill nav-pilot -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install qf-studio/navigator nav-pilot --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/qf-studio/navigator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/nav-pilot .opencode/skills/nav-pilot && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "nav-pilot" agent skill from https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot into .opencode/skills/nav-pilot/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nav-pilot", 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: nav-pilot
GitHub stars: 355
Token cost: ~1.3k tokens
SKILL.md length: 549 words
Files: 1
Skills in repo: 32
Repo updated: Oct 8, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Dispatch a Navigator task doc to Pilot as a labeled GitHub issue.

Works in 7 steps: Resolve the Target Task Doc → Load Pilot Config → Build the Command → …
User says dispatch TASK-XX to Pilot
SKILL.md covers When to Invoke, Execution Steps, Error Handling and Success Criteria, plus 1 more section
Calls gh

What it does

Nav Pilot is an agent skill from qf-studio/navigator. Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).

Its SKILL.md is about 1.3k 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 Agent Workflows. It works with GitHub. The repository describes itself as: Finish What You Start — Context engineering for Claude Code. Sessions last 20+ exchanges instead of crashing at 7. The licence is MIT.

When your agent uses it

User says dispatch TASK-XX to Pilot
Hand off to Pilot
Queue for Pilot

Example prompts

“dispatch TASK-XX to Pilot”
“hand off to Pilot”
“send to Pilot”
“/nav-pilot”

Requirements

Pre-approved tools (allowed-tools): Read, Edit, Bash, Glob

Workflow steps

7 steps, taken from the step headings in SKILL.md.

Resolve the Target Task Doc
Load Pilot Config
Build the Command
Pre-flight Confirmation (ToM Checkpoint — high-stakes)
Dispatch
Record Back Into the Doc
Confirm

What it can do on your machine

Read from SKILL.md and the folder at commit 3bb9eac. 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:
- Read
- Edit
- Bash
- Glob
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, 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

Nav Pilot loads about 1.3k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 549 words of instructions outside code blocks.

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

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, Edit, Bash, Glob
```

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 qf-studio/navigator at commit 3bb9eac, republished under its MIT licence (© qf-studio). 549 words, ~1,262 tokens.

Download SKILL.mdSave it as .claude/skills/nav-pilot/SKILL.md (or your agent's skills folder).

name: nav-pilot
description: Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
allowed-tools: Read, Edit, Bash, Glob
version: 1.0.0

Navigator → Pilot Dispatch Skill

Hand a finished Navigator task doc off to Pilot by creating the pilot-labeled GitHub issue Pilot polls, then record the issue back into the doc.

This skill does NOT validate the doc. Spec checking is Pilot's job (its spec_validator). nav-pilot only resolves the doc, creates the labeled issue, and records the result. It consumes what nav-task authored — it does not author or archive docs itself.

When to Invoke

Invoke when the user says:

"Dispatch TASK-XX to Pilot"
"Hand this off to Pilot" / "send to Pilot"
"Queue TASK-XX for Pilot" / "create the Pilot issue"

DO NOT invoke when:

User is authoring/archiving a task doc (that's nav-task)
User wants Pilot worker status (out of scope — this skill is one-way)
No task doc exists yet (tell them to create one with nav-task first)

Execution Steps

Step 1: Resolve the Target Task Doc

Explicit ID ("TASK-07"): use .agent/tasks/TASK-07-*.md.
No ID: pick the active/in-progress task. If ambiguous, list candidates (ls .agent/tasks/*.md) and ask which one.
If the file does not exist, stop and tell the user to author it first.

Read the doc and extract:

Title = the first H1 (# TASK-XX: <name>), stripped of the TASK-XX: prefix if present (or keep the full H1 — match what Pilot expects).
Body file path = the doc itself (passed via --body-file, never inlined).

Step 2: Load Pilot Config

Read pilot from .agent/.nav-config.json:

json

"pilot": {
  "enabled": true,
  "label": "pilot",
  "repo": null
}

label (default "pilot"): the label Pilot polls for.
repo (default null): target owner/name. When null, gh uses the current git repository's origin — do NOT pass --repo.

If pilot.enabled is false, stop and tell the user to enable it.

Step 3: Build the Command

bash

gh issue create \
  --title "<H1 title>" \
  --label "<pilot.label>" \
  --body-file ".agent/tasks/TASK-XX-<slug>.md" \
  [--repo "<pilot.repo>"]   # only when pilot.repo is set

Step 4: Pre-flight Confirmation (ToM Checkpoint — high-stakes)

Creating a GitHub issue is an outward-facing action. ALWAYS confirm first:

About to dispatch to Pilot:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Repo:  <pilot.repo or "current origin (gh default)">
Title: <H1 title>
Label: <pilot.label>
Body:  .agent/tasks/TASK-XX-<slug>.md (<N> lines)

Command:
  gh issue create --title "..." --label "pilot" --body-file "..."
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Create this issue? [Enter to dispatch / "dry-run" / corrections]

--dry-run mode: if the user asked for a dry run (or says "dry-run" here), print the exact gh command and STOP. Do not execute.

Show full SKILL.md (238 more words)Show less

Step 5: Dispatch

Run the gh issue create command. Capture the returned issue URL from stdout (gh issue create prints the URL on success).

If gh fails:

not authenticated → tell the user to run gh auth login
label missing on the repo → offer gh label create pilot
no git remote / repo not found → ask for pilot.repo in config

Step 6: Record Back Into the Doc

Edit the task doc:

Add the issue URL under ## Refs: - Pilot issue: <url>
Update the status line to **Status**: 🚀 Dispatched to Pilot.
Update **Last Updated**: to today.

Step 7: Confirm

✅ Dispatched to Pilot

Issue:  <url>
Label:  pilot
Task:   TASK-XX — <title>

Recorded back into .agent/tasks/TASK-XX-<slug>.md (status → 🚀 Dispatched).
Pilot will pick it up on its next poll of `pilot`-labeled issues.

If the knowledge graph is enabled, the Edit will sync via the normal PostToolUse hook — no extra action needed.

Error Handling

Situation	Response
No task doc found	Ask which task; suggest `nav-task` to create one
`pilot.enabled: false`	Stop; tell user to enable in `.nav-config.json`
`gh` not authenticated	Prompt `gh auth login`
`pilot` label missing	Offer `gh label create pilot`
No remote / repo unknown	Ask user to set `pilot.repo`

Success Criteria

Correct task doc resolved and H1 used as the issue title
Pre-flight confirmation shown before any network call
--dry-run prints the command without executing
Issue created with the pilot label
Issue URL recorded back into the doc; status → 🚀 Dispatched

Notes

One-way by design: monitoring Pilot workers and pulling results back are out of scope (see .agent/tasks/TASK-54-nav-pilot-dispatch-skill.md).
Validation is intentionally absent — Pilot's spec_validator owns that.
Pairs with nav-task (authors the doc) → nav-pilot (dispatches it).

Files

Just SKILL.md in skills/nav-pilot of qf-studio/navigator.

Open the folder on GitHubat commit 3bb9eac

Compare with similar skills

Nav Pilot 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.

Nav Pilot compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Nav Pilot this skillqf-studio/navigator	355	—	~1.3k	Automated safety check: Notes	MIT	2 days ago
Diagnosing Superpowers Sessionsobra/superpowers	297k	3 repos	~1.7k	Automated safety check: Pass	MIT	yesterday
Auto Skill Buildertradecatlabs/vibe-coding-cn	17k	1 repos	~2.4k	Automated safety check: Pass	MIT	yesterday
Agentic Workflow Designerdotnet/Open-XML-SDK	4.6k	2 repos	~3.5k	Automated safety check: Pass	MIT	yesterday
Skill Seekers Builderyusufkaraaslan/Skill_Seekers	15k	—	~760	Automated safety check: Pass	MIT	10 days ago
Repomix Codebase Packeryamadashy/repomix	29k	—	~1.3k	Automated safety check: Notes	MIT	today

Similar skills

Diagnosing Superpowers Sessions
obra/superpowers
Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.
297k GitHub starsUsed in 3 repos~1.7k tokens
Agent WorkflowsAuto-check passed
Auto Skill Builder
tradecatlabs/vibe-coding-cn
Meta-skill that turns docs, APIs, code or specs into a reusable skill with references and a quality gate, and refactors skills that are unclear or misfire.
17k GitHub starsUsed in 1 repo~2.4k tokens
Agent WorkflowsAuto-check passed
Agentic Workflow Designer
dotnet/Open-XML-SDK
Official
Interviews you one question at a time about goal, trigger, permissions and data needs, then drafts a single agentic workflow markdown file.
4.6k GitHub starsUsed in 2 repos~3.5k tokens
Agent WorkflowsAuto-check passed
Skill Seekers Builder
yusufkaraaslan/Skill_Seekers
Detects the type of a knowledge source and uses the Skill Seekers MCP tools to turn docs, repos, PDFs or videos into packaged AI skills.
15k GitHub stars~760 tokensUpdated 10 days ago
Agent WorkflowsAuto-check passed
Repomix Codebase Packer
yamadashy/repomix
Packs a local directory or remote GitHub repository into one AI-friendly file with Repomix, then searches it to explore structure, find patterns and count tokens.
29k GitHub stars~1.3k tokensUpdated today
Agent WorkflowsAuto-check: notes
Context Mode Ops
mksglu/context-mode
Runs maintenance for the context-mode project with parallel subagents: issue triage, PR review, releases, bug fixes, announcements and branch syncing.
26k GitHub stars~6k tokensUpdated today
Agent WorkflowsAuto-check passed

Questions about Nav Pilot

What does Nav Pilot do?

Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Nav Pilot is an agent skill from qf-studio/navigator. Dispatch a Navigator task doc to Pilot as a labeled GitHub issue.

When should I use Nav Pilot?

Nav Pilot fits situations like: user says dispatch TASK-XX to Pilot; hand off to Pilot; queue for Pilot.

How do I install Nav Pilot in Claude Code?

Run `npx skills add qf-studio/navigator --skill nav-pilot -a claude-code`. Or copy the skill folder (skills/nav-pilot in qf-studio/navigator) into .claude/skills/nav-pilot in your project. Claude Code loads it when a task matches its description.

How do I install Nav Pilot in Codex?

Run `npx skills add qf-studio/navigator --skill nav-pilot -a codex`. Or copy the skill folder (skills/nav-pilot in qf-studio/navigator) into .agents/skills/nav-pilot in your project. Codex loads it when a task matches its description.

Can I use Nav Pilot 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/navigator --skill nav-pilot -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nav-pilot, .gemini/skills/nav-pilot, .github/skills/nav-pilot and .opencode/skills/nav-pilot in your project.

What does Nav Pilot need to run?

Going by SKILL.md and its folder, Nav Pilot needs the command-line tools its instructions call (gh). Its frontmatter pre-approves these tools: Read, Edit, Bash, Glob.

Does Nav Pilot access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Nav Pilot 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 Nav Pilot use?

Nav Pilot 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 Nav Pilot use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Nav Pilot?

Skills that share tags, products or a category with Nav Pilot: Diagnosing Superpowers Sessions (obra/superpowers, 297k stars), Auto Skill Builder (tradecatlabs/vibe-coding-cn, 17k stars), Agentic Workflow Designer (dotnet/Open-XML-SDK, 4.6k stars) and Skill Seekers Builder (yusufkaraaslan/Skill_Seekers, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Nav Pilot?

qf-studio (a GitHub organization) maintains it in qf-studio/navigator, which has 355 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.

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

Install Nav Pilot

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Navigator → Pilot Dispatch Skill

When to Invoke

Execution Steps

Step 1: Resolve the Target Task Doc

Step 2: Load Pilot Config

Step 3: Build the Command

Step 4: Pre-flight Confirmation (ToM Checkpoint — high-stakes)

Step 5: Dispatch

Step 6: Record Back Into the Doc

Step 7: Confirm

Error Handling

Success Criteria

Notes

Files

Compare with similar skills

Similar skills

More from qf-studio/navigator

Related

Questions about Nav Pilot