Case study § 07

Claude Code skills ecosystem for a team

Platform · MCP · 30+ skills · team tooling · execution boundaries

Context

Moving from individual use of Claude Code to an agentic workflow shared across a whole team, reproducible: that's the starting point, once the tool is adopted beyond a single seat.

More than 30 skills, built for a team rather than a single seat, cover document production, research, orchestration and MCP servers.

In the background, an onboarding constraint: an install script, an onboarding README and a CLAUDE.md template per engagement.

The point is not to add one more skill: it's to reason about execution boundaries so the tooling holds at team scale, not just for a single seat.

The system

An explicit boundary organizes the whole thing: what runs inside the agent on one side, what stays usable on the conversational-assistant side on the other.

Diagram: Claude Code skills ecosystemThe Obsidian vault, a memory of versioned markdown files, talks both ways with the Claude Code orchestrator, which activates an ecosystem of more than thirty skills grouped into document production, research, orchestration and MCP servers, to equip the whole team. A tooled install, script, README, template, feeds that ecosystem. The team's work then updates the vault's memory in return.VAULT UPDATEMEMORYOBSIDIAN VAULTVERSIONED.MD FILESORCHESTRATORCLAUDE CODESKILLS · 30+DOCUMENTPRODUCTIONRESEARCHORCHESTRATIONMCP SERVERSTEAMINSTALLINSTALLSCRIPTONBOARDINGREADMECLAUDE.MDTEMPLATEDiagram: Claude Code skills ecosystemThe Obsidian vault, a memory of versioned markdown files, talks both ways with the Claude Code orchestrator, which activates an ecosystem of more than thirty skills grouped into document production, research, orchestration and MCP servers, to equip the whole team. A tooled install, script, README, template, feeds that ecosystem. The team's work then updates the vault's memory in return.MEMORYOBSIDIAN VAULTVERSIONED .MD FILESORCHESTRATORCLAUDE CODEINSTALLINSTALL SCRIPTONBOARDING READMECLAUDE.MD TEMPLATESKILLS · 30+DOCUMENT PRODUCTIONRESEARCHORCHESTRATIONMCP SERVERSTEAMVAULT UPDATE
DIAGRAMThe vault as versioned memory, an orchestrator that activates the skills: the loop that equips a whole team.

Equip a team, not just yourself: the principle holds for the whole ecosystem, from the skills themselves to how a new engagement inherits them.

Decisions & trade-offs

Key decision

More than 30 skills, automatic install, an onboarding README, a CLAUDE.md template per engagement.

More than 30 Claude Code skills for a team: document production, research, orchestration, MCP servers. With an install script, an onboarding README and a CLAUDE.md template per engagement.

Trade-off

Separate what runs inside the agent, skills, hooks, MCP, from what stays portable on the assistant side.

The architecture separates what runs inside the agent, skills, hooks, MCP, from what stays usable on the conversational-assistant side.

Result

A platform for a team, not a throwaway script.

What it shows

Equipping a team on an agentic workflow and reasoning about execution boundaries.