Six steps, all in SkillKeeper and in Claude’s own app. Nobody on the team opens GitHub or a terminal.
Step 1
Push
Anyone sends a skill to the library from inside Claude (“push this skill to SkillKeeper”), by upload, or by pasting instructions that Claude turns into a skill.
It lands as a private draft that only they see. Claude never shares on anyone’s behalf.
NorthbeamPR
Library
Mine · 3 private drafts
Claude added 3 skills to your draftsOnly you can see them. Share the ones that belong to Northbeam.
write-proposalpushed from Claude · 2 h ago
Private draftShare
client-onboardingpushed from Claude · 2 h ago
Private draftShare
weekly-reportpushed from Claude · yesterday
Private draftShare
A member’s Library. Claude added three skills to their drafts; only they can see them.
Step 2
Share
They share it with the team when it is ready. A lead is told.
Before it goes, the check gives advice on the spot: anything that usually should not leave their machine, line by line. The lead sees the same notes.
SHARE 2 SKILLS · STEP 2 OF 2
A quick look before the team sees these
The check reads each skill for things that usually should not leave your machine. Maya, your lead, sees the same notes.
client-onboardingnothing to look at
write-proposal1 note
LINE 14Mentions Halden Foods, which looks like a client name.
Edit firstShare 2 skills
Sharing two drafts. One mentions a name that looks like a client.
Step 3
Review and merge
The lead reads it. When several people have similar skills, SkillKeeper groups them and Claude drafts one best version, with every section’s origin shown.
The lead edits and applies it. The old versions are retired and point to the new one. A merge draft by Claude takes about twenty seconds.
NorthbeamLEADMC
3 SIMILAR SKILLS
MC
write-proposalMaya · source
JO
proposal-v2Jon · 71% similar
PR
client-pitchPriya · 64% similar
DRAFTED WITH CLAUDE
20 s
write-proposal
## Structurefrom Maya
Problem, approach, scope, timeline.
## Pricing tablefrom Jon
Rate card by role, with a fixed-fee option.
## Tonefrom Priya
Plain, short sentences, no jargon.
EditApply merge
Three similar skills from three people, and the one version Claude drafted from all of them.
Step 4
Approve
Approved, or sent back with a note.
A skill sent back returns to its author as a private draft, with the lead’s note at the top. They get an email.
NorthbeamLEADMC
Review
client-onboardingPriya · waiting 2 h
Send backApprove
weekly-reportJon · waiting 1 day
Line 22 emails the report to a personal address. Use the team inbox and send it back to me.
Jon gets it back as a private draft, with your note at the top.Send back to Jon
meeting-notesAlex · waiting 3 days
Send backApprove
A lead sends a skill back: one line would have emailed the report to a personal address.
Step 5
Publish
One click. The approved library is written to the company’s own private GitHub repository in Claude’s plugin format.
Nobody opens GitHub. SkillKeeper creates the repository and keeps it in shape. A publish takes about fifteen seconds, and each one is validated with Claude’s own plugin validator before it goes out.
NorthbeamLEADMC
Publishing v1.3.0
1 merge · 2 new skills · to the repository SkillKeeper hosts for Northbeam
✓Checked
✓Validated with Claude’s plugin validator
Writing the librarystep 3 of 3
VERSION
CHANGES
IN CLAUDE
1.2.02 skills added11 Oct, 14:02
1.1.01 rename2 Oct, 09:41
1.0.06 skills24 Sep, 16:10
Publishing v1.3.0: one merge and two new skills, on its last step.
Step 6
In everyone’s Claude
The company’s Claude organization syncs from that repository. New and changed skills are in everyone’s Claude within minutes, by themselves: in chat and in Cowork.
A team on Pro or Max adds the library once, each person for themselves.
The same library reaches Claude Code through the same organization. When a merge renames a skill, a rename map keeps the old name working.
NorthbeamLEADMC
Library / write-proposal
Write a proposalPublished · v1.3.0merged from 3
IN EVERYONE’S CLAUDE
Since 14:02 today
WHERE
Chat, Cowork and Claude Code
OLD NAMES STILL WORK
proposal-v2, client-pitch
Write a proposal, merged from three people’s versions. The old names keep working.
Also
Send a skill to someone outside
Another company, a client, a partner, a friend. A sealed copy of one version goes to up to ten addresses. They read all of it first, then decide whether it enters a library of theirs.
The copy carries who wrote it and that it came through SkillKeeper. It waits thirty days; the recipient gets one reminder after seven. Every send is logged under Settings → Sent outside.
SEND A COPY · WRITE-PROPOSAL · V3
Send write-proposal to someone
For people outside Northbeam. Colleagues get it through Share.
To
priya@halden.example ×tom@partner.example ×
1 note before it leaves Northbeamchecked in 18 s
LINE 14Mentions Halden Foods, which looks like a client name.
✓I have looked at this
CancelSend copy
The sender: a copy of version 3, checked before it leaves.
Halden FoodsInboxPD
MCMaya Chen at Northbeam sent you a skill · 29 Oct
write-proposalTurns a brief into a client proposal with scope, pricing and timeline.
checked 29 Oct · passVersion 3 · sent through SkillKeeper
name: write-proposal description: Turns a brief into a client…
## Structure 1. The problem, in the client’s words
Add to my draftsDeclineNothing enters your library until you choose.
The recipient: everything readable first, with where it comes from.
Also
The check
Before a skill is shared or sent, the check reads every file as text. It never runs the content. Outcomes are pass, notes or refused, and nothing leaves on an unfinished check. A skill that passes is checked, with a date; never “safe”.
What it reads
1
Form and limits
Names, sizes and kinds of file. Every file is read as text.
2
Patterns and hidden text
Comments, invisible characters, styled-away elements, even inside an SVG logo.
3
Links and packages
Every link and package the skill names.
4
Text aimed at the model
Instructions written for the AI rather than for the reader.
5
A reading by Claude
For what rules cannot see.
When it runs
Advice before sharing
instant
Shown to the member as they share. No network.
Full check before a copy leaves
15–20 s
Runs before a skill is sent outside the workspace.
Claude has one, on Team and Enterprise plans: owners provision skills, members can publish to the organization with optional review, duplicates get a hint, versions and group access exist, and a published skill reaches everyone by itself.
Claude can share skills inside your organization. SkillKeeper merges them, keeps them as your own files, checks them on any plan, and sends them to the people outside your organization who need them.
ONLY SKILLKEEPER
WHY A TEAM CARES
Merges duplicates into one skill.
Similar skills are grouped automatically, Claude drafts the best of all of them with provenance, a lead applies it. Claude’s library only says “possible duplicate”.
Why a team caresThe team ends up with one way of doing each thing, built from everyone’s best. This is the product.
The library is the company’s own files.
Plain SKILL.md folders in the company’s private GitHub, readable by any tool that speaks the open format. Claude’s library lives inside Claude’s admin screens.
Why a team caresIt is theirs. It survives a change of vendor, plan or admin.
Sends skills between companies.
A sealed copy to any email address; the recipient reads everything before it enters their library; the origin is recorded. Claude’s sharing stops at the organization boundary.
Why a team caresCompanies share with clients, partners and peers. That is how know-how travels.
Reads every byte before a skill spreads.
Hidden text, instructions aimed at the model, secrets, links that reach out, and a reading by Claude. On every plan. Claude’s own scan is Enterprise-only.
Why a team caresA skill is text an AI obeys. Someone should read it first.
Works for small teams on Pro or Max,
with any member as the lead. Claude’s library needs Team or Enterprise and an Owner.
Why a team caresMost companies of five to fifty are not on Enterprise.
A person sets it up with you.
Black Matter VC builds the starter library from the company’s own public material and walks the lead through the first week.
Why a team caresDay one is not an empty page.
Where Claude is simpler
No GitHub, no connector.
GitHub is created and tended for you. The connector is one paste, done once.
Beyond Claude
Write it once, review it once, use it everywhere
A skill is a folder with a SKILL.md file inside. Anthropic released that format as an open standard, Agent Skills, and dozens of tools now read it. SkillKeeper publishes exactly that format, plus a flat skills/ folder for tools that read a directory.
Automatic delivery is Claude today. For the others, SkillKeeper gives you the files in exactly the shape they expect.
TOOL
HOW THE LIBRARY GETS THERE
TODAY
Claude: chat, Cowork, Claude Code
How the library gets thereThe organization syncs the repository; updates arrive by themselves
TodayLive, automatic
Perplexity Computer
How the library gets thereUpload a skill (a .zip with SKILL.md at its root, or the .md) under Plugins → Add custom
TodayWorks, one skill at a time, by hand
ChatGPT (Business, Enterprise, Edu) and Codex
How the library gets thereUpload a skill under Plugins → Skills → Create → Upload from your computer
TodayWorks, one skill at a time, by hand
Cursor, GitHub Copilot, Gemini CLI, Goose, OpenClaw, Hermes and the rest
How the library gets therePoint the tool at the repository’s skills/ folder, or install the plugin
TodayWorks, by hand
Steps for other tools as published by Perplexity and OpenAI, read 28 October 2026.