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.
tools
MANDATORY prerequisite — load this skill BEFORE every `generate_diagram` tool call. NEVER call `generate_diagram` directly without loading this skill first. Trigger whenever the user asks to create, generate, draw, render, sketch, or build a diagram — flowchart, architecture diagram, sequence diagram, ERD or entity-relationship diagram, state diagram or state machine, gantt chart, or timeline. Also trigger when the user mentions Mermaid syntax or wants a system architecture, decision tree, dependency graph, API call flow, auth handshake, schema, or pipeline visualized in FigJam. Routes to type-specific guidance, sets universal Mermaid constraints, and tells you when to use a different diagram type or skip the tool entirely (mindmaps, pie charts, class diagrams, etc.).
development
DEFAULT PIPELINE for all tasks requiring execution. You (Claude) are the strategic orchestrator. Codex agents are your implementation army - hyper-focused coding specialists. Trigger on ANY task involving code, file modifications, codebase research, multi-step work, or implementation. This is NOT optional - Codex agents are the default for all execution work. Only skip if the user explicitly asks you to do something yourself.
development
This skill should be used when the user asks to analyze a UI screen recording and map interaction states into Figma. Trigger for requests such as "put video frames in Figma", "extract states from my recording", "map interactions from video to Figma", "analyze this screen recording", "create a storyboard from my video", "deconstruct this interaction in Figma", "annotate the UI states in my recording", or "pull the key moments from this video into Figma". Also trigger when the user references a video file (.mp4, .mov, .webm, .avi) together with Figma, design review, interaction analysis, prototypes, or UI states. The skill extracts key visual moments from a video, infers interaction triggers, and builds an annotated Figma Design storyboard using native Figma annotations and uploaded screenshot assets.
development
Generate a FigJam project plan board from a PRD plus codebase context. Interactive flow: research → propose sections → per-section deep research → per-section content + block-shape proposal → create FigJam → skeleton → fill → diagrams → wrap. Each content block (section, nested section, intro callout, table, multi-column text, sticky column, diagram section, metadata strip) has its own subskill reference file. Use when the user asks for 'project plan in FigJam', 'interactive project plan', '/generate-project-plan', or provides a PRD and wants per-section confirmation on content + rendering.