plugins/cache/nyldn-plugins/octo/9.30.0/skills/skill-copilot-provider/SKILL.md
GitHub Copilot CLI as optional zero-cost provider via copilot -p programmatic mode. Use when: AUTOMATICALLY ACTIVATE when user says:. "copilot provider" or "add copilot" or "github copilot" or "use copilot"
npx skillsauth add moliboy5000/.claude skill-copilot-providerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
GitHub Copilot CLI (GA since Feb 2026) serves as an optional provider in the Claude Octopus
multi-LLM ecosystem. Integration uses the official copilot -p programmatic mode, not
reverse-engineered API endpoints.
Core principle: Copilot supplements existing providers for research and exploration at zero additional cost (uses existing GitHub Copilot subscription). Each prompt counts as one premium request against your subscription quota.
Agent types: copilot (general), copilot-research (research-focused)
# Check copilot CLI is available
if ! command -v copilot &>/dev/null; then
# Copilot CLI not installed — silently skip
return 0
fi
Graceful degradation: When Copilot CLI is unavailable or unauthenticated, silently skip. Other providers continue to operate normally.
Copilot CLI checks credentials in this precedence order:
COPILOT_GITHUB_TOKEN env var (highest priority — fine-grained PAT with "Copilot Requests" permission)GH_TOKEN env varGITHUB_TOKEN env varcopilot login)gh) authentication fallbackOption 1: Interactive login (recommended for local dev)
copilot login
Option 2: Fine-grained PAT (recommended for CI/automation)
export COPILOT_GITHUB_TOKEN="github_pat_..."
Option 3: Reuse existing gh auth
If gh auth login is already configured, Copilot CLI will use it automatically.
Note: Classic PATs (ghp_*) are NOT supported. Use fine-grained PATs (github_pat_*).
| Role | Agent Type | Use Case |
|------|-----------|----------|
| General | copilot | Broad research, code explanation, exploration |
| Research | copilot-research | Research-focused exploration and analysis |
# Programmatic mode (non-interactive)
copilot -p "<prompt>" --no-ask-user
When Copilot is active in a multi-provider workflow:
Providers:
🔴 Codex CLI - Implementation
🟡 Gemini CLI - Security review
🟢 Copilot CLI - Research perspective
🔵 Claude - Synthesis
Indicator legend:
The /octo:doctor providers check reports Copilot availability and auth method:
Providers:
✓ Copilot CLI installed (auth: keychain)
When unauthenticated: ⚠ Copilot CLI installed but not authenticated
When missing: ℹ Copilot CLI not installed (optional)
copilot -p prompt = 1 premium request from your monthly allowance/model)🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 Discover Phase: Researching WebSocket authentication patterns
Providers:
🔴 Codex CLI - Technical implementation analysis
🟡 Gemini CLI - Ecosystem research
🟢 Copilot CLI - Research perspective
🔵 Claude - Strategic synthesis
🐙 **CLAUDE OCTOPUS ACTIVATED** - Multi-provider research mode
🔍 Discover Phase: Researching WebSocket authentication patterns
Providers:
🔴 Codex CLI - Technical implementation analysis
🟡 Gemini CLI - Ecosystem research
🔵 Claude - Strategic synthesis
When Copilot is not detected, it is silently omitted from the provider list.
development
Configure Claude Octopus providers and preferences. Use when: Use this skill when the user wants to "configure Claude Octopus", "setup octopus",. "configure providers", "set up API keys for octopus", or mentions octopus configuration.
tools
Zero-context implementation plans with bite-sized tasks. Use when: Use when you have a spec or requirements for a multi-step task.. Auto-invoke when user says "plan how to implement X", "create implementation plan", . "break down this feature into tasks".
content-media
Process screenshot-based UI/UX feedback to fix visual issues. Use when: AUTOMATICALLY ACTIVATE when user provides visual feedback:. "[Image X] The /settings should be Y". "[Image X] these button styles need to be fixed"
testing
Verify claims with actual evidence before declaring success — use to prevent false completion. Use when: Use when about to claim work is complete, fixed, or passing.. Auto-invoke before: commits, PRs, task completion, moving to next task.. ALWAYS use before expressing satisfaction ("Done!", "Fixed!", "All passing!").