Solve it once. The team never solves it again.
A skill is a lesson worth keeping. Publish one and it shows up in every teammate's assistant automatically, starting with their next session. No file to send, no wiki page to remember to update.
DownloadHow a skill spreads
- 1
Someone solves something
An engineer works through a tricky migration, a flaky test, or a fix nobody had written down. The lesson is worth keeping.
- 2
It becomes a skill
The reusable part gets distilled into a skill, tagged with what it applies to and who wrote it.
- 3
They choose to publish it
Promoting a skill from personal to team-wide is a deliberate, recorded action. Nothing shares itself by accident.
- 4
It appears next session
Every teammate's assistant picks up the skill automatically the next time they start working, with no file passed around and no message to send.
Opt-in sharing, clear authorship.
Sharing a skill with the team is a choice you make, not a default you fall into. The default leans private, so your own notes stay yours until you decide otherwise. Once shared, a skill carries the name of the person who wrote it, so credit and history stay clear even as the list of skills grows into the hundreds. Two people can write a skill with the same title without one clobbering the other, because authorship keeps them distinct.
Read about scopingCommon questions
What counts as a skill?
Any reusable lesson worth keeping: a fix for a tricky bug, a convention for how your team writes migrations, a working pattern for a flaky integration. If it is worth telling a teammate, it is a skill candidate.
Does a skill share itself automatically?
No. Promoting something from just yours to the whole team's is a deliberate, recorded action. Nothing private becomes shared by accident.
How fast does a shared skill reach the team?
By each teammate's next session. There is no file to send and no channel to post in. Their assistant just knows it the next time they open it.
Who gets credit for a skill?
The author is attached to the skill permanently. Two people can write a skill with the same name without one clobbering the other.
Can a skill be wrong, and what happens then?
Yes, like any note a person writes. Skills are versioned, so a correction is a new version, not a silent overwrite.
Let one fix become everyone's fix.
Install the stack and publish your first skill to the team.
Windows (PowerShell): irm https://get.theapiary.sh/install.ps1 | iex
Download