scbe-session-corkscrew

Coordinate auditable SCBE session activity across machine and human channels.

6|1|Updated Jan 17, 2026

Search Tags:#workflow #versioning #session-management #auditability #scbe #cross-talk

Ready to run

npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-session-corkscrew

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: scbe-session-corkscrew
Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/external/codex-skills-live/scbe-session-corkscrew
Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-session-corkscrew

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating and auditing multi-agent SCBE sessions across machine and human lanes, ensuring traceability and non-destructive handoffs.

Core Features & Use Cases

Start or rotate a session with a timestamped callsign and session status.
Emit append-only cross-talk packets and mirror key packets to Obsidian for readability.
Mark sessions as verified or retired to maintain an auditable history.
Use case: coordinating agent handoffs and progress updates while preserving provenance across repo lanes.

Quick Start

Start a new session with a unique TaskId and summary, then emit progress packets and sign on the session to establish a verifiable chain across lanes.

Frequently Asked Questions about scbe-session-corkscrew

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

FAQPage Schema

What is append-only cross-talk packet emission for multi-agent session coordination?▼

Mirroring key cross-talk packets to Obsidian provides a readable, human-accessible view of auditable session activity. It helps track agent handoffs and progress updates while maintaining provenance across lanes.

How do I start a verifiable multi-agent session with timestamped callsigns?▼

You rotate a session by updating its timestamped callsign and status, then emitting append-only cross-talk packets. This maintains an auditable, non-destructive history while coordinating handoffs across repo lanes.

When do I need to mark an auditable session as verified or retired?▼

This approach suits multi-agent workflows requiring deterministic scripting, mandatory packet fields, and auditable history. It is ideal for coordinating agent handoffs and progress updates across machine and human lanes.

What's the best way to coordinate cross-lane session activity across human and machine channels?▼