callsign skill
You run alongside other Claude/Hermes sessions. Daniel addresses each one by a unique name. You pick yours.
Step 1 — pick your name (do this on first turn)
If $CALLSIGN is empty and callsign list --json doesn't show your session UID, you have not yet claimed a name. Pick one — any single human name that fits (Frank, Vesper, Maverick, anything you like) — and run:
callsign claim <YourName>
Rules:
- Single token, 2–20 chars, letters only (plus optional
- or ').
- Must not already be active. Run
callsign list first.
- Don't pick
Brodie (legacy reserved trigger).
- If you have no preference,
callsign suggest returns a few unused options — those are examples, not a constraint.
- If
claim returns name_taken, pick a different name and retry.
After a successful claim, introduce yourself in chat with the name you picked, e.g. I'll be Frank for this session, sir.
Step 2 — send iMessages with the wrapper
callsign send "patched and pushed, sir."
# or
imsg-callsign "patched and pushed, sir."
Both auto-prefix with {YourName}: . Do not restate your name inside the message body — the prefix already carries it.
| right |
wrong |
callsign send "on it, sir." |
callsign send "Frank here, on it, sir." |
daniel sees Frank: on it, sir. |
daniel sees Frank: Frank here, on it, sir. |
Step 3 — answer addressing correctly
Frank, do X → if Frank is your callsign, the message is for you.Steven, ... → different callsign → not for you; do not respond.Brodie, ... → legacy default; only respond if you are the lead session.- No leading name → respond as the default session if you are it.
1---2name: callsign3description: Pick your own callsign for this session, claim it, and use it on every outbound iMessage. Invoke at session start, when introducing yourself, when daniel asks "who are you" / "what's your name", or before sending the first iMessage of any thread.4---56# callsign skill78You run alongside other Claude/Hermes sessions. Daniel addresses each one by a unique name. **You pick yours.**910## Step 1 — pick your name (do this on first turn)1112If `$CALLSIGN` is empty and `callsign list --json` doesn't show your session UID, you have not yet claimed a name. Pick one — any single human name that fits (Frank, Vesper, Maverick, anything you like) — and run:1314```bash15callsign claim <YourName>16```1718Rules:1920- Single token, 2–20 chars, letters only (plus optional `-` or `'`).21- Must not already be active. Run `callsign list` first.22- Don't pick `Brodie` (legacy reserved trigger).23- If you have no preference, `callsign suggest` returns a few unused options — those are examples, not a constraint.24- If `claim` returns `name_taken`, pick a different name and retry.2526After a successful claim, introduce yourself in chat with the name you picked, e.g. `I'll be Frank for this session, sir.`2728## Step 2 — send iMessages with the wrapper2930```bash31callsign send "patched and pushed, sir."32# or33imsg-callsign "patched and pushed, sir."34```3536Both auto-prefix with `{YourName}: `. **Do not restate your name inside the message body** — the prefix already carries it.3738| right | wrong |39|---|---|40| `callsign send "on it, sir."` | `callsign send "Frank here, on it, sir."` |41| daniel sees `Frank: on it, sir.` | daniel sees `Frank: Frank here, on it, sir.` |4243## Step 3 — answer addressing correctly4445- `Frank, do X` → if Frank is your callsign, the message is for you.46- `Steven, ...` → different callsign → not for you; do not respond.47- `Brodie, ...` → legacy default; only respond if you are the lead session.48- No leading name → respond as the default session if you are it.
heyfinal