call

Delivers one message to a Paseo agent or terminal pi session via a resolver script.

Updated Nov 25, 2024
One-click install
npx skills add https://github.com/cbrostrom/dotfiles --skill call-cbrostrom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: call
Source: https://github.com/cbrostrom/dotfiles/tree/main/stow/agents/.agents/skills/call
Command: npx skills add https://github.com/cbrostrom/dotfiles --skill call-cbrostrom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple AI agent sessions is messy: finding the right peer, avoiding stale rosters, and preventing runaway message loops all cost tokens and attention. This Skill routes a single message to exactly one peer agent with strict budget and loop-guard rules. ## Core Features & Use Cases - Paseo-first routing: Resolves Paseo agents by id prefix, name, or working directory using the bundled peer-resolve.mjs script, then delivers via paseo send --no-wait. - Terminal pi fallback: Reaches bare pi sessions through the pi-peer registry when Paseo cannot, with presence detection (live, stalled, offline) and mail counts. - Auto-call governance: Permits unsolicited peer calls only under a concrete trigger, a Higgins vault search for routing, a strict token budget, and one-call-per-turn guardrails. - Use Case: After discovering that a shared config changed, an agent runs one Higgins search to find the owning project, resolves the peer by cwd, and sends a two-sentence summary with a file pointer prefixed by a [call:from=...] marker. ## Quick Start Ask the agent to call the pi session working in the project directory and tell it that the build is now green.

Frequently Asked Questions about call

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send a message to another Paseo agent?▼

Resolve the target with peer-resolve.mjs agents <pattern> to get its id, then run paseo send <agent-id> --no-wait with your message. Prefix the text with a [call:from=<label>] marker so timeline UIs render it as a call card.

How do I message a pi session running in a terminal?▼

Run peer-resolve.mjs peers <pattern> to list matching pi-peer sessions with presence and mail counts, then deliver through the message_peer tool using the resolved name. Never write directly to ~/.pi/agent/peers inboxes, which bypasses loop guards.

When should I use Paseo versus pi-peer for agent messaging?▼

Paseo is the default route for any agent it manages. Fall back to pi-peer only when the target is a bare pi process in a terminal that Paseo cannot reach, or when the user explicitly names a terminal session.

Can an agent message a peer without being asked?▼

Only under strict conditions: a concrete trigger like a broken build or changed shared config, routing via one Higgins vault search, a message of three sentences or fewer, and a maximum of one auto-call per turn to a live target.

Why does peer resolution show offline sessions?▼

The resolver lists offline peers only when no live or stalled session matches the pattern. Sending to an offline peer queues mail that is read only if someone resumes that session with pi -c, so confirm with the user first.

How do I clean up stale pi-peer registry entries?▼

Run peer-resolve.mjs prune --days N to remove offline records older than N days (default 7) whose inboxes are empty. Records with waiting mail are never deleted, and pruning should only run after offering it to the user.