Everyone is building skills right now. ReusableReuseThe same practice serving many times, across many spaces, the key measure of the Practice Graph's value. capabilities an agent can call: can draft a proposal, can analyze a contract, can follow up with a prospect. It's modular, it's handy, and it's a good thing. But it's also the moment to draw a distinction the trend erases: a capability isn't a practice.
A skill is a packaged capability, a reusable building block. In our CREW grammar (Concepts, Roles, Environments, Workflows), it's the C: a Concept, a component. A prompt, a tool, a block of content. Useful, yes. Sufficient, no.
Because a skill, alone, has no notion of who is accountable for it, where it lives, how it's validated, how it evolves. A skill that anyone executes, with no version, no expert to endorse it, no environment, no validation stepValidation stepA stage in a publication's path (draft → review → approved), with rules that gate each transition., is exactly the C of CREWCREWMarylink's governance framework (Concepts, Roles, Environments, Workflows) grounded in research. stripped of the R, the E and the W. It's a brick lying on the ground. It can do the work. No one knows if it's the right brick, nor who laid it, nor whether it changed since yesterday.
What a practice adds is precisely the three letters that are missing.
The R, roles: who wrote this practice, who validated it, who is allowed to use it. Accountability. An anonymous skill commits no one. A practice is attributed, endorsed, held by someone.
The E, environments: where the practice lives. In which spaceSpaceA workspace by domain or topic where a team publishes, shares and governs its practices., for which team, internally or for a client, partitioned. A skill floats rootless. A practice is situated, and its context is part of what it is.
The W, workflows: the steps it goes through. How it goes from draft to validated, how it's reviewed, how it improves with use. A skill is frozen until someone silently rewrites it. A practice has a trajectory, a history, an authoritative version.
The Practice GraphPractice GraphThe living architecture that links your practices, concepts, roles and spaces, executable by your teams and by AI. doesn't replace skills. It wraps them in governanceGovernanceThe roles, validation steps and reviews that ensure the quality of shared practices.. It takes the capability, the C, and adds who is accountable for it, where it lives, and how it evolves. It's the difference between “an agent can do that” and “an agent executes our validated way of doing that, and it improves.”
And that's exactly where it counts, in 2026. As agents multiply, the bottleneck is no longer capability. Skills will be everywhere, and good ones. The bottleneck becomes trust and governance. A skill no one endorses, with no version, no context, is precisely what a CIO cannot deploy at scale, because they cannot be accountable for it.
The practice is what makes the skill deployable.
A skill answers one question: can my agent do that.
The real question, to deploy it at scale: who is accountable for it, where does it live, who validated it, and how does it evolve?