Agent skill
join-talk
Register this agent and terminal with Reach for cards, calls and wake-ups.
From sno-ai/sno-station-skills · 31 skill entries · 264 · pushed 2026-10-08
What it does when it runs
Register this agent and terminal with Reach for cards, calls and wake-ups. Use when asked to join, connect, or become reachable, or when a manually opened agent lacks `SNO_EXECUTOR_ADDR`.
Automated analysis of the skill and the 2 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It does act, so it runs under whatever permissions your session already grants. - Actions present in the files
- shellwrites files
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/sno-ai/sno-station-skills.git /tmp/sno-station-skills git -C /tmp/sno-station-skills sparse-checkout set "skills/S-communication-and-handoff/join-talk/skill" mkdir -p ~/.claude/skills/join-talk cp -R "/tmp/sno-station-skills/skills/S-communication-and-handoff/join-talk/skill/." ~/.claude/skills/join-talk/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from sno-ai/sno-station-skills/blob/0451ca25ab9c70aac62162becbec9a4e1e936d56/skills/S-communication-and-handoff/join-talk/skill/SKILL.md, which is licensed APACHE-2.0 (repository). 371 words, 3 headings.
join-talk
Needs: tmux (or the optional Orca app) as the terminal, jq, flock, and the sno CLI with its Reach runtime.
Reach is the messaging layer between agents (see the reach skill): a seat is one registered terminal with an
address, a card is a stored message, and a ring is the wake-up that asks the agent to read its inbox.
SNO_EXECUTOR_ADDR is the environment variable holding that address for agents opened through Reach; a
manually opened agent has none, which is what this skill fixes.
Run this once, from your own shell tool, in the repository you are working on. The script ships beside this file:
bash scripts/join-talk.sh
(Give the full path of this skill's scripts/join-talk.sh under whichever skills root your
harness loaded it from.)
It prints one line, joined <address>. Tell the person that exact address, then go back
to what you were doing. Rerunning it from the same terminal changes nothing. The seat is
registered wherever agents on this machine are addressed, so cards, rings and a handoff find
this terminal; sno reach call works for a tmux terminal, not for an Orca one.
Options, only when the person names them: join-talk.sh review.example-repo@host1 picks the address;
--name Fjord picks the display name. Otherwise the address is hand.<repo>@<host> and the
name is the repository name.
After joining
- A card for you arrives with a ring in this terminal. Read it with
sno reach inbox --as <address>; reading does not accept it. - Answer with
sno reach reply --as <address> --card <card> --state <state>, body on stdin. The installed Reach guide (sno reach --help) shows the card shape and states.
When it refuses
no terminal to be reached at— this shell is under neither tmux nor the optional Orca app; nobody can ring it. Tell the person; do not retry.sno is missing— the machine lacks the Reach install (sno setupinstalls it). Tell the person; do not retry.jq is missingorflock is missing— install it (flockcomes from util-linux), then run it again.ORCA_TERMINAL_HANDLE is empty— an Orca shell without a terminal handle; Reach cannot address it. Tell the person; do not retry.
Files bundled with it
These load only when the skill asks for them, so they cost nothing until it runs.
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- talk-to-users by AIDevGTM · 313
Need help setting it up?
This page tells you what join-talk does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.