just
Skill17 starsChanged 7 days agoMITView on GitHub
Just answer" mode. Use when a message starts with /just, or the user says "just tell me", "don't do it, tell me", "answer only", "audit mode". Answer literally and only the question asked; no edits, no side-effecting commands, no pushes, no "while I was at it", no next-step offers.
- Commits and pushes
7 other projects use a version of this.
Adopted by
Most recently taken up by
- FFatTiger/just-skilltheir own version, first seen Nov 8, 2026
- disler/bowsertheir own version, first seen Oct 8, 2026
- casey/justtheir own version, first seen Oct 8, 2026
- wyattjoh/skillstheir own version, first seen Sep 27, 2026
- asw101/ai-skillstheir own version, first seen Aug 21, 2026
- moabualruz/fulcrumtheir own version, first seen Apr 28, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- casey/just★ 37ksame name
- disler/bowser★ 265same name
- moabualruz/fulcrum★ 4same name
- asw101/ai-skills★ 3same name
- wyattjoh/skills★ 3same name
- CodeWithBehnam/cc-docs★ 2same name
- FFatTiger/just-skill★ 1same 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 repositoryOne other file it gives its agents.
- onboard-projectSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
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 22
Literally: Don't infer an unstated intent.
- Distinctive: line 24
Honest about uncertainty: If it can't be verified without acting, say so: "not checked, because checking requires X."
- Very specific: line 48
After a /just answer, the tool log for that turn must contain no Edit/Write, and among Bash calls nothing but reads.
“Common” is measured: kept by at least 6 in 10 of the 5 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
/just — answer, don't act
Agents are trained to be autonomous: ask "could we…" and they go and do it. This skill flips the mode for one request: answer literally what was asked, then stop.
The rule is small, local and checkable: the tool log for this turn must contain no writing call.
Contract
- Read, never change. Allowed: Read, Grep, Glob, safe
git log/diff/show/status,ls,cat, SELECT queries, web fetch/search. Forbidden: Edit, Write, any command that changes files, the database, the cluster, configs or git history;git pushabove all. If answering seems to require a change, that is an action, not an answer: say what would have to be done, and don't do it. - Only the question asked. "Could we add seven red lines?" → "Yes/no, because…", not the lines. No widening: no "also noticed", no "you should also", no list of next steps.
- Literally. Don't infer an unstated intent. If the question is ambiguous enough that the answers diverge, ask one clarifying question and stop.
- Honest about uncertainty. If it can't be verified without acting, say so: "not checked, because checking requires X."
- Short ending. The answer ends with the answer. No "want me to do it?".
Audit mode
An audit is valuable precisely because it diagnoses without intervening: look, assess, name —
and don't "fix it on the way", because the fix changes what hasn't been measured yet. /just
gives this per request; for a whole session the user says "audit mode", and the contract holds
until lifted ("audit mode off", "you can act now").
Examples
/just will recall break if I delete rerank/.venv?→ "No: recall goes throughmem_opsto Postgres and the embedder; that venv only holds the reranker service's dependencies. The service itself — yes, it will fail." (no commands)/just how many map orphans in myrepo?→ run the read-only check —python ci/freshness.py <repo_dir> myrepo, without--mark, which is the flag that writes — and report the number. Don't fix./just fix the glob→ "That's an action, not a question. Not doing it in /just mode; lift the mode and I will." (don't fix)
Checking the contract
After a /just answer, the tool log for that turn must contain no Edit/Write, and among Bash
calls nothing but reads. If it does, the contract was broken — that is a bug of the mode, not
"helpful initiative".
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.

