workspace-status
Skill1 starsChanged 2 months agoMITView on GitHub
Use when the operator asks for constellation / multi-repo NEXT authority, types /workspace-status, or before pasting a NEXT prompt from a multi-root workspace. Show which member owns **product_order** PRIMARY and whether relay tips are fresh. Focused editor tabs are not authority. Exit 35 (WORKSPACE_RELAY) means stale/ambiguous/missing relay integrity. Single-repo ok status green does not imply workspace.ok. Prefer {REPO_SLUG}-OVERSEER-HANDOVER.md / {REPO_SLUG}-ROADMAP.md so multi-root tabs are distinct. Doctor reports board_name_violation for bare legacy names under strict_board_names.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- eugenelim/agent-ready-repotheir own version, first seen Nov 14, 2026
- phanijapps/memextheir own version, first seen Oct 17, 2026
- JetXu-LLM/DocMasontheir own version, first seen Oct 8, 2026
- patricio0312rev/workspacestheir own version, first seen Jan 25, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- JetXu-LLM/DocMason★ 152same name
- eugenelim/agent-ready-repo★ 31same name
- patricio0312rev/workspaces★ 9same name
- phanijapps/memex★ 0same name
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 repository26 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .cursor/rules/build-verification-required.mdcCursor rule
- .cursor/rules/check-ok-thinking.mdcCursor rule
- .cursor/rules/governance-sync.mdcCursor rule
- .cursor/rules/l1-checkpoints-consumer-owned.mdcCursor rule
- .cursor/rules/no-docs-only-pr-to-main.mdcCursor rule
- .cursor/rules/orchestrator.mdcCursor rule
- .cursor/rules/print-next-closeout.mdcCursor rule
- .cursor/rules/tier-authority.mdcCursor rule
- .cursor/rules/workspace-authority.mdcCursor rule
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- governance-syncSkill
- print-nextSkill
- workspace-statusSkill
- build-verification-reviewSkill
- check-okSkill
- deploy-verification-reviewSkill
- freeze-review-loopSkill
- freeze-reviewSkill
- governance-syncSkill
- knowtationSkill
- print-nextSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 0 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Use when the operator asks for constellation / multi-repo NEXT authority, types /workspace-status, or before pasting a NEXT prompt from a …
- Very specific: line 26
Prefer {REPO_SLUG}-OVERSEER-HANDOVER.md / {REPO_SLUG}-ROADMAP.md so multi-root tabs are distinct.
“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Workspace status skill
Use when the operator asks for constellation / multi-repo NEXT authority, types
/workspace-status, or before pasting a NEXT prompt from a multi-root workspace.
Purpose
Show which member owns product_order PRIMARY and whether relay tips are fresh. Focused editor tabs are not authority.
CLI
./cli/ok workspace status
./cli/ok workspace status --json
./cli/ok workspace check-next
./cli/ok workspace doctor
./cli/ok status --workspace --exit-codeExit 35 (WORKSPACE_RELAY) means stale/ambiguous/missing relay integrity.
Single-repo ok status green does not imply workspace.ok.
Board filenames
Prefer {REPO_SLUG}-OVERSEER-HANDOVER.md / {REPO_SLUG}-ROADMAP.md so multi-root tabs
are distinct. Doctor reports board_name_violation for bare legacy names under
strict_board_names.
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.

