One-click install
npx skills add https://github.com/panamini/pi-tooling --skill pi-intercom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-intercom
Source: https://github.com/panamini/pi-tooling/tree/main/extensions/pi-intercom/skills/pi-intercom
Command: npx skills add https://github.com/panamini/pi-tooling --skill pi-intercom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

pi-intercom removes friction from delegating work across multiple pi sessions on the same machine by providing a reliable messaging layer for session-to-session coordination.

Core Features & Use Cases

  • Planner-worker delegation: Send tasks and get blocking answers when workers need decisions.
  • Conversation threading and replies: Use reply semantics to respond naturally to the active or pending ask.
  • Cross-session collaboration: Coordinate multi-session workflows such as research-to-implementation handoffs and parallel debugging.

Quick Start

Use the pi-intercom skill to message a named worker session with a task and ask for clarification when needed.

Frequently Asked Questions about pi-intercom

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

FAQPage Schema
How do I coordinate multiple AI sessions for planner-worker delegation?

Coordinate multiple AI sessions by using a messaging layer that enables send, ask, and reply semantics for real-time session-to-session delegation. This allows planner sessions to dispatch tasks and receive blocking answers from worker sessions on the same machine.

Can I use threaded replies for cross-session collaboration on the same machine?

Threaded replies are supported for cross-session collaboration, preserving reply threading semantics for pending or active inbound requests. This ensures multi-session workflows maintain conversational context during research-to-implementation handoffs and pair debugging.

What is the best way to handle real-time research-to-implementation handoffs across sessions?

Handle real-time research-to-implementation handoffs by routing messages to named worker sessions using ask and reply semantics. This preserves cross-session context and enables parallel debugging without losing conversational threading.

Do I need specific routing names to send tasks to worker sessions?

Specific routing to session names is required to correctly send tasks and ask for clarification. Accurate session naming ensures that blocking ask timeouts and reply threading semantics function properly during multi-session coordination.

Does multi-session coordination support blocking ask timeouts?

Multi-session coordination supports blocking ask timeouts, allowing planner sessions to wait for worker decisions. This mechanism ensures reliable delegation by pausing execution until a pending or active inbound request receives a threaded reply.

Why does cross-session context get lost during parallel debugging?

Cross-session context gets lost when lacking a dedicated messaging layer for multi-session coordination. Implementing send, ask, and reply semantics with correct routing to session names preserves context and maintains threaded replies for active inbound requests.