scbe-system-engine

Coordinate SCBE-AETHERMOORE math, automation, and service connectors for multi-agent workflows.

6|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-system-engine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scbe-system-engine
Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/external/codex-skills-live/scbe-system-engine
Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill scbe-system-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinates SCBE-AETHERMOORE math, automation, and service connectors to enable end-to-end multi-agent workflows with auditable governance and patchability.

Core Features & Use Cases

  • Deterministic dual-output contract: StateVector + DecisionRecord to ensure traceable agent decisions.
  • Multi-service orchestration: GitHub, Hugging Face, Notion, Linear, Zapier, and browser automation routing.
  • On-demand patching: supplies scripts and references to enable self-improvement loops and governance patches.

Quick Start

Run the KO-tongue reviewer on a sample diff to see the agent outputs and tri-fold summary generation.

Frequently Asked Questions about scbe-system-engine

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

FAQPage Schema
How do I coordinate multi-agent workflows across GitHub, Linear, and Notion?

Multi-agent workflows across GitHub, Linear, and Notion are coordinated through browser-backed routing and service connectors. The system engine orchestrates AI-to-AI tasks end-to-end while enforcing deterministic math validation and dual-output traceability.

What is a deterministic dual-output contract for AI governance?

A deterministic dual-output contract enforces AI governance by generating a StateVector and a DecisionRecord for every agent action. This ensures traceable, auditable decisions across multi-agent automation workflows and service connectors.

How do I enforce traceable agent decisions in automated patching workflows?

Traceable agent decisions in automated patching workflows are enforced by the dual-output contract, yielding a StateVector and DecisionRecord. The system supplies scripts and references to enable self-improvement loops and governance patches.

Can I use Zapier and Hugging Face connectors for end-to-end multi-agent automation?

Yes, Zapier and Hugging Face connectors support end-to-end multi-agent automation. The system engine routes tasks through these services alongside GitHub, Notion, and Linear, generating a tri-fold action summary to guide build, document, and route steps.

When do I need browser-backed routing for AI-to-AI workflows?

Browser-backed routing for AI-to-AI workflows is needed when coordinating multi-agent tasks across external services like GitHub and Hugging Face. It enables auditable governance, patchability, and deterministic math validation across the orchestration pipeline.

What are the limitations of using a tri-fold action summary for build and route steps?

The tri-fold action summary guides build, document, and route steps but is limited to the orchestration context of the system engine. It relies on the dual-output contract and available service connectors to function correctly within the multi-agent workflow.