sageox
Skill13 starsChanged 39 days agoMITView on GitHub
What SageOx is and how to use it in this repository: load team context at session start, record the session, and reach the team's shared knowledge. Read this when you see a .sageox/ directory, when someone mentions SageOx or the ox CLI, or when ox-cli-* skills are referenced but missing.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- sageox/oxword for word, first seen Jun 11, 2026
Other versions1 project uses a version of this.
Word for word · 1
- sageox/ox★ 68100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-avatarSkill
- agent-bringupSkill
- monitor-prSkill
- sageoxSkill
- agent-avatarSkill
- agent-bringupSkill
- monitor-prSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Run it at session start — it is fine to read the user's request first — and again after a context compaction or clear.
- Distinctive: line 35
If they are referenced but absent:
- Distinctive: line 60
When SageOx-delivered context measurably changed what you did, credit it.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SageOx
This repository uses SageOx: shared context infrastructure for teams whose coworkers are both human and AI. Architectural decisions, team conventions, and the history of prior sessions are available to you here — you are not starting from zero.
This is the repository's fallback SageOx skill: the orientation a coworker gets
when the ox CLI is not installed, and the ox-cli-* skills it would have
placed are therefore absent. It is deliberately small and stable for that
reason — it has to stand alone.
Start every session with prime
ox agent primeRun it at session start — it is fine to read the user's request first — and again after a context compaction or clear. It
loads team conventions, architectural decisions, prior sessions from teammates,
and your agent identity. Most other ox commands need that identity.
The rest of the SageOx skills are installed locally, not committed
You may see references to skills named ox-cli-* — ox-cli-plan,
ox-cli-consult, ox-cli-recap, and others. Those are installed on this
machine by the ox CLI and are deliberately not committed to the
repository, so upgrading ox never puts vendor files into anyone's pull request.
If they are referenced but absent:
ox doctor --fixThat materializes the current set. If ox itself is missing, install it first —
everything below degrades gracefully without it, and this file is still the map.
Reaching the team's knowledge
| When you need | Run |
| Team context at session start | ox agent prime |
| Prior work on a topic | ox query "<question>" |
| Code symbols and git history | ox code search "<query>" |
| Team decisions and conventions | ox agent team-ctx |
| Health check | ox status / ox doctor |
Being a good teammate
Your work is visible to the team, and theirs to you. When you start something
substantial, say so — ox murmur --topic=wip "<what you're building>" — and read
the murmurs that reach you, so two coworkers don't rebuild the same thing twice.
When SageOx-delivered context measurably changed what you did, credit it. When it did not, add nothing: invented attribution is worse than none.
Beyond the CLI
SageOx is the product; ox is one surface of it. The same team context is
reachable through the SageOx MCP server and the web app, so a coworker who never
installs the CLI still gets the shared picture. That is why this skill is named
for the product rather than the binary.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

