The codes
Every artefact in the marketplace has a code in the form PREFIX-XXXX-XXXX. The
prefix tells you what it is before you paste it.
| Prefix | Installs |
|---|---|
AGNT- | An employee |
SKIL- | A skill |
PLUG- | A plugin |
WORK- | A standalone workflow |
APPS- | An app |
CONN- | A connection |
COLL- | A collection, which is several of the above at once |
Install one
Paste it into the chat box. There is no install screen to find, because the runtime recognises the shape of a code and acts on it.
Installing an employee cascades, in this order:
- Its required plugins install
- Skills its workflows reference install
- Any additional skills install, pulling their own plugin dependencies
- Its triggers register
- Its persona loads
One code can therefore pull in six or seven components, which is the point: the role should arrive able to do the job rather than as a shell you have to equip.
Share one
A code is just text, so sharing is sending the text. Put it in a message, a document, a README, or on a slide. Whoever pastes it gets the same install, with the same dependencies, on their own machine.
This is the cheapest way to give someone a working setup. Rather than writing instructions for configuring an employee, send the code for the one you already configured.
A code carries the definition: persona, workflows, skills, plugin dependencies, triggers. It does not carry your data, your connections or your memory. The person who installs it authorises their own accounts and starts with an empty history, which is what you want when sharing something that reads mail.
Collections
When several things only make sense together, a COLL- code installs the set. That
is the right shape for a team that hands work between its members, since installing one of them
alone leaves a handoff pointing nowhere.
Check it
- After installing, confirm the plugins it needed arrived too
- Confirm its triggers are registered rather than only its persona being present
- Ask it to do the job it was hired for and see what it says is missing
When it goes wrong
The code is not recognised
The format is exact: a known prefix, then four characters, a hyphen, four more. Anything else is treated as ordinary text. Check for a missing character or a line break in the middle when the code came out of a chat message.
It installed but cannot do anything
The definition arrived, the authorisations did not, and they never do. Connect the accounts it needs on your own machine.