GB-Power-Market-JJ copilot-cli

install

source · Clone the upstream repo

git clone https://github.com/GeorgeDoors888/GB-Power-Market-JJ

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/GeorgeDoors888/GB-Power-Market-JJ "$T" && mkdir -p ~/.claude/skills && cp -r "$T/openclaw-skills/skills/awalesagar/copilot-cli-base" ~/.claude/skills/georgedoors888-gb-power-market-jj-copilot-cli && rm -rf "$T"

OpenClaw · Install into ~/.openclaw/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/GeorgeDoors888/GB-Power-Market-JJ "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/openclaw-skills/skills/awalesagar/copilot-cli-base" ~/.openclaw/skills/georgedoors888-gb-power-market-jj-copilot-cli && rm -rf "$T"

manifest: openclaw-skills/skills/awalesagar/copilot-cli-base/SKILL.md

source content

Copilot CLI Reference Skill

GitHub Copilot CLI is a terminal-native AI coding agent. This skill provides reference docs for all features, commands, and operational patterns.

Quick Reference

Interactive:

copilot

→ trust directory →

/login

→ prompt Programmatic:

copilot -p "PROMPT" --yolo --no-ask-user -s

With permissions:

copilot -p "PROMPT" --allow-tool='shell(git:*), write' --no-ask-user

Custom agent:

copilot -p "PROMPT" --agent=my-agent

Model override:

copilot -p "PROMPT" --model claude-opus-4.6

When to Use Copilot CLI vs Claude Code

Rate-limited on Claude Code? → Use Copilot CLI as fallback
CI/CD automation? → Copilot CLI (built-in Actions support)
Clean stdout needed? → Claude Code (no PTY/ANSI issues)
Long iterative reviews? → Copilot CLI (better for many iterations)

See

reference/patterns-and-best-practices.md

for the full decision matrix.

Key Gotchas

Always use
```
-p
```
(not
```
-i
```
) for automation —
```
-i
```
hangs
```
--yolo
```
does NOT skip folder trust — pre-trust in
```
~/.copilot/config.json
```
No
```
copilot config set
```
— edit config JSON manually
Size timeouts by complexity: 120s (simple) → 1800s (large)
Background servers die between exec spawns — restart each time

See

reference/troubleshooting.md

for all issues and fixes.

Reference Documents

Full index:

reference/index.md

File	Contents
`getting-started.md`	Installation, auth, config, permissions, env vars
`usage.md`	Interactive & programmatic modes, commands, shortcuts, model selection
`automation-and-delegation.md`	CI/CD, GitHub Actions, autopilot, delegate, fleet, custom agents
`customization.md`	Custom instructions, plugins, MCP servers, enterprise governance
`hooks.md`	Hook types, config, denial responses, policy scripts
`integrations.md`	VS Code integration, ACP server
`research.md`	`/research` reports, `/chronicle` session history
`troubleshooting.md`	Auth, rate limits, SIGTERM, PTY, trust, config gotchas
`patterns-and-best-practices.md`	Decision matrix, prompt engineering, anti-patterns

All files in

reference/

directory.