scbe-mobile-connector-orchestrator
Operate the SCBE mobile-goal control plane with external service connectors (Shopify, Zapier, n8n, Slack, Notion, Airtable, GitHub Actions, Linear, Discord, generic webhook). Use when asked to register connectors, bind goals to connectors, run step execution, enforce high-risk approval gates, or troubleshoot connector dispatch failures.
Best use case
scbe-mobile-connector-orchestrator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Operate the SCBE mobile-goal control plane with external service connectors (Shopify, Zapier, n8n, Slack, Notion, Airtable, GitHub Actions, Linear, Discord, generic webhook). Use when asked to register connectors, bind goals to connectors, run step execution, enforce high-risk approval gates, or troubleshoot connector dispatch failures.
Teams using scbe-mobile-connector-orchestrator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scbe-mobile-connector-orchestrator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-mobile-connector-orchestrator Compares
| Feature / Agent | scbe-mobile-connector-orchestrator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Operate the SCBE mobile-goal control plane with external service connectors (Shopify, Zapier, n8n, Slack, Notion, Airtable, GitHub Actions, Linear, Discord, generic webhook). Use when asked to register connectors, bind goals to connectors, run step execution, enforce high-risk approval gates, or troubleshoot connector dispatch failures.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# SCBE Mobile Connector Orchestrator
Use this skill to run phone-driven autonomous workflows through `src/api/main.py` safely.
## Scope
1. Register and inspect connectors.
2. Create and manage mobile goals.
3. Bind connectors to goals.
4. Advance execution with high-risk approval gates.
5. Troubleshoot connector dispatch and auth failures.
## Canonical API Endpoints
1. `GET /mobile/connectors/templates`
2. `POST /mobile/connectors`
3. `GET /mobile/connectors`
4. `GET /mobile/connectors/{connector_id}`
5. `DELETE /mobile/connectors/{connector_id}`
6. `POST /mobile/goals`
7. `GET /mobile/goals`
8. `GET /mobile/goals/{goal_id}`
9. `POST /mobile/goals/{goal_id}/bind-connector`
10. `POST /mobile/goals/{goal_id}/advance`
11. `POST /mobile/goals/{goal_id}/approve`
## Required Safety Rules
1. Never auto-approve high-risk steps when `require_human_for_high_risk=true`.
2. Never execute if connector auth material is missing for protected endpoints.
3. Keep Shopify operations read-safe by default (`payload_mode=shopify_graphql_read`).
4. Treat non-2xx connector responses as failed step dispatch.
5. Preserve deterministic event history and return latest goal state.
## Standard Workflow
1. List templates and pick connector profile.
2. Register connector with minimal valid fields.
3. Create goal in `execution_mode=connector` with that `connector_id`.
4. Call `advance` until:
- `review_required`: request explicit user approval, then call `approve`.
- `completed`: return final state and summary.
- `failed`: return failure reason and dispatch details.
## Shopify Path (Preferred Default)
1. Register connector with:
- `kind=shopify`
- `shop_domain=<store>.myshopify.com`
- `auth_type=header`
- `auth_header_name=X-Shopify-Access-Token`
- `auth_token=<admin_api_token>`
2. Let API auto-build endpoint:
- `https://<store>.myshopify.com/admin/api/<version>/graphql.json`
3. Keep first runs read-only and inspect goal events before adding write workflows.
## Quick Command Templates (PowerShell)
```powershell
$api = "http://localhost:8000"
$key = "demo_key_12345"
Invoke-RestMethod -Method Get -Uri "$api/mobile/connectors/templates" -Headers @{"x-api-key"=$key}
```
```powershell
# register connector
$conn = Invoke-RestMethod -Method Post -Uri "$api/mobile/connectors" `
-Headers @{"x-api-key"=$key} -ContentType "application/json" `
-Body (@{
name = "shopify-admin-read"
kind = "shopify"
shop_domain = "your-store.myshopify.com"
auth_type = "header"
auth_header_name = "X-Shopify-Access-Token"
auth_token = "<TOKEN>"
enabled = $true
} | ConvertTo-Json)
$connectorId = $conn.data.connector_id
```
```powershell
# create and advance goal
$goal = Invoke-RestMethod -Method Post -Uri "$api/mobile/goals" `
-Headers @{"x-api-key"=$key} -ContentType "application/json" `
-Body (@{
goal = "Run storefront operations and publish report"
channel = "store_ops"
priority = "high"
execution_mode = "connector"
connector_id = $connectorId
targets = @("https://your-store.myshopify.com/admin")
require_human_for_high_risk = $true
} | ConvertTo-Json)
$goalId = $goal.data.goal_id
Invoke-RestMethod -Method Post -Uri "$api/mobile/goals/$goalId/advance" -Headers @{"x-api-key"=$key} -ContentType "application/json" -Body "{}"
Invoke-RestMethod -Method Get -Uri "$api/mobile/goals/$goalId" -Headers @{"x-api-key"=$key}
```
## Troubleshooting Matrix
1. `401 Invalid API key` -> confirm `x-api-key` and environment.
2. `404 connector not found` -> connector owner mismatch or deleted connector.
3. `blocked / review_required` -> call `approve` before next `advance`.
4. `connector_http_error` -> inspect endpoint auth/header contract.
5. `connector_network_error` -> endpoint unreachable, TLS/DNS/firewall issue.
## Output Contract
Return:
1. `connector_id` and profile summary.
2. `goal_id`, current `status`, and current step index.
3. Actionable next command (`approve`, `advance`, or fix auth/endpoint).
4. Brief risk note if high-risk steps are pending.Related Skills
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.
scbe-code-scanning-ops
Operate GitHub code scanning and CodeQL remediation for SCBE repositories. Use when triaging code-scanning alerts, mapping alert classes to fix patterns, validating targeted regressions, or wiring dedicated CodeQL workflows and runbooks into the repo.
scbe-world-anvil-lore-rag-7th-tongue
Build and operate a lore-focused RAG system using World Anvil exports and SCBE docs, with deterministic Claude/Codex cross-talk packets for handoff. Use when users ask to structure lore canon retrieval, sync worldbuilding data, enforce citation-grounded generation, or coordinate a 7th Tongue overseer lane across multiple AI agents.
scbe-webtoon-book-conversion
Convert The Six Tongues Protocol and related manuscript sections into webtoon/manhwa storyboard packets, episode roadmaps, panel expansion plans, and image-generation-ready prompt lanes. Use when extending the series storyboard, adapting book chapters into vertical scroll episodes, or keeping art generation tied to canon instead of drifting into generic fantasy panels.
scbe-voice-render-verification
Govern and verify SCBE voice rendering work that maps Langues weighting into breath, phase, and Layer 14 audio-axis packets. Use when implementing or reviewing `scripts/voice_gen_hf.py`, emitting sidecar voice packets, validating canonical tongue ordering, tuning breath planning or phase timing, or keeping voice docs and code aligned with `docs/LANGUES_WEIGHTING_SYSTEM.md` and `docs/specs/SCBE_VOICE_EMOTIONAL_TIMBRE_SYSTEM.md`.