GitHub Copilot Skills Should Stay Quiet Until You Ask for a Release
A release checklist should stay unloaded until the task matches, and one shared folder plus a symlink is how that GitHub Copilot skill travels without a second copy.

The release-checklist body loads when you prepare a release, not when you say "run the tests," and one symlink shares that folder
You pasted the release checklist into the chat, and the next request to run the tests started talking about auto-merge. The checklist was right for a release, and it was loaded for a task that did not need it.
In this article: You will add a
release-checklistskill for Ticket Triage, prove that a plain request to run the tests does not need the body, and commit one folder plus a symlink. You will see how Copilot CLI 1.0.112 searches.github/skills,.agents/skills, and.claude/skills, why the first copy wins, and how Claude Code, OpenCode, and Pi treat the same name. By the end, the checklist waits until you ask for a release,src/classify.jsis untouched, and the commit is yours.
Preview: written November 16, 2026, before Microsoft Ignite. Some paid steps are not yet tested live; this guide will be updated November 21, 2026.
A release checklist is useful once a week and noisy every other day. Paste it into a GitHub Copilot session and "run the tests" can come back talking about auto-merge. The checklist was not wrong. It was loaded for a task that never asked for it.
A GitHub Copilot skill is a folder with a SKILL.md file, in the Agent Skills shape. Only the name and the description load up front. The body loads when the task matches. Ticket Triage already sorts tickets into refund, shipping, or other, and four tests pass. You will add release-checklist under .agents/skills, point .claude/skills at that folder with a symlink, ask two questions, and commit the skill yourself. src/classify.js has no crushed-mug rule. You do not add one today.
Starting fresh or fell behind? Run git switch -C main copilot/day-08. This replaces your main with the end of Day 8; to keep your own work, run git branch my-backup first.
A skill loads the name, not the checklist
Minimum metadata is a name and a description. Scripts, references, and assets may sit beside SKILL.md. This checklist has none. The standard does not choose every client's search folders, conflict priority, invocation controls, or trust model. Your three lines name npm test, a path in this repo, and auto-merge. They do not name a Copilot-only tool. The description says when to use the skill and when not to. The three Confirm lines are the body, and they stay unloaded until a task matches.

"Run the tests" should not mention auto-merge, and it should not treat the crushed mug as a release gate. "Prepare the release checklist" should cover the three checks you wrote: tests pass, src/classify.js still has no crushed-mug rule, and auto-merge stays off. Auto-merge would merge a pull request without a separate yes from you. A person merges. You do not open a GitHub issue today. git diff is still the proof the classifier did not change.

The poster is that split. The name, and the line that says when not to use the skill, load first. Tests, an unchanged classifier, and a human merge stay in the body until the request is a release.
These steps use Copilot CLI 1.0.112, as of November 16, 2026. Discovery for this folder was tested that day with skill list. This article does not print that listing. A paid model invocation of the body was not observed. There is no sample reply. Re-run the two questions on your account before you trust the wording.
copilot --version
Write the line down if you did not keep it. Do not reinstall. The git checks do not depend on a reply.
Write release-checklist in one folder
Work in ~/code/ticket-triage. On Windows, use the Ticket Triage folder you already have. If that path is C:\code\ticket-triage, use it. Run the blocks in Git Bash, or in the bash-compatible terminal you use for npm test. The agent does not run git.
cd ~/code/ticket-triage
git diff -- src/classify.js
git status --short
npm test
git diff -- src/classify.js prints nothing. git status --short prints nothing. npm test reports refund, shipping, other, and crushed mug in pieces is other, plus # tests 4, # pass 4, and # fail 0. Timings do not count. If status prints paths, if the classifier diff prints a patch, or if the pass count is not four with zero failures, stop. Do not ask a session to clean the tree or edit the classifier.
Save this exact file at .agents/skills/release-checklist/SKILL.md. Do not also save it under .github/skills. Copilot keeps the first copy it finds, so a second copy there would hide this one.
---
name: release-checklist
description: Prepare Ticket Triage for a release. Use when asked to prepare the release checklist. Do not use for a plain request to run the tests.
---
Confirm npm test passes.
Confirm src/classify.js still has no crushed-mug rule. The open issue has to say so before that file changes.
Confirm auto-merge is off. A person merges.
test -f .agents/skills/release-checklist/SKILL.md && echo ok
The command prints ok. If it prints nothing, fix the path. Do not add a second SKILL.md somewhere else.
gh skill preview is the habit before you install a skill you did not write. GitHub does not verify skills. You wrote this one, so preview is not a blocker today. This article does not show preview output.
One symlink, not a second copy
Claude Code reads .claude/skills. Copilot CLI reads that path later than .agents/skills. From the repository root, the link target is relative to .claude/.
mkdir -p .claude
ln -s ../.agents/skills .claude/skills
.claude/skills now points at ../.agents/skills. You do not copy the files. On Windows, if ln fails, stop. A second copy is a duplicate name, and Copilot keeps the first one it finds. If .claude/skills is already a real directory, stop and look. Do not delete a directory you do not recognize.
readlink .claude/skills
The line is ../.agents/skills. A different path means you remove the link and run ln again. Do not replace it with a real directory.

The file you commit is the shared one. A copy under .github/skills would win, because that folder is checked first.

The poster is that setup. The committed path is .agents/skills/release-checklist/SKILL.md, and the link target is ../.agents/skills. If ln fails, you stop. You do not paste a duplicate to make the link work.
Two requests, one credit cap
Start a new copilot session in ~/code/ticket-triage. Do not pass --agent. --max-ai-credits caps the credits this session may use. A credit is the usage unit. The cap applies to this session, not the account. Replace 20 with a small number you choose before you press Enter. You pass no model name.
cd ~/code/ticket-triage
copilot --max-ai-credits 20
You do not pass --continue, --yolo, --allow-all, or --allow-all-tools. --yolo allows tools, paths, and URLs. You do not enable auto-merge, and you do not open a pull request today. If a picker appears, do not type a model name. If the only way forward is a model name, stop. If the shell history still shows the placeholder 20, the check fails until it shows the number you chose.
Ask the first question on its own.
Run the tests.
The reply should not need the release checklist body. It should not talk about auto-merge, and it should not treat the crushed-mug issue as a release gate. From a second terminal, run the tests yourself.
cd ~/code/ticket-triage
npm test
npm test still shows the four names, # tests 4, # pass 4, and # fail 0. If the pass count is not four, stop. Do not ask the session to change src/classify.js. Then ask the second question in the same session.
Prepare the release checklist.
Look for the three checks: tests pass, src/classify.js still waiting on the crushed-mug change, and auto-merge off. Those points belong in this reply, and they do not belong in the first. There is no on-screen badge for a skill, and there is no sample reply. A paid model invocation of this skill was not recorded on November 16, 2026. Re-run this on your account before you trust the wording. If the session asks to edit src/classify.js, to turn auto-merge on, or to commit, refuse. If you cannot tell which answer refuses, stop the turn.

skill list on Copilot CLI 1.0.112 showed that the CLI could see the skill. A paid model following the three checks was not observed that day. The replies on your screen are yours.
Prove the tree, then commit it yourself
Leave the session up until you have read both replies. From a second terminal:
cd ~/code/ticket-triage
git diff -- src/classify.js
git status --short
npm test
The classifier diff prints nothing. Status may list .agents/skills/release-checklist/SKILL.md and .claude/skills, and it must not list src/classify.js or test/classify.test.js. Tests still show four passes and zero failures. If the classifier diff prints a patch, run git restore src/classify.js, run the diff again, and do not commit that file.
You commit the skill and the symlink. The agent does not run git. git add names the file and the link. It does not follow the link into a second copy.
git add .agents/skills/release-checklist/SKILL.md .claude/skills
git commit -m "Add the Ticket Triage release checklist skill"
git status --short
git diff -- src/classify.js
npm test
After the commit, status prints nothing, the classifier diff still prints nothing, and tests still show four passes and zero failures.

The win is the skill on disk, a second reply that covers the three checks while the first did not need that body, four passing tests, an empty diff on src/classify.js, and the commit above.

The classifier did not grow a crushed-mug rule while you asked about a release. The checklist stayed in the second reply. The commit is yours, not the agent's.
First found wins
The Copilot CLI plugin reference orders project folders first. First found wins: .github/skills, then .agents/skills, then .claude/skills. The same reference then lists folders inherited from a parent directory, then personal ~/.copilot/skills, then personal ~/.agents/skills, then plugins, then paths you configure. The November 16, 2026 test on Copilot CLI 1.0.112 confirmed the three project folders and that conflict priority. It did not re-prove every later step. Your file is in the second project folder, with no same-named copy in the first.
A skill that lives only under ~/.copilot/skills or ~/.agents/skills is on this machine. It is not in the Ticket Triage commit. Today's skill is the project copy you can hand to someone else with the repo.
Gotcha: copying release-checklist into .github/skills because that path looks more official. Copilot finds that folder first. The copy there wins, and the body under .agents/skills is not the one that loads. Use one name in one folder.
Other Copilot surfaces are not this test. The VS Code Copilot harness documents .github/skills and ~/.copilot/skills as preferred locations, and it says that the table is not every folder. GitHub code review documents .github/skills. The November 16, 2026 notes do not show that code review discovers every other project folder or home folder. JetBrains Air has no Air-specific skill-folder contract in those notes. This walkthrough did not test JetBrains, Air, code review, or a separate collision order for the GitHub Copilot app. Do not treat the CLI order as an app rule. A cloud session does not upload home skills on its own. This walkthrough did not run a cloud test.
A plugin package is not today's skill
Copilot CLI loads an Agent Plugins folder. An Agent Plugins package is a directory with a root plugin.json and a fixed skills/ directory. The portable core is skills and MCP configuration, not every vendor's agents, hooks, or rules. The CLI reference accepts the canonical 1.0.0 and 1.1.0 schema identifiers. The standards site used for this check presents 1.0.0. Accepting 1.1 does not make 1.1 a requirement. You do not need either schema today.
On November 16, 2026, a Copilot CLI 1.0.112 test passed --plugin-dir and ran skill list --json. The run loaded a skill named spec-check from the test package. The recorded result is skill discovery. You do not add plugin.json, and you do not pass --plugin-dir.
Vendor pieces live in com.github.copilot/ inside a plugin. Other clients ignore a namespace they do not implement. The shared skill is .agents/skills, not that namespace. The sketch is not a task. skills/ is the portable part. com.github.copilot/ is the Copilot-only part.
my-plugin/
plugin.json
skills/
test-workflow/
SKILL.md
mcp.json
com.github.copilot/
agents/
hooks/
You do not create my-plugin. release-checklist stays at .agents/skills/release-checklist/SKILL.md. You do not move it under com.github.copilot/.

Discovery from .agents/skills is tested on Copilot CLI 1.0.112 with skill list. A paid invocation of the body was not observed. Do not write down that the model followed the three checks on November 16, 2026.
Gotcha: treating the checklist reply as permission to turn auto-merge on. The body says a person merges. A sentence in a skill does not flip a GitHub setting, and you do not flip it today.
Four tools, two opposite duplicate rules
Each row is one tool's project folders, how that tool picks a winner when two skills share a name, and whether it loads an Agent Plugins folder. The Copilot row matches the CLI discovery test. The other rows are the November 16, 2026 ledger plus each tool's skills doc, not a second test you run while reading.

Tool, Project skill folders, Duplicate names, and Loads an Agent Plugins folder? are the four columns. Tool names the client. Project skill folders lists the project paths that client searches, in that client's order. Duplicate names says which copy loads when two skills share a name. Loads an Agent Plugins folder? records whether the client loads that package, and which version the note was checked on. The doc sources are the Copilot CLI plugin reference, Claude Code's skills doc, the OpenCode skills doc, and Pi's skills doc.
- GitHub Copilot CLI reads
.github/skills, then.agents/skills, then.claude/skills, and keeps the first name it finds. It loads an Agent Plugins folder. The result is documented and tested on CLI 1.0.112. - Claude Code reads
.claude/skillsonly. When names collide, the order is enterprise, then personal, then project. It does not load an Agent Plugins folder. Askills/directory loads only because that path matches Claude's own layout. Claude Code ignores the manifest name and a rootmcp.json. The layout note was tested on 2.1.325. - OpenCode reads
.opencode/skills,.claude/skills, and.agents/skills. A later source wins, so the last copy of a name is the one that loads. It does not load an Agent Plugins folder. The result was tested on 2.3.0, and issues #40993 and #41561 were closed as not planned. - Pi reads
.pi/skillsand.agents/skills, keeps the first name, and warns. It has no native Agent Plugins support. A communitypi-agent-pluginspackage adds that.
Copilot keeps the first copy. OpenCode keeps the last. One name in .agents/skills, plus ln -s ../.agents/skills .claude/skills, keeps those two rules from pointing at opposite files.

Copilot, OpenCode, and Pi can read .agents/skills. Claude Code cannot, unless .claude/skills points there. A copy in each favorite folder would make Copilot and OpenCode disagree about which body is real.
If you have used Claude Code: Claude Code reads .claude/skills. The symlink is how this one folder reaches it. You do not keep a second body for Claude. When names collide, Claude's order is enterprise, then personal, then project. Copilot does not use that order.
Do this today
Everyone
.agents/skills/release-checklist/SKILL.mdexists, and.claude/skillspoints at../.agents/skills. The check istest -f .agents/skills/release-checklist/SKILL.md && echo okprintingok, andreadlink .claude/skillsprinting../.agents/skills. Keep one skill name, in.agents/skillsonly. On Windows, iflnfailed, you stopped, and you did not copy the folder.- The second request covers tests,
src/classify.jsstill waiting, and auto-merge off. The first request did not need that body. The check is those two replies on your screen. There is no sample reply. A paid model invocation of this skill was not recorded on November 16, 2026. npm testshowsrefund,shipping,other, andcrushed mug in pieces is other, plus# tests 4,# pass 4, and# fail 0.git diff -- src/classify.jsprints nothing.- The commit is yours.
git log -1 --onelineshowsAdd the Ticket Triage release checklist skill. The agent did not run git. You did not pass--yolo, you did not name a model, and you did not turn on auto-merge.
If you read the folder rules
- Write the project folder order and which copy wins:
.github/skills, then.agents/skills, then.claude/skills, first found wins, then personal~/.copilot/skillsand~/.agents/skills. The check is that order in your note, plus a line that the repo does not contain a secondrelease-checklistskill. - Write that discovery from
.agents/skillsis tested on Copilot CLI 1.0.112, and that a paid invocation of the body was not observed. A note that only says the model followed the checklist on November 16, 2026 fails the check.
The checklist waits until you ask
The failure is a good checklist sitting in the room for every request. GitHub Copilot skills load a name and a description first, and they hold the body until the task matches. "Run the tests" stays a test run. "Prepare the release checklist" earns the three Confirm lines.
One release-checklist under .agents/skills, reached by ln -s ../.agents/skills .claude/skills, is the file you can share. You do not add a twin under .github/skills, and you do not name a model to get through copilot --max-ai-credits 20. Leave with an empty diff on src/classify.js, four passing tests, and a commit you made. Auto-merge stays off. A person merges.
This is Part 9 of "GitHub Copilot, Day-to-Day," a 16-part guide to using GitHub Copilot as a daily coding agent.