The Iceberg of Skills

When I finally asked my team who was using AI skills, the answer was seven out of nine. Not a pilot group. Not the two enthusiasts. Nearly everyone — already writing skills, already firing them daily.

So why did it feel like nothing was shared? Because almost none of those skills had ever been seen by a second person. They lived in personal ~/.claude directories: private, unlisted, helping exactly one person at a time. My team didn’t have an adoption problem. It had a visibility problem.

That’s the iceberg. The visible peak is what your company officially ships to everyone. The mass — the experiments, the workflows, the small automations people quietly built for themselves — is underwater. No culture poster has ever raised an iceberg. What raises skills is a promotion path: a map of where skills live, one rule for placing them, and a ladder they climb when they prove themselves.

By the end of this playbook you’ll have: a published four-layer map, a promotion rule your team can quote from memory, one skill firing for every person, and a sharing loop whose first agenda filled itself.

The map: four layers

Layer 1 — the meta plugin. One plugin, installed by everyone. The base instructions every agent in the company should carry: how you write docs, how you handle customer data, what your internal terms mean. The peak of the iceberg — everyone sees it, everyone inherits it.

Layer 2 — role plugins. One per role: Sales, Customer Success, Tech Lead. A person installs the couple that match their actual work. These carry the distilled workflows of the role — the follow-up writer for Sales, the escalation summarizer for CS — so a new hire inherits the role’s best tricks on day one instead of year two.

Layer 3 — project plugins. Long-running projects get their own. Skills built by the people on the project, for the people on the project: the conventions, test patterns, and deploy rituals of that specific codebase.

Layer 4 — personal skills. ~/.claude. Experiments and works-in-progress. Auto-loads for exactly one person, invisible to everyone else. This is the underwater mass — and at most companies, it’s where the best material is stuck.

The one rule: a skill lives at the narrowest layer that covers everyone who needs it. Promotion is what happens when a skill’s audience outgrows its layer — personal → project → role → company, one rung at a time.

Step 1 — Audit the underwater mass

Before building anything, find out what already exists. Ask every person one question: what’s in your personal skills folder? Not “would you like to share something” — just an inventory. Half the answers will start with “it’s probably nothing, but…” Those are the ones you want. People undersell their own automations; “probably nothing” is where the promotion candidates hide.

Checkpoint: a written list of existing personal skills, each with a person’s name attached.

Step 2 — Publish the map

Write the four layers on one page: what each layer holds, who installs it, one example each. State the placement rule next to it. Then resist the urge to scaffold everything at once — create the meta plugin and the one role plugin where the audit found the most material. The other layers earn their existence when a skill actually needs them.

Checkpoint: the map lives in your handbook, linked from wherever your team actually looks — not in a deck.

Step 3 — Set the promotion rule

A skill moves up when it has helped its owner three or more times. Three is the threshold between a real workflow and a one-off. Then two moves: a PR into the layer above (next to the work it describes), and a short announcement to the people who just inherited it. The announcement isn’t ceremony — it’s the difference between a skill that exists and a skill that fires.

And every skill keeps exactly one owner. A person, never “the team.” When it breaks or drifts, someone’s name is on it.

Checkpoint: the rule is written where contributions happen — the plugin repo’s readme — and your team can recite it: three fires, one PR, one announcement, one owner.

Step 4 — Seed the peak

An empty meta plugin teaches everyone that the map is theoretical. Ship it on day one with a single undeniable skill — one thing every role touches weekly. Ours was documentation writing: the skill knows how we write and where each kind of doc goes. Pick your most universal pain, and pick only one; the peak is seeded by quality, not volume.

Checkpoint: one skill firing for every person in the company within a week of publishing the map.

The map gives skills an address. The loops give them a reason to move. You need two: one inside each department, where role-plugin candidates surface among people who share a workflow — and one across the org, where meta-plugin candidates and the war stories go.

The format is yours. Four properties are not negotiable:

Fixed cadence — a predictable ritual beats an inspired one that dies after two runs.
The agenda comes from member submissions, one line each, and it is never blank: if nobody applies, the host pulls candidates from the audit list. “Nothing to share, let’s skip” is how loops die.
Failure stories outrank demos. “Where AI betrayed us” saves everyone the same burn.
The host rotates. The loop belongs to the team, not to you.

(Parameters, sample-size-one: nine engineers, sixty minutes, once a month keeps the ladder moving.)

Checkpoint: the first agenda filled itself before the first session happened.

Step 6 — Run the first cycle, and go first

At session one, you present — and you bring a failure. Mine was an autobug fixer I’d triggered on every issue; it simulated activity, spammed the tech lead, and helped nobody. The lesson was worth more than any demo: scope it to where it can actually help. A room’s honesty calibrates to its most senior person, and if you open with a polished win, everyone after you will too. Then the loop becomes a showcase, which is a slower way to die.

After the session, harvest. Every skill shown is a promotion candidate; ask each presenter for the PR while it’s warm.

Checkpoint: the first promoted skill merged within a week of that session.

The 30-day scoreboard

Working is countable:

the audit list exists, with names
the map is published and the meta plugin is installed by everyone
at least one skill has climbed a full rung — personal to project, or project to role
session two’s agenda filled without you chasing anyone

Three of four means the ladder is moving. Zero of four means the map was never the problem — reread step 6, because the missing piece is almost always that nobody senior went first.

Strip the machinery and there’s not much AI left in this playbook. An address for every skill. A ladder to climb. Witnesses when it climbs. But the thing being promoted was never a Markdown file — it’s the moment one person’s private trick becomes the whole team’s reflex.

A company is its people learning from each other. The iceberg just makes that visible.