OpenClaw GitHub Copilot
Use this skill to make GitHub Copilot the simplest possible OpenClaw default.
This skill is for four jobs:
- 1. first-time GitHub Copilot setup in OpenClaw
- switching the default model to Copilot
- fixing common
copilot-bridge/github-copilot auth or alias issues - giving the user one short command path instead of a pile of manual steps
What this skill assumes
- -
openclaw is installed - the user has GitHub Copilot access on the GitHub account they will log in with
- the agent prefers OpenClaw CLI commands over hand-editing config files
Fast path
Start with the single diagnostic command:
CODEBLOCK0
If the user wants Copilot to become the default model and auth is already valid:
CODEBLOCK1
If auth is missing or expired and you are in an interactive TTY:
CODEBLOCK2
That wrapper is the preferred entrypoint because it:
- - checks whether the Copilot model exists
- checks whether the short alias exists
- optionally creates the alias when asked
- optionally runs the official GitHub Copilot device login
- optionally switches the default model to Copilot
Canonical identifiers
- - Full model id: INLINECODE2
- Preferred alias: INLINECODE3
Always verify what OpenClaw already knows before claiming anything:
CODEBLOCK3
If the alias exists, prefer it in human-facing instructions because it is shorter:
CODEBLOCK4
If the alias is missing, use the full model id:
CODEBLOCK5
Recommended workflow
1. Diagnose first
Run:
CODEBLOCK6
Use the stronger live probe when auth freshness matters:
CODEBLOCK7
The script reports:
- - whether the Copilot model is registered
- whether
copilot-auto points at that model - what the current default model is
- whether GitHub Copilot is already the active default
2. Authenticate only with the official flow
If the model exists but auth is missing or stale, use:
CODEBLOCK8
Important:
- - this requires an interactive TTY
- it may require a browser/device-code step
- do not pretend it can be completed silently in the background
3. Switch the default model
If the user explicitly wants Copilot as the default model:
CODEBLOCK9
Or use the wrapper:
CODEBLOCK10
4. Confirm result
Verify with:
CODEBLOCK11
The configured default should resolve to copilot-bridge/github-copilot.
If the current session still behaves like the old model, start a fresh OpenClaw session. Skill and default-model changes are most reliable in a new session.
Good trigger phrases
Use this skill for requests like:
- - "让 OpenClaw 用 GitHub Copilot"
- "把默认 agent 切到 Copilot"
- "检查 Copilot bridge 配好了没有"
- "GitHub Copilot 在 OpenClaw 里怎么登录"
- "给我一个最简单的 Copilot 配置流程"
- "copilot-auto 不生效"
Practical response pattern
When helping a user, keep the answer operational:
- 1. say whether the model exists
- say whether it is already the default
- give the next exact command
- only mention manual alias cleanup or config editing if the CLI flow is insufficient
Example:
CODEBLOCK12
References
- -
references/setup-guide.md - full first-time setup walkthrough - INLINECODE7 - missing model, alias, auth, and session behavior
- INLINECODE8 - release checklist for publishing to ClawHub
OpenClaw GitHub Copilot
使用此技能让 GitHub Copilot 成为 OpenClaw 最简单的默认配置。
此技能负责四项工作:
- 1. 在 OpenClaw 中首次设置 GitHub Copilot
- 将默认模型切换为 Copilot
- 修复常见的 copilot-bridge/github-copilot 认证或别名问题
- 为用户提供一个简短命令路径,而非一堆手动步骤
此技能的假设条件
- - openclaw 已安装
- 用户在其登录的 GitHub 账户上拥有 GitHub Copilot 访问权限
- 代理更倾向于使用 OpenClaw CLI 命令而非手动编辑配置文件
快速路径
从单个诊断命令开始:
bash
bash {baseDir}/scripts/copilot-quickstart.sh --probe
如果用户希望 Copilot 成为默认模型且认证已有效:
bash
bash {baseDir}/scripts/copilot-quickstart.sh --probe --activate
如果认证缺失或已过期,且你在交互式 TTY 环境中:
bash
bash {baseDir}/scripts/copilot-quickstart.sh --probe --login --activate
该包装脚本是首选入口点,因为它:
- - 检查 Copilot 模型是否存在
- 检查短别名是否存在
- 可选地在被要求时创建别名
- 可选地运行官方 GitHub Copilot 设备登录
- 可选地将默认模型切换为 Copilot
标准标识符
- - 完整模型 ID:copilot-bridge/github-copilot
- 首选别名:copilot-auto
在做出任何声明前,始终验证 OpenClaw 已知的信息:
bash
openclaw models list --plain
openclaw models aliases list
openclaw models status --plain
如果别名存在,在面向用户的指令中优先使用它,因为它更短:
bash
openclaw models set copilot-auto
如果别名缺失,使用完整模型 ID:
bash
openclaw models set copilot-bridge/github-copilot
推荐工作流程
1. 首先诊断
运行:
bash
bash {baseDir}/scripts/copilot-status.sh
当认证新鲜度重要时,使用更强的实时探测:
bash
bash {baseDir}/scripts/copilot-status.sh --probe
该脚本报告:
- - Copilot 模型是否已注册
- copilot-auto 是否指向该模型
- 当前默认模型是什么
- GitHub Copilot 是否已经是活动的默认模型
2. 仅使用官方流程进行认证
如果模型存在但认证缺失或过期,使用:
bash
openclaw models auth login-github-copilot
重要提示:
- - 这需要交互式 TTY 环境
- 可能需要浏览器/设备代码步骤
- 不要假装它可以在后台静默完成
3. 切换默认模型
如果用户明确希望将 Copilot 设为默认模型:
bash
bash {baseDir}/scripts/copilot-activate.sh
或使用包装脚本:
bash
bash {baseDir}/scripts/copilot-quickstart.sh --activate
4. 确认结果
使用以下命令验证:
bash
openclaw models status --plain
配置的默认模型应解析为 copilot-bridge/github-copilot。
如果当前会话仍然表现为旧模型的行为,请启动一个新的 OpenClaw 会话。技能和默认模型的更改在新会话中最可靠。
良好的触发短语
对此类请求使用此技能:
- - 让 OpenClaw 用 GitHub Copilot
- 把默认 agent 切到 Copilot
- 检查 Copilot bridge 配好了没有
- GitHub Copilot 在 OpenClaw 里怎么登录
- 给我一个最简单的 Copilot 配置流程
- copilot-auto 不生效
实用响应模式
在帮助用户时,保持回答的可操作性:
- 1. 说明模型是否存在
- 说明它是否已经是默认模型
- 给出下一个确切的命令
- 仅在 CLI 流程不足时提及手动别名清理或配置编辑
示例:
text
GitHub Copilot 这个模型已经在 OpenClaw 里了,但当前默认模型不是它。
直接执行 bash {baseDir}/scripts/copilot-quickstart.sh --probe --activate。
如果后面提示鉴权失效,再跑 openclaw models auth login-github-copilot。
参考资料
- - references/setup-guide.md - 完整的首次设置指南
- references/troubleshooting.md - 缺失模型、别名、认证和会话行为
- references/publish-checklist.md - 发布到 ClawHub 的发布清单