Join Talk logo

Join Talk

Organization
sno-ai
join-talk

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`.

Overview

Publishersno-ai
Repositorysno-station-skills
Skill namejoin-talk
Stars
604
Forks
415
Bundled files
2
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by sno-ai on GitHub. Read the source before you install it.

Installation

Install the Join Talk AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/sno-ai/sno-station-skills/tree/main/skills/S-communication-and-handoff/join-talk/skill
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/sno-ai/sno-station-skills.git /tmp/sno-station-skills
mkdir -p .claude/skills
cp -r /tmp/sno-station-skills/skills/S-communication-and-handoff/join-talk/skill .claude/skills/join-talk
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Join Talk in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Join Talk on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Join Talk is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

join-talk

Needs: tmux (or the optional Orca app) as the terminal, or a Cursor IDE chat, 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
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. A Cursor IDE chat has no terminal: it is registered by its conversation id (channel cursor-ide), and a card reaches it when its turn ends. A Cursor CLI must run under tmux to be reachable.

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, the optional Orca app nor a Cursor IDE chat; nobody can ring it. Tell the person; do not retry.
  • sno is missing — the machine lacks the Reach install (sno setup installs it). Tell the person; do not retry.
  • jq is missing or flock is missing — install it (flock comes 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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Join Talk AI skill do?

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`.

Why use Join Talk on TypingMind?

Because you install it once and use it with any model. Join Talk is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Join Talk in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/sno-ai/sno-station-skills/tree/main/skills/S-communication-and-handoff/join-talk/skill. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Join Talk?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Join Talk?

As many as you like. As long as a model supports skills, you can use Join Talk with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Join Talk AI skill free?

Yes. It is published on GitHub by sno-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇