Dispatch Navigator task docs to Pilot as labeled GitHub issues via gh CLI.
npx skills add https://github.com/qf-studio/navigator --skill nav-pilot-qf-studio
Please help me install this Agent Skill. Skill: nav-pilot Source: https://github.com/qf-studio/navigator/tree/main/skills/nav-pilot Command: npx skills add https://github.com/qf-studio/navigator --skill nav-pilot-qf-studio
.agent/tasks/ by explicit ID (e.g., TASK-07) or by picking the active task, extracting the H1 title for the issue. - Config-Driven Dispatch: Reads the pilot section of .agent/.nav-config.json for the label and target repo, then builds the correct gh issue create command with --body-file. - Pre-flight Confirmation & Dry-Run: Shows the exact repo, title, label, and command before any network call, and supports a dry-run mode that prints the command without executing. - Write-Back Tracking: Records the created issue URL under the doc's ## Refs section and updates the status to Dispatched. - Use Case: After authoring TASK-12 with nav-task, say "dispatch TASK-12 to Pilot" and the Skill creates the pilot-labeled issue and logs the URL back into the doc. ## Quick Start Tell the assistant to dispatch TASK-XX to Pilot after authoring the task doc with nav-task.High-intent search queries and answers about installing and using this skill.
Say "dispatch TASK-XX to Pilot" after authoring the doc with nav-task. The Skill resolves the doc in .agent/tasks/, builds a gh issue create command with the pilot label and --body-file, confirms with you, then creates the issue and records the URL back into the doc.
Use gh issue create with --title, --label, and --body-file pointing at the markdown file. The body file is passed by path rather than inlined, and gh prints the new issue URL on success.
No, validation is intentionally out of scope. Spec checking is owned by Pilot's spec_validator on the receiving side; nav-pilot only resolves the doc, creates the labeled issue, and records the result.
If gh is not authenticated, the Skill tells you to run gh auth login. If the pilot label does not exist on the repo, it offers to run gh label create pilot. If no remote is found, it asks you to set pilot.repo in .nav-config.json.
Yes, request a dry run and the Skill prints the exact gh issue create command and stops without executing. Every dispatch also shows a pre-flight confirmation with repo, title, label, and body file before any network call.
No, the handoff is one-way by design. Monitoring Pilot worker status and retrieving execution results are explicitly out of scope for this Skill.
xobotyiGenerate structured tasks, bug reports, and feature requests for issue trackers.
shuff57Automate the GitHub Pull Request lifecycle from branch creation to merging.
adtecoTrack persistent multi-session work using bd dependency graphs and structured session notes.
githubnextCreate and manage GitHub Copilot coding agent sessions via the gh agent-task CLI extension.