scbe-admin-autopilot
Operate SCBE in admin mode through the Issac Command Center, watchdog loops, service launchers, cross-talk relay commands, and verified storage or sync runs. Use when the user asks for always-on agent workflows, command-center automation, repo or system health checks, backup or prune lanes, service bootstrapping, or admin-level orchestration.
Best use case
scbe-admin-autopilot is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Operate SCBE in admin mode through the Issac Command Center, watchdog loops, service launchers, cross-talk relay commands, and verified storage or sync runs. Use when the user asks for always-on agent workflows, command-center automation, repo or system health checks, backup or prune lanes, service bootstrapping, or admin-level orchestration.
Teams using scbe-admin-autopilot 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-admin-autopilot/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-admin-autopilot Compares
| Feature / Agent | scbe-admin-autopilot | 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 SCBE in admin mode through the Issac Command Center, watchdog loops, service launchers, cross-talk relay commands, and verified storage or sync runs. Use when the user asks for always-on agent workflows, command-center automation, repo or system health checks, backup or prune lanes, service bootstrapping, or admin-level orchestration.
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 Admin Autopilot Use this skill to run SCBE from the local command-center surface instead of inventing one-off shell commands. ## Entry Surface - Start with `issac-help`. - Prefer `hdoctor` before assuming the local HYDRA surface is healthy. - Read `references/issac-command-center.md` when you need the exact alias list or grouped command map. - The aliases live in `scripts/hydra_command_center.ps1`; install them with `scripts/install_hydra_quick_aliases.ps1` if they are missing. ## Core Lanes 1. Command Center Health Lane - Use `hstatus`, `hqueue`, and `hdoctor` for first-pass health checks. - Use `hwf`, `hcanvas`, `hbranch`, and `hlattice` to prove the major HYDRA surfaces are reachable. 2. Research + Swarm Lane - Use `hresearch`, `hdeep`, `hswarm`, `harxiv`, `harxiv-ml`, `harxiv-get`, and `harxiv-outline` for directed research and swarm work. - Use `hcascade`, `harticle`, or `hmission` when the user wants a multi-step autonomous run instead of a single query. 3. Skill + Memory Lane - Use `hskills-refresh`, `hskills`, and `hstack` for repo-local skill synthesis and stack composition. - Use `hremember`, `hrecall`, and `hsearch` to persist or retrieve working facts. 4. Service + Relay Lane - Use `scbe-api`, `scbe-bridge`, `octo-serve`, and `htunnel` to start the major services and tunnels. - Use `xtalk-send`, `xtalk-ack`, `xtalk-pending`, and `xtalk-health` to keep agent coordination explicit. 5. Agent Continuity + Storage Lane - Keep agents moving with: - `scripts/system/watchdog_agent_stack_default.ps1` - `scripts/system/run_watchdog_loop.ps1` - `scripts/system/register_agent_stack_tasks.ps1` - Run storage shipping, verification, and optional prune with: - `python scripts/system/ship_verify_prune.py --source <path> --dest <backup1> --dest <backup2> --min-verified-copies 2 --delete-source` - Run repo or cloud sync with: - `python scripts/system/system_hub_sync.py --help` ## Safety Gates 1. Do not assume the aliases are loaded; verify with `issac-help` or run the installer. 2. Prefer `hdoctor` or `hstatus` plus `hqueue` before long autonomous runs. 3. Never delete local files unless `--delete-source` is explicitly set. 4. Require checksum verification and at least 2 verified copies before prune. 5. Keep secrets in env vars only. At minimum, check `SCBE_API_KEY` before authenticated API work. 6. Record ports, artifact paths, and cross-talk packet IDs in the run summary. ## Output Contract Each admin run should emit: - command evidence or service status output - artifact paths for storage, workflow, or synthesis outputs - a cross-talk packet or explicit note that no packet was required ## Quick Start ```powershell # inspect the operator surface issac-help hdoctor # run a multi-step mission hmission "stabilize the agent workflow stack" # boot the main API scbe-api ```
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.
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`.
scbe-universal-synthesis
Orchestrate all installed Codex skills through an auto-updating synthesis matrix with Sacred Tongues routing, emotion/intent metadata, and decodable lexicon packets tied to established SCBE characters. Use when the user asks for cross-skill coordination, auto skill updates, multi-skill routing, or Sacred Tongues intent mapping.