scbe-docker-workflow
Coordinate SCBE Docker workflows from build to runtime. Use for SCBE container commands, docker-compose service startup, health checks, and troubleshooting of image/build failures, port conflicts, and container startup issues in SCBE repos.
Best use case
scbe-docker-workflow is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Coordinate SCBE Docker workflows from build to runtime. Use for SCBE container commands, docker-compose service startup, health checks, and troubleshooting of image/build failures, port conflicts, and container startup issues in SCBE repos.
Teams using scbe-docker-workflow 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-docker-workflow/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-docker-workflow Compares
| Feature / Agent | scbe-docker-workflow | 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?
Coordinate SCBE Docker workflows from build to runtime. Use for SCBE container commands, docker-compose service startup, health checks, and troubleshooting of image/build failures, port conflicts, and container startup issues in SCBE repos.
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 Docker Workflow ## Quick Start 1. Change to repo: - `C:\Users\issda\SCBE-AETHERMOORE-working` 2. Verify Docker files: - `Dockerfile` - `docker-compose.yml` - `docker-compose.api.yml` - `docker-compose.unified.yml` 3. Run the standard command for your target stack: - Single image: `npm run docker:build` then `docker run -it -p 8000:8000 scbe-aethermoore:latest` - Single compose: `npm run docker:compose` - API compose: `docker-compose -f docker-compose.api.yml up -d` - Unified stack: `docker-compose -f docker-compose.unified.yml up -d` ## Standard Operations - Build image: - `docker build -t scbe-aethermoore:latest .` - `docker build -t scbe-aethermoore .` - Run container directly: - `docker run -it scbe-aethermoore:latest` - Add port mapping when testing API locally, typically `-p 8000:8000` - Start compose stacks: - `docker-compose up -d` - `docker-compose -f docker-compose.api.yml up -d` - `docker-compose -f docker-compose.unified.yml up -d` ## Health and Runtime Checks - `docker ps` - `docker logs <container>` - Health check endpoints: - `http://localhost:8000/v1/health` (API-focused compose) - `http://localhost:8080/health` (unified gateway and Dockerfile default health test) - `docker ps -f health=unhealthy` to spot failing healthchecks ## Troubleshooting Playbook - Build errors before compile step: - Retry with `docker build --no-cache -t scbe-aethermoore:latest .` - Check for transient network errors downloading build toolchains (Node/Python/liboqs) - Container exits immediately: - `docker logs <container>` - Validate expected env vars from stack file and `.env` usage - Port conflicts: - Check host ports `8000`, `8080`, and `3000` are free before mapping - Use compose alternatives or remap ports in a temporary override - Compose startup stalls: - `docker-compose logs -f` - Confirm required service health using container logs and `docker ps -f status=running` ## Reference and Deep Context For full stack maps, service-level expectations, and deeper remediation steps, read: - [references/docker-stack.md](references/docker-stack.md) ## Automation Assets Use the troubleshooting script when you need repeatable diagnostics: - `scripts/scbe_docker_status.ps1` - `assets/action-summary.template.yaml` Example usage: - `.\scripts\scbe_docker_status.ps1 -RepoPath . -InspectStacks -ShowLogs` - `.\scripts\scbe_docker_status.ps1 -RepoPath . -ContainerName scbe-core -LogTail 120` - `.\scripts\scbe_docker_status.ps1 -RepoPath . -CleanRestart`
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.