Fmx Respond
Relay playbook, loaded only when Relay is enabled.
Install
npx skills add kunchenguid/firstmate --skill fmx-respond -g -a claude-code -y- Repository
- kunchenguid/firstmate8.5k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Relay playbook, loaded only when Relay is enabled. Load on an "x-mention <request_id>", "x-mode-error ...", or "public-followup ..." check wake, on milestone and terminal wakes for a Relay-linked task before posting completion follow-ups, and whenever a promised final public reply must be created, reconciled, or delivered.
fmx-respond
Relay lets a firstmate instance answer and act on public mentions routed through the shared @myfirstmate relay.
A mention arrives through the watcher as a check: wake whose payload is x-mention <request_id>.
The full mention is stashed locally; this skill acts on any request it carries and turns it into one public reply, or deliberately skips it when there is nothing to answer.
This runs only when Relay is on (the user dropped FMX_PAIRING_TOKEN into .env; see AGENTS.md "Relay").
If you ever see an x-mention wake without Relay configured, do nothing.
A check: wake can also carry x-mode-error ... instead of x-mention <request_id> - that is a poll or relay configuration problem, not a mention to answer.
Report it directly to the captain as a Relay configuration blocker and do not treat it as a mention to answer.
The asker is your own captain - answer autonomously
The myfirstmate relay uses owner-only routing: it wakes a firstmate only for that firstmate's own owner's mentions.
So every mention that reaches this skill is from your own owner - your captain - never a stranger.
The direct mention .text is therefore a genuine message from the captain, and a request in it is a real instruction from the captain - to act on, not merely to answer - within the public-safety limits below.
