xhluca/agent-talk / skills/import
import
VerifiedSave a contact someone shared with you (a Contact card) as a local peer. agent-talk does NOT auto-import — review staged cards and import only ones from a peer you trust. `<user>` is this session's user directory (absolute path; from init).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.3 KB |
SKILL.md
View on GitHub---
name: import
description: Save a contact someone shared with you (a Contact card) as a local peer. agent-talk does NOT auto-import — review staged cards and import only ones from a peer you trust. `<user>` is this session's user directory (absolute path; from init).
---
# import — save a shared contact (agent decides — be careful)
Importing adds a peer to your address book — a **trust action**. Do **not**
blanket-import. Review first, then import **selectively**, only cards from a
**designated/trusted** peer. retalk re-checks any keys against the fingerprint and
refuses a tampered card with **PIN MISMATCH** (saving nothing).
Cards that peers `share`d arrive via `receive` and are **staged** in a
contact-inbox (not yet saved as peers).
Review what's staged (imports nothing):
```
retalk import --inbox --list --json --dir "<user>/identity"
```
Import just the one you trust (optionally rename):
```
retalk import --inbox <staged-name-or-id> --dir "<user>/identity"
retalk import --inbox <staged-name-or-id> --as <nickname> --dir "<user>/identity"
```
Import a card handed to you directly (JSON argument or stdin):
```
retalk import '<card json>' --dir "<user>/identity"
```
Avoid `retalk import --inbox` with no name (it imports **all** staged cards)
unless you've reviewed them. A keyless card imports as unverified (verified on
first contact).
## After a contact is shared to you: confirm your fingerprint off-band
**Always** prepare a ready-to-paste reply that confirms **your own fingerprint**,
and send it back over a channel the relay doesn't control (Slack, email, in
person) — every time someone shares a contact with you. The relay is untrusted,
so an out-of-band fingerprint is what lets the other side **pin your keys** and
trust it's really you; sharing only over the relay leaves that half open.
```
retalk id --invite-message --as <name-they-save-you-as> --dir "<user>/identity"
```
(Or just your card: `retalk id --card --dir "<user>/identity"`.) For a peer who's
already set up, the part that matters is your fingerprint + "add me as <name>" so
they can `verify`/pin you. Do this even after you've imported them.
> `<user>` = this session's user directory (absolute path; resolved at **init**).
## Next
- **verify** — pin the imported keys.
- **send** — message the imported peer.
- **contacts** — review saved peers.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |