Guides · Oct 10, 2026
How to set up a shared agent folder for your team
How to set up one shared folder for a team, with the jobs you repeat, a skill for each and a weekly review that makes the folder smarter over time.
Built by Simon + Claude
TL;DR
- A team folder gives everyone the same context, with the team's jobs, skills for the work you repeat and an agent that knows how you work.
- Share the folder with a changelog and a few rules, so every correction makes it better for the whole team and a new hire starts with all of it.
- Start with one team, one folder and the three jobs that come back every week.
In many teams everyone uses AI on their own. Each person types the same background into a new chat, and the corrections and feedback they give stay in their own history.
How to build AI capital is about why it pays to keep that work in a system you own. This guide shows how to do it in one team, with a sales team as the example.
We use Claude Code in this guide. The same setup works in other agentic tools that work in a folder on your computer, such as Claude Cowork, ChatGPT Work, Codex, Visual Studio Code, Cursor and Antigravity CLI from Google.
The team folder
The system is one folder that the whole team works from, like the sales team's folder at the top of this page. It is the same idea as an agent in a folder, and Claude working from this folder is the team's agent.
CLAUDE.md is the team's onboarding for Claude. It says who the team is, where things are, which skill to use for which job and what the rules are. In Claude Code it is a file in the folder, and in Cowork the folder instructions do the same job.
Where the folder lives. It works best on your computer, where the agent runs scripts on the files. A folder in the cloud also works, such as SharePoint through a connector, but the agent can do less with the files there. A folder on GitHub is the exception, where Claude Code can run scripts in the cloud too.
Easy to switch tools. The knowledge, the systems and the logic sit in the folder, not in the tool. If you build the folder in Claude Code, you can pick up where you left off in Codex the week after.
Codex reads its instructions from a file called AGENTS.md and looks for skills in its own folder, so ask Codex to set that up the first time.
Start with the jobs
We recommend starting with the jobs to be done. That means the work the team has to get done every week, so each skill is built for a real job. Let Claude interview the person who knows the work best.
Sales team jobs
One question at a time. What does the team do every Monday?
We pull the pipeline report from the CRM and follow up everyone we met last week.
What happens after a client meeting?
Whoever ran the meeting writes a proposal. It should go out within two days.
Thank you. Each job is written down with how often it comes, who does it today and what a good result looks like. jobs.md, 9 jobs
Reply to Claude
YouInterview me about the jobs our sales team does every week, month and quarter. Ask one question at a time. Then write jobs.md with each job, how often it comes, who does it today and what a good result looks like.
Mark the three jobs that come back every week. Those three are where you start. With the jobs written down, let Claude set up the rest of the folder.
YouSet up this folder as a shared workspace for our sales team. Suggest a structure with a CLAUDE.md, a folder for our context, skills, examples, output and a learnings.md, based on jobs.md. Show me the plan before you create anything.
Share the folder
Many of our clients share the folder through SharePoint or Google Drive, as a quick way to get started. Claude works in the folder on each person's computer, and everyone has the same files.
The team needs a few rules for working in the same files. If two people change the same file at the same time, you can end up with two versions of the file, and someone has to merge them by hand. Anthropic does not document shared folders, so agree who edits which file and keep backups.
Let Claude interview you about how the team will share the folder.
YouWe plan to use this folder as a team agent, shared in SharePoint. Interview me about how we will work with it, one question at a time. Then write a changelog.md where every change to CLAUDE.md and the skills gets a date and a name. Add rules for working together to CLAUDE.md, or to our folder instructions in Cowork, such as who edits which file and how we avoid two people writing at once.
A skill for each job
A skill is one job done the way the team's best person does it, with the checklist the work has to pass. Build it from examples of work that went well. Skills in Claude Cowork shows how to make one.
Skills are not the same as agents. A skill describes how a task is done. An agent is a role, such as a researcher or a reviewer, and one agent can use several skills. In Claude Code the team's agents sit in their own folder, .claude/agents, next to .claude/skills.
YouMake a skill for our proposals from the three winning proposals in examples. Write when to use it, the sections a proposal always has, what we never promise, and the checks before it goes to a client. Ask me about anything unclear.
Keep the skill's file in the team folder so the whole team can read it, in .claude/skills when you use Claude Code. In Cowork the owner adds it in Customize > Skills and shares it with the team, and only the person who shares a skill can change it.
With the proposal skill in place, anyone on the team runs the job with one line, and Claude takes the rest from the folder, the skill, the client files and the examples.
Proposal for Company B ⌄
Sales teamWrite a proposal for Company B from today's meeting notes.
- Read CLAUDE.md
- Read context/clients/company-b
- Used skill proposal
- Checked against the checklist, fixed two points
- Saved output/proposal-company-b.docx
AssumedStart date in November
YouWrite a proposal for Company B from today's meeting notes with our proposal skill. Check it against the checklist, save it in output and list what you assumed.
Four kinds of work
A proposal is a job on request, one of four kinds of jobs in jobs.md.
Rhythm jobs run on a schedule in the cloud, and a job that uses the team folder on your computer needs the desktop app open and the computer awake. Connectors and automation shows how. For a big job like a tender response, a team of agents splits up the work.
YouEvery Monday at 7, write the pipeline report from the CRM with our pipeline skill and save it in output.
Build small tools for the team
Claude can also build small tools and dashboards in HTML for the work the team does, and keep them in the folder next to the skills. Anyone on the team opens them in a browser. Read more in our guide to the magic powers of HTML.
For a sales team, one example is a tool for MEDDIC, a checklist sales teams use to decide which deals are worth their time. Each letter is a question to answer about the customer, such as who holds the budget and what problem they need solved.
YouBuild an HTML tool in the tools folder for qualifying a deal with MEDDIC. One row per letter with a score from 0 to 2 and a note, the total at the top, and the next step for the weakest row. Add a button that copies a short summary for the CRM.
Save your feedback
The folder gets better when corrections go back into it. Each time someone fixes a draft, the fix becomes a dated line in learnings.md.
YouUpdate learnings.md based on our conversation and the feedback provided.
Once a week the owner reads the new lines and makes the next few changes to the skills and CLAUDE.md.
YouRead this week's work in output and the new lines in learnings.md. Suggest the three changes to our skills or CLAUDE.md that would save the team the most time next week. Show them to me before you change anything.
How team knowledge compounds
Over months the saved corrections add up. What used to sit in one person's head ends up in the folder, where the whole team can use it. A new hire gets it on day one, and it stays when someone leaves.
YouRead learnings.md, changelog.md and output from the last three months. Tell me what the team knows now that it did not know three months ago, and which knowledge still lives in only one person's head.
Share the folder through GitHub
As the team grows, a more advanced way to share the folder is GitHub, a service where developers keep shared work with a full history of every change. The team folder lives there, and each person has a copy on their own computer.
When someone improves a skill, they send the change to GitHub, and the others fetch it. Every change is saved with a name, a date and a note, so the history does the job of the changelog. The owner can also approve a change before it reaches the rest of the team, on a paid GitHub plan.
From team to department and company
Each team keeps its own folder, and every team reads the same company folder. Skills every team needs go in the company's skill library, set to require review so an owner approves each one. When one team hands work to another, it hands over a file.
Your first four weeks
Today, run the jobs interview with the person who knows the team's work best.
