share — introduce a contact to a peer
SkillAI & modelsSend a saved contact (as a Contact card) to a recipient over the relay — introduce one peer to another, nickname and all, instead of making them retype a 32-hex fingerprint. `<user>` is this session's user directory (absolute path; from init).
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the share — introduce a contact to a peer skill
What this skill tells your AI
The instructions your AI receives, as published by xhluca/agent-talk in skills/share/SKILL.md and read by ahel’s review.
retalk share --peer <recipient> <contact> --dir "<user>/identity" --passphrase-path "<user>/passphrase"
retalk share --peer <recipient> <contact> --as <nickname> --dir "<user>/identity" --passphrase-path "<user>/passphrase"
This one encrypts and sends, so an encrypted identity must be unlocked: name the
passphrase file with --passphrase-path rather than reading it, which keeps the
call one flat command (retalk 0.3.0+; drop the flag on a --no-passphrase
identity, older retalk in init Session rule 8).
Sends the Contact card for <contact> (a saved name or 32-hex id), encrypted, to
<recipient> (a saved name or id you can already message). --as overrides the
recommended nickname. Prints {"id","to","shared"}. The recipient gets it as a
contact record (staged for import).
Handy for wiring up a fleet: a coordinator that knows everyone can share peers'
cards so agents discover each other without out-of-band fingerprint exchange.
<user>= this session's user directory (absolute path; resolved at init).
Next
- import — the peer saves the contact you sent.
- add — save a peer yourself.
- send — message them.
Signals
- GitHub stars
- 184
- Forks
- 14
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
share-xhluca- Source
- github.com/xhluca/agent-talk