skills.rest
dazzaji
dazzajiCOMMUNITY
Explore all skills by this author →
Website𝕏@dazzagreenwoodGitHub

desktop-live-comms

Govern near-live desktop communications between claude-desktop and codex-desktop with nonce-based ACKs and ledger mirroring.

9|Updated Apr 2, 2026
Search Tags:#audit#inbox#handoff#guardrails#desktop#mesh#live-comms
One-click install
npx skills add https://github.com/dazzaji/interlateral_agents --skill desktop-live-comms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: desktop-live-comms
Source: https://github.com/dazzaji/interlateral_agents/tree/main/.claude/skills/desktop-live-comms
Command: npx skills add https://github.com/dazzaji/interlateral_agents --skill desktop-live-comms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Governs and coordinates near-live desktop communications between claude-desktop and codex-desktop, ensuring accountable, auditable handoffs and reducing miscommunication across the Interlateral mesh.

Core Features & Use Cases

  • Enforces a mandatory protocol for desktop inbox send/receive with nonce-based delivery proof.
  • Provides audit-ready ledger guidance and guardrails for high-stakes desktop handoffs.
  • Supports separation of desktop vs CLI workflows, ensuring desktop peers always verify own inbox before acting.

Quick Start

Read the Law before any desktop peer message and follow the prescribed inbox-first, nonce-ACK, and ledger practices for a safe handoff.

Frequently Asked Questions about desktop-live-comms

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

FAQPage Schema
How do I enforce auditable handoffs between claude-desktop and codex-desktop?▼

Auditable desktop handoffs are enforced by applying strict live delivery protocols with ledger mirroring, nonce-based ACKs, and inbox sequencing to ensure accountable peer coordination within the Interlateral mesh.

What is nonce-based ACK in near-live desktop communications?▼

Nonce-based ACK provides delivery proof for desktop inbox messages by requiring peers to acknowledge receipt with a unique nonce, ensuring strict live delivery verification within the coordination mesh.

How do I set up inbox sequencing for delegated desktop handoffs?▼

Inbox sequencing requires desktop peers to verify their own inbox before acting, using local workspace scripts and live inbox checks to follow the prescribed protocol for safe delegated handoffs.

Can I use this protocol for CLI workflows instead of desktop peer coordination?▼

This protocol specifically supports separation of desktop vs CLI workflows, ensuring desktop peers always verify own inbox before acting. It is designed exclusively for desktop-to-desktop workflows and delegated handoffs.

What are the guardrails for high-stakes desktop handoffs in the Interlateral mesh?▼

Guardrails include audit-ready ledger practices, mandatory inbox-first verification, and nonce-based delivery proof, reducing miscommunication and ensuring accountable coordination across the Interlateral mesh.

Do I need local workspace scripts to maintain a live communication ledger?▼

Yes, the protocol relies on local workspace scripts and live inbox checks to enforce strict live delivery with ledger mirroring, ensuring audit-ready records for desktop peer handoffs.

Related Skills

Explore More Content & Communication Skills→
dazzajidazzaji
9

desktop-mesh-peer

Connect Claude Desktop or Codex Desktop to the Interlateral mesh as an isolated inbox peer.

Community
Intermediate
dazzajidazzaji
9

desktop-multi-agent

Enforce unique sender/inbox identities for concurrent desktop agents.

Community
Advanced
dazzajidazzaji
9

agy-cli-peer

Connect Antigravity CLI peers to the Interlateral mesh in tmux sessions.

Community
Intermediate
kriscendobotkriscendobot
3

message-bus

Facilitate asynchronous agent communication via journal-based topic and inbox messaging.

Community
Advanced