Every teammate at the Institute runs their own Claude. With Leslie OS, every one of those Claudes already knows how the Institute works: our programs, our people, our tools, and our conventions. Nobody configures AI from scratch, and nobody gets a version that guesses.
Out of the box, an AI assistant knows nothing about your organization. Ask it to look up a founder, log a coaching note, or build an on-brand deck. It either can't, or it invents an answer.
The usual fix is that everyone teaches their own assistant. That fails twice. Each person repeats the same work. And every assistant drifts in a different direction.
We had already built two AI systems for founders. Our own team was still working with AI that didn't know us.
How It Works
The design rests on one rule: each layer holds the least-changing version of what it needs, and upper layers point to lower ones instead of copying them.
A short block each teammate pastes into their Claude settings. It says who we are, names the baseline tools, and tells Claude to load the master skill for Institute work. It loads in every session, so it stays tiny.
A skill called leslie-os loads only when the work is Institute-related. It orients Claude and routes to the right specialist skill. It points to Notion for facts instead of restating them, so it rarely needs reinstalling.
The live source of truth: programs, people, contacts, and conventions. Claude fetches it at runtime, so it is never stale.
Why the split: without an enterprise plan, nothing can be pushed to every account centrally. So the layer every person maintains is the smallest one, and everything that churns lives in Notion.
Capabilities
Tools and Stack
I designed the architecture and did the integration. This was a team build: other colleagues built several of the skills. My job was to make the parts fit and keep them from drifting.
The hard part was governance, not prompts. Every knowledge page and every skill has an owner and a review cadence. Skills move from Draft to Reviewed to Released. And one rule gets revisited more than any other: facts live in exactly one place.
This is the third AI system I have taken to full adoption at the Institute, after the coaching copilot and the Startup Intelligence System. The first two served founders. This one serves the team.
The core is live: the knowledge base, the six connectors, and eight released core skills. Four skills are still in draft: researcher decks, the coaching playbook, new-cohort setup, and a cross-system data ontology under review. The team keeps filling in the knowledge base.
I don't have impact numbers yet. Adoption came first. Measurement comes next.