How SkillRelay works
Your team's know-how lives as skills: short instructions your AI tools follow. Skills reach everyone automatically. Fixing one is a sentence in chat.
There are exactly two setups, and both happen once: the workspace (one admin turns on team-wide distribution) and your tools (each person connects their own chat apps and editors). Everything after that is just talking.
Using skills
You get every skill automatically: nothing to install, nothing to update. When something is wrong or missing, say so, in whatever chat you're already in:
- “What team skills do we have?”
- “The proposal skill quotes last year's pricing: the Growth plan is $99 now.”
- “Save how we run customer kickoff calls as a team skill.”
- “Yesterday's change to the interview-feedback skill made it worse. Put it back.”
The fix applies immediately and reaches the whole team within about 30 minutes. Every change is a new version with the author's name on it: nothing is ever lost, anything can come back.
Your one-time setup: connect the tools you use. The Connect page has a tab for each one — Claude, ChatGPT, Cursor, Claude Code, Codex, and more — and each takes about a minute. If your admin set up team-wide delivery, some tools need nothing at all.
Packs
Skills reach the whole team by default. A pack is a named opt-in collection, such as "Sales" or a personal pack. Teammates add a pack once and receive every skill in it, including future additions. To start one, say “save this as a skill in a new Sales pack.” Each pack is owned by its creator, who reviews changes to it when approvals are on.
Running it (admins)
One person does the setup checklist once (about five minutes). After that there is no ongoing admin work: skills publish themselves. Invite people from Settings; each teammate gets a one-click email. Everyone joins as a Reader. Promote people to Editor when they should change things.
Approvals (optional)
Off by default: safety comes from undo, since anyone can revert anything in one sentence and every change is attributed. Teams that want a gate turn on approvals in Settings: changes to the skills everyone gets then wait for an admin's one-click sign-off, and each pack is reviewed by its owner. Admins always publish directly, and you never wait on yourself.
If something breaks
- A skill got worse: say “put it back how it was”, or use its history on the Skills page.
- A publish failed: the error shows on Settings. No edits are lost. Fix the cause and press “Publish now”.
Want the machinery (architecture, permissions, data handling, threat model)? That's the About page.