For those who scale it

The Operating Model

How an organisation actually runs agents — the layer between strategy and code.

Capability becomes an asset only when it is reusable, governed, and findable.

Skillsthe reusable unitAgent Catalogthe registryPower Usersthree-tier distributionCoE & Enablementthe governing bodyAdoption Patternsthe failure modespublishconsumegovernscuratesenablesmitigatesCapability becomes an asset only when reusable, governed, and findable.
01
Skills as the Reusable Unit
The open standard that turns capability into a versioned, governed inventory.
02
Power Users vs Consumers
The three-tier distribution — and where governance most often fails.
03
The Agent Catalog
Internal registries for agents, skills, and tools — owned, scored, risk-tiered.
04
CoE & Enablement
Hub-and-spoke vs federated. The platform team as velocity engine.
05
Adoption & Failure Patterns
The adoption cliff, the scaling cliff, the governance gap.

Worked example — Skills

Pillar III · The Craft

Build the skill

The practitioner defines a SKILL.md with metadata, scripts, and references — a portable, versioned unit of capability.

Pillar II · The Operating Model

Govern the catalog

The org registers skills in a searchable registry, scores them, and gates which tiers of users can deploy them.

Pillar I · The Groundwork

Set the reuse policy

Leadership mandates that all AI capabilities ship as skills — versioned, governed, and findable across teams.