The skill economy
Five briefs, roughly 14,000 words, and the one cluster with dated external validation.
The base vault — the unit of the economy
“a skill, done properly by a creator, is a ‘base vault’ holding far more than a SKILL.md: all the materials that make the skill explainable, trustworthy, and executable. The creator takes the time to create, collect, and curate this base vault; it is the canonical, complete expression of their skill.”
This is the vault-as-substrate architecture (standards.sgit.ai) applied to skills: the vault holds the sources, the reasoning, the provenance and the executable form; the SKILL.md is a projection of it — the same projection idea as the graph page, applied commercially rather than architecturally.
What is actually being sold — the cascade
“you have the fundamental first repo-like structure or vault that is used to create the customised version, which is what you sell… more interesting is the customised version, the one developed, certified, and maintained by the creator… that is fundamentally what you sell, you maintain it, and that is the one that has the intellectual property element.”
The finance brief makes the cascade concrete: the corporate skill → the group version → the cybersecurity version → the ethics-response-team version — with the observation that “the existing 20-to-200-page finance document does not work” precisely because it cannot cascade the way a forked, versioned skill can.
The economics here are the villagers argument (open-source.sgit.ai): pay the owner of the skill because it is cheaper than maintaining your own understanding. Same value margin, applied to knowledge instead of code.
Distribution — ride the aggregators
The Tessl brief is a real case, in real conversation: “can a vault layer take skills from an aggregator like Tessl, add value (a vault, customisation, maintenance, token handling), and create monetisation paths that reward the skill’s creator?” The position: the aggregator grows the market; the vault layer adds provenance, customisation and maintenance on top; the creator gets paid through the layer rather than despite it.
Scoring — the differentiator
From the marketplace research: today’s marketplaces score on “GitHub stars, install counts, update cadence, and security scans” — and notably, update cadence ranks skills higher in most storefronts than star ratings. The gap the vault can fill:
“trustworthy scoring grounded in cryptographic provenance, evals, and an auditable graph, rather than gameable popularity.”
That sentence is the whole competitive position, and it depends on two things the estate has (provenance, vaults) and one it does not: evals — G3.
The OWASP expert case
“say you are an OWASP leader or member with a good reputation for a certain set of application-security skills… one of the challenges today is that you do not have good revenue streams easily, apart from working for companies or doing consulting. That is where skills come into play, because you should be selling those skills.”
Shared with open-source.sgit.ai, which owns the OWASP monetisation thread; this site owns the mechanism — base vault → certified version → maintained customisation.
The validation, dated
“one of the feedbacks I got today at the conference is how it’s a powerful workflow and solution for us, and the vaults are perfectly aligned with that, perfect for capturing skills, version-controlling skills, and customising and selling skills.”
External, real-world, recorded the same day (1 June 2026). Small, but it is the only market signal in the cluster, and it is cited here as exactly that — one signal, not proof.