Use case · Skills
Our best agent skills live on one laptop. Give each engineer the same catalog on every machine.
Keep your team's skills in one GitHub repo. Each engineer imports it once, and the skill that matches loads on every machine they use. Import again to update.
The team's best skills sit in one home folder.
Built into each agent
- SKILL.md files on each machine or repo
- Copied by commit, plugin or admin folder
- A folder for each agent
One catalog on your account
- Imported from your team's GitHub repo
- One catalog for both agents
- Nothing written to the disk
Each machine or repo needs its own copy. Context Mode keeps the skills on the gateway.
Put the skills in a GitHub repo. Import it once.
// console → Skills https://github.com/your-org/agent-skills → Preview import → Add all
Large repos import in batches. Import again to update.
A teammate imports the same repo on their account.
// their console → Skills https://github.com/your-org/agent-skills → Preview import → Add all
Same repo, same skills. When the repo changes, each of you imports again.
“Since this morning our blog URLs end with a dash. … the test suite is red. … Figure out what broke and fix it.”
⏺ context-mode · skill diagnosing-bugs auto-loaded
Nobody typed a skill name. The reply names the skill that loaded.
“Walk me through how slugify turns a title into a slug, step by step.”
This question matches no skill, so none loads. If the match is weak, no skill loads.
Right skill picks on 10 texts, offline.
Small sample, judged by one person. Treat it as direction.
One engineer wrote the skills. The rest of the team never gets them.
The agent loads skills from SKILL.md files. Each machine or repo needs its own copy, by commit, plugin or admin folder.
Claude Code and Codex read skills from different folders. A team that uses both keeps a copy for each.
In each agent, the model loads a skill when its description fits, using only the files on that machine.
From a repo to every agent. No files to sync.
- 01Put the skills in a GitHub repo
One folder per skill, each with a
SKILL.mdand a clear description. - 02Each engineer imports it once
In the console, open Skills, paste the repo URL, click Preview import, then Add all. The catalog is one per account, and there are no team roles yet, so each engineer imports the same repo. Import again to update. A skill body can be 262,144 bytes at most.
- 03The right skill loads
On every machine you use, Context Mode compares each message with each skill. At most one loads per turn, and the reply names it.
The right skill, or none. Named in every reply.
| Context Mode | Built into each agent | |
|---|---|---|
| Where skills live | One catalog on your account | Files on each machine or repo |
| New laptop | Ready at once on your account; each teammate imports the repo once | Commit, plugin or admin folder on each machine |
| Claude Code and Codex | One catalog for both | A folder for each agent |
| Which skill loads | The one that matches, named in the reply | The agent decides |
Skill picks: an offline eval on 10 texts, judged by one person. Treat the numbers as direction, not as live accuracy. We have not measured whether skills give better answers. The catalog is one per account; there are no team roles yet, so each engineer imports the same repo, and imports again after a change. Method and sources →
What this uses.
Import from GitHub once per account. The skill that matches loads, one per turn at most.
Import, matching, the reply line, cost, and a 5-minute test.
The judge, the 0.5 floor, and what we have not measured.
Write a skill once. Every teammate uses it.
npx @context-mode/cli connects your agents. 1,000 requests free, no card.