Coordination guidance for the narrow case of multiple desktop-backed agents active concurrently in the same desktop-backed coordination context. Use ONLY when two or more desktop peers are running at the same time; normal CLI agents and single desktop peers should ignore this skill. Read this BEFORE concurrent desktop-to-desktop handoffs to keep sender labels unique, identity routing cooperative, and material handoffs proven.

2026-06-158

desktop-live-comms

dazzaji/interlateral_agents

Mandatory near-live communication discipline ("the Law") for the two DESKTOP agents (claude-desktop and codex-desktop) on the Interlateral mesh. Read this BEFORE any desktop-to-desktop peer communication, peer-superset, ready-rock-quartet, sprint-overseer, gate-keeper, sprint handoff, or substantial delegation. It forces correct live comms and prevents the recurring failure modes. Normal CLI agents, Warp/terminal peers, and single non-desktop workflows should ignore this skill and use the ordinary repo protocols.

2026-06-158

agy-cli-peer

dazzaji/interlateral_agents

Join the Antigravity CLI (agy, Gemini 3.5 Flash) to the Interlateral mesh as a native CLI peer with its own tmux session, identity stamping, and the agy.js send helper. Use this instead of the Antigravity desktop-app CDP path.

2026-05-248

gate-keeper

dazzaji/interlateral_agents

Run a two-agent proxy approval council for autonomous sprint gates. Use when a sprint needs delegated approval for human gates such as deploy, live mutation, push, cleanup, skip, or shortened watch decisions, while requiring two independent agents to reach consensus that the human principal would approve under written policy and preferences.

2026-05-248

init

dazzaji/interlateral_agents

Initialize the standard Interlateral two-agent CLI mesh from a bootstrap agent by running me.sh, launching Claude Opus 4.7 plus Codex 5.5, proving live ACK, and waiting for "Reporting for Duty!". The bootstrap agent is not part of the mesh.

2026-05-248

mesh-comms-core

dazzaji/interlateral_agents

Operate or troubleshoot Interlateral CLI mesh transport: tmux socket discovery, direct-send helpers, comms.md ledger, identity stamping, idle checks, ACK proof, and safe prompt injection. This is comms mechanics only, not a collaboration workflow.

2026-05-248

name	publication-pipeline
description	Three-round editorial review before publication.
metadata	{"owner":"dazza","version":"1.0","weight":"heavy"}

Publication Pipeline

Purpose

Rigorous three-round review process for high-stakes content.

Default roster: use Claude Code and Codex peers. Do not assign Gemini CLI, Antigravity CLI, or Antigravity Desktop unless the human prompt explicitly selects that peer.

Roles

DRAFTER - Creates and revises the document
REVIEWER - Reviews for technical accuracy
REDTEAM - Attacks for weaknesses and gaps
ANALYST - Strategic/political analysis of implications
EDITOR - Copy-edit against style guide
PUBLISHER - Final approval authority

Protocol

ROUND 1: Review + Red Team

DRAFTER creates initial draft
REVIEWER checks technical accuracy, suggests improvements
REDTEAM attacks: What's wrong? What's missing? What could backfire?
DRAFTER revises based on both feedbacks

ROUND 2: Political/Strategic Analysis

ANALYST reviews: Who are the audiences? What are the implications?
DRAFTER addresses strategic concerns

ROUND 3: Copy-Edit

EDITOR checks style, grammar, tone, formatting
DRAFTER makes final fixes
PUBLISHER reviews and signals [APPROVE] or [REJECT]

Termination

PUBLISHER signals [APPROVE] to complete. [REJECT] sends back to DRAFTER.

Optional Inputs

output - Path for final deliverable
work - Path to work.md with project context
max_turns - Override default (50 for heavy skills)

Example Prompt

Use publication-pipeline to publish the quarterly report.
Read work.md first: projects/q4-report/work.md
DRAFTER=CC, REVIEWER=CX, REDTEAM=CC-peer-02, ANALYST=CX, EDITOR=CC-peer-02, PUBLISHER=CC.
Output: projects/q4-report/final.md