compass
Skill312 starsChanged 10 days agoMITView on GitHub
Record the decision just made into compass, the rated decision store, with the user's rating (good, bad, impressive, interesting) and note. The user fires it when they notice a decision worth keeping.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- mqmalagris/agent-skillstheir own version, first seen Nov 5, 2026
- me-cedric/agent-compasstheir own version, first seen Nov 1, 2026
- BarganConstantin/agent-skillstheir own version, first seen Nov 1, 2026
- norrietaylor/distillerytheir own version, first seen Nov 1, 2026
- spacedock-dev/spacedocktheir own version, first seen Nov 1, 2026
- luci-efe/skillstheir own version, first seen Nov 1, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- simota/agent-skills★ 96same name
- spacedock-dev/spacedock★ 85same name
- norrietaylor/distillery★ 25same name
- BarganConstantin/agent-skills★ 4same name
- Zenobia000/agent-skills-starter★ 4same name
- me-cedric/agent-compass★ 3same name
- Aether-liusiqi/compass★ 2same name
- healthier-vitamins/agentic-grimoire★ 2same name
- chrisjay629/compass★ 1same name
- jaysu66/atria-skill-library★ 1same name
3 more not listed
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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/AGENTS.mdAGENTS.md
- memoSkill
- prepSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 39
If the decision the user means is ambiguous, ask before storing.
- Very specific: line 40
Before a real fork later, you can drone @devpulse compass query "<topic>" to see how similar past decisions were rated.
“Common” is measured: kept by at least 6 in 10 of the 9 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
Compass — Record a Decision
Purpose: Capture the decision just made into compass (the rated decision engine) with the user's rating and note. The user fires this when they notice a decision worth recording — they supply the judgement, you supply the decision text from the conversation. This is the human-triggered answer to the "noticing" problem: the user notices, you describe and store.
Usage: /compass <rating> <note> in Claude Code and OpenCode, $compass <rating> <note> in Codex — rating is one of: good, bad, impressive, interesting.
Examples:
/compass good chose to continue the dead agent instead of starting fresh/compass bad reached into the branch instead of dispatching/compass impressive(rating only — you write context, decision, and note from the conversation)
Arguments: the words the user typed after the command name.
Execution
- Parse the words after the command name:
- First token =
rating. It MUST be one ofgood | bad | impressive | interesting. If it isn't, don't guess — ask the user which rating they meant and stop. - Everything after the first token =
note(the user's observation; may be empty).
- First token =
- From the recent conversation, identify the decision being rated. Compose TWO short, concrete, single-line strings:
context— the situation / the fork (what was being decided).decision— what was actually chosen. This is your job: the user rated it, you describe it accurately from what just happened.
- Store it (source is
user, since they triggered the rating):
Omitdrone @devpulse compass add "<context>" "<decision>" --rating <rating> --note "<note>" --source user--noteif the note is empty. - Confirm in one line: the rating, the decision recorded, and the new id.
Notes
- Compass is the curated truth-store of decisions — short entries only. Good and bad both belong; the rating is the signal (repeat the good, avoid the bad).
- Compass is separate from @memory. Do NOT also write this to
.trinity/or memory — different store, different purpose. - If the decision the user means is ambiguous, ask before storing. One good entry beats a vague one.
- Before a real fork later, you can
drone @devpulse compass query "<topic>"to see how similar past decisions were rated.
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.