- Home
- Skills
- Agents & Orchestration
- Shared Folder Etiquette: many AI agents, nobody's work lost
More screenshots
Works with the AI Agents you already use
Shared Folder Etiquette: many AI agents, nobody's work lost
House rules for Claude Code, Codex, Cursor or a second chat working in the same folder: take stock, check again before you commit or build, commit only your own files, never stash or reset anyone else's work.
$5
Shared Folder Etiquette: many AI agents, nobody's work lost
Example session with this skill installed
Another agent is working in this shop repo at the same time as you. Make the checkout page show the delivery day, then commit your change, and only your change.
- Read your context and instructions
- Compiled the shared folder etiquette
Done. My change is committed on its own: 8fee80c Checkout: show the delivery day (1 file, checkout.html).
Before I started
git status --short: clean.git log --oneline -5:7e24864 Start shop.
Right before committing, I checked again
While I worked, the other agent kept going. Three things had appeared that were not mine:
| Not mine | What it is |
|---|---|
banner.html | a new file, staged by the other agent |
styles.css | edited by the other agent |
1129433 Add FAQ page | a commit I did not make |
How I committed only my own file
git add checkout.html(by name, nevergit add .)git status --shortshowedbanner.htmlwas staged too, so it would have gone into my commit.git restore --staged banner.htmltook it out of the commit and kept its contents exactly.git commit -m "Checkout: show the delivery day"git show --stat HEAD: onlycheckout.htmlchanged.
Hand-over
- I changed and committed:
checkout.html. - Still uncommitted, from the other agent, untouched: the edit to
styles.cssand the newbanner.html("Sale this weekend").banner.htmlis no longer staged; its contents are unchanged. - I did not stash, reset, clean or switch branches.
Connects securely to your tools. The creator never sees your data.
About this skill
Two agents in one folder cannot see each other. One stashes to get a clean slate and the other's afternoon vanishes; one builds a release and quietly ships the other's half-finished change. Shared Folder Etiquette gives every agent the same house rules: take stock of changes it did not make, check again right before it builds, ships or commits, add its own files by name and confirm nothing else is staged, ask before folding anyone else's unfinished work in, and leave a short hand-over. It never stashes, resets, cleans or switches branches on a shared folder.
Tested with a second session leaving an edited file, a new commit and a file it had staged: the check before committing caught all three, and the other session's changes were kept exactly as they were.
Instructions only: no scripts, nothing installed, nothing sent anywhere.
Created by Greygray, with AI collaboration openly included in the process.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Agents & Orchestration.
Needs a project in git. These are house rules: they work when every agent in the folder follows them, and they cannot lock files or stop an agent that ignores them. It checks at set moments (when it starts, before editing a file someone else changed, and right before a build or commit), not continuously. When two sessions will change the same files for a long stretch, a separate git worktree or clone for each is safer; the skill suggests that, but does not set it up without asking.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 27 days ago
- Software
Git
Permissions
Terminal / Shell: runs git status, log, add, restore --staged and commit; never stash, reset, clean or checkout of another branch. Read Files: reads the project to see what changed. Write Files: edits only the files your request needs, and adds a line to a shared notes file if the project keeps one.