scbe-mobile-connector-orchestrator

Coordinate mobile-goal workflows across external connectors with approval gates.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate mobile-goal workflows by managing external connectors to bind goals, execute steps, and enforce high-risk approval gates across multiple services.

Core Features & Use Cases

  • Connectors registration and inspection
  • Bind goals to connectors and manage execution flow with safety gates
  • Troubleshoot dispatcher failures and audit goal state history
  • Quick integration with Shopify, Zapier, Notion, Slack, GitHub Actions, and more

Quick Start

Register a connector and create a mobile goal to execute a guarded workflow across your services.

Frequently Asked Questions about scbe-mobile-connector-orchestrator

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

FAQPage Schema
How do I orchestrate mobile workflows across multiple services like Shopify and Slack?

You orchestrate mobile workflows by registering external connectors for services like Shopify and Slack, binding goals to them, and executing steps with enforced safety gates. The orchestrator manages the execution flow and treats non-2xx responses as failures to ensure safe automation.

What are high-risk approval gates in automated workflow orchestration?

High-risk approval gates are safety rules enforced during workflow step advancement. They pause automated execution to require explicit approval before proceeding with sensitive actions across connected services like GitHub Actions or Zapier, ensuring deterministic event history.

Can I use generic webhooks with a mobile goal orchestrator?

Yes, you can register and use generic webhooks alongside specific connectors like Linear and Discord. The orchestrator binds mobile goals to these webhooks and manages execution flow while preserving deterministic event history for troubleshooting.

How do I troubleshoot dispatcher failures in automated connector workflows?

You troubleshoot dispatcher failures by auditing the goal state history. The orchestrator preserves deterministic event history across connector registration, goal binding, and step advancement, allowing you to inspect exact execution paths and identify non-2xx response failures.

Does the mobile connector orchestrator support Zapier and Notion integrations?

Yes, the orchestrator supports quick integration with Zapier and Notion. It manages external connectors to bind mobile goals, execute steps, and enforce high-risk approval workflows across these platforms and other connected services.

Why does my workflow fail when a connector returns a non-2xx response?

Workflows fail on non-2xx responses because the orchestrator enforces strict safety rules by treating them as execution failures. This prevents invalid step advancement and preserves deterministic event history for safe automated mobile goal orchestration.