Short answer
A Claude setup going stale is still running but no longer matches your business: old instructions, hidden skills, projects tied to people who left. You’ll be able to check your own setup for five plain signs and decide what to fix first, using the same look I take at CoworkConsultant.com before I change anything for a client.
Your team opens Claude every day and nothing is broken, so nobody looks. Most owners judge a setup by whether it still answers. That’s almost right. It can answer every question from last spring’s price list and last year’s team.
This isn’t a rebuild, and it isn’t the monthly owner routine I hand over. It’s the diagnosis that tells you whether you need one.
| Fact | What it means for a stale check |
|---|---|
| Project instructions shape every chat in that project | They only change when someone edits them |
| Chats don’t share context unless it’s added to project knowledge | A fix in one chat never reaches the next |
| A custom skill is visible only to its creator until shared | Good work sits on one account |
| A removed member’s private projects are closed to everyone else | Work tied to a leaver is out of reach |
| Archiving a shared project keeps its members and permissions | Archive is tidying, not access control |
Sources: Anthropic’s overview of projects and what happens to a removed member’s data, plus its help articles on sharing and skills.
Five Signs of a Claude Setup Going Stale
When I set this up for a client, I check these five before I touch a single setting.
- Instructions nobody has edited since the services or team changed.
- Knowledge files older than the work, so staff paste background into every chat.
- Skills only one person can see, built by a colleague and never shared.
- Private projects owned by someone who left, or is about to.
- Archived projects with the old team still on them.

Two or more means the setup has drifted. You don’t need a new tool, you need the setup back in line with the business. Not sure which apply? Book a short call with CoworkConsultant and I’ll go through the list with you.
Check Claude Project Instructions Against Today’s Business
Project instructions apply to every chat in the project and stay exactly as written until someone edits them. Chats don’t learn from each other either: a correction stays in its chat unless someone adds it to project knowledge.
Let me give you an example. You open your proposals project and read the instructions. They still describe the services you sold last year, and the knowledge files still hold the old scope template. Paste the instructions into a new chat with today’s services page attached and ask Claude to compare them. It comes back with a short list: the retired service, the discount you stopped offering, the template section that no longer exists. That list is your edit.
If yours need a fresh start rather than a patch, here’s how a small team writes project instructions in one voice.
Find the Skills Nobody Shared
A custom skill someone uploads is visible only to them until they share it. Admins see skill names and sharing status, not the files. The colleague whose proposals always come out right may simply have a skill nobody else has.
Ask each person which skills they built themselves. Share the useful ones, or publish them to the organization. Shared skills are view-only for recipients, and they get the creator’s updates at next use.
Here’s how I set up custom Claude skills by role. Several skills growing into one job is often a plugin, which my custom plugin build handles. Larger teams can look at custom plugin development on Strategized.ai.
Look at Who Owns Your Claude Shared Projects
Once a member is removed, nobody else can open the projects they kept private. Projects they shared with the organization stay available. The creator can switch a project between private and the whole organization from its Share button at any time, so fix it while that person is still on the team.

Archiving is the other trap. It doesn’t remove anyone or change permission levels, and the knowledge stays. To cut someone off, remove them in the project’s sharing settings.


If someone has already left, read what happens to an employee’s Claude chats and files. If it was your consultant, use the handoff after a consultant leaves.
The honest part: if you’re the only person in your Claude account, the last two signs don’t apply. Check your instructions and files and you’re done. Nobody needs to be hired for that. If the signs come from headcount instead, read whether you have outgrown the setup or the plan.
Michael’s take
A stale setup costs a small business quietly. Nobody complains. They stop trusting the answers and go back to doing the work by hand. The fix is rarely a new feature. It’s putting the setup back in line with the business and naming who owns each piece. That’s most of what I do as a Claude Consultant, and it’s work an owner can learn to keep up.
Run the Stale Check This Week
- Open your busiest projects and read the instructions out loud.
- Ask each person which self-built skills they use, and share the good ones.
- Move any private project owned by someone who is leaving to the organization.
- Open your archived projects and remove anyone who shouldn’t still have access.
Prompt: check Claude project instructions for stale lines
Below are the instructions from one of my Claude projects. Attached is my current services page. List every line in the instructions that mentions a service, person or process missing from the page, and every service on the page the instructions never mention. Quote each line exactly. Don't suggest new wording yet.
Claude returns two short lists. Check each line before you edit, because only you know which differences are on purpose.
Want the stale spots fixed and an owner named for each one? That’s part of the Owner Build and Team Setup. Book a free 20 minute call, open calendar, day or night, and you’ll leave knowing which of the five signs to fix first.
Frequently Asked Questions
What are the signs of a Claude setup going stale?
Old instructions, outdated knowledge files, unshared skills and projects tied to people who left. At CoworkConsultant.com, I check those before changing anything on a client’s setup.
Do Claude project instructions share context between chats in the same project?
No, and at CoworkConsultant.com it’s the first thing I explain to owners: instructions reach every chat in the project, but details from one chat stay in that chat unless someone adds them to project knowledge.
Why doesn’t a colleague’s skill show up in Claude organization skills?
Usually because it was never shared. At CoworkConsultant.com, I check this first: a custom skill someone uploads stays visible only to them until they share it with colleagues or publish it to the organization.
Is archiving Claude shared projects the same as revoking access?
No. At CoworkConsultant.com, I remind owners that archiving keeps every member, permission level and the project knowledge in place; to cut someone off, remove them in the project’s sharing settings.
