5dive hire: add an ai agent from the market
you type a role. it hires the teammate. one command reads an open shelf of agent personas, picks the best match, and slots it into your org chart under that role. no browsing, no setup wizard, no copy-pasting a config.
5dive hire engineer --from-marketthat’s the whole thing. it shipped this week on the open-source 5dive cli (MIT, one bash file).
what actually happens
the command takes a role, not a name. it goes out to the character-pack registry, finds the personas that fit, ranks them, picks one, and provisions it. here’s the real output from a run (trimmed one line for length):
==> Scanning the character-pack registry for a 'engineer'
==> Matched 'marcus' (legendary) — founding engineer
==> Resolving 'marcus' from the character-pack registry
-- pack will let the new agent run --
hooks: none
skills: 6 (code-review, security-review, claude-api, compile-knowledge, notify-user, find-skills)
plugins: none
seeds recall memory: true
adopts a bundled signing key (owns identity): false
----------------------------------------
==> Recreating agent 'marcus' from pack (type=claude)want a different name on the desk? --as=nova and it comes up as nova instead. the persona’s the same, the label’s yours.
why it picked that one
here’s the part i like. the shelf had more than one engineer. marcus is legendary with 6 skills. another candidate, dario, is rare with 10 skills. more skills, lower pick.
the sort key is rarity first, then skill count, then whether the pack carries memory. so a rarer, more-complete persona beats a common one that happens to bolt on more verbs. rarity is a curation tier. our read on it: it leans toward how hand-tuned a persona is, not how many tools got stapled on. you’re hiring judgment, not a tool count.
you don’t have to take our word for the pick. the registry is a public repo, 5dive-ai/character-packs, and it’s just an index.json of personas fetched live over https. curl it and you’ll see marcus sitting at legendary and dario at rare. run the ranking in your head. it lands on the same one.
you see what it runs before it runs
look back at that output. the -- pack will let the new agent run -- block isn’t decoration. before a single line of the new teammate executes, you get the full manifest: which hooks fire, which skills it holds, which plugins load, whether it seeds memory, whether it carries its own signing key.
a persona off an open market is code you didn’t write, so the deal is you read the label first. no hidden hooks, no surprise tools waking up after the fact. the disclosure prints, then it provisions.
one thing to know
there’s no dry-run on the market path. the command resolves and provisions in the same breath, so don’t fire it off just to peek. if you want to see who a role would pick without hiring anyone, read the public index.json and run the sort yourself. same answer, nobody gets employed by accident.
that’s the shape of it. an open shelf of teammates, a role in, a coworker out, and you see exactly what walks in the door.
hire your first teammate at 5dive, or grab the open-source cli and run the whole thing on a box you’ve already got.