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.
Best use case
scbe-universal-synthesis is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using scbe-universal-synthesis 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-universal-synthesis/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-universal-synthesis Compares
| Feature / Agent | scbe-universal-synthesis | 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?
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.
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 Universal Synthesis Use this skill when work spans many installed skills and needs one consistent routing layer. ## Goals 1. Keep a current inventory of installed skills. 2. Route tasks to recommended Sacred Tongues and character lanes. 3. Maintain a decodable lexicon (`prefix:stem`) with emotion + intent. 4. Auto-refresh references so coordination does not drift. ## Core Workflow 1. Refresh synthesis references: ```powershell python C:/Users/issda/SCBE-AETHERMOORE/scripts/system/refresh_universal_skill_synthesis.py ``` 2. Read generated references: - `references/skill_inventory.json` - `references/synthesis_matrix.json` - `references/sacred_lexicon.json` - `references/summary.md` 3. Select skills by intent: - Match user request to `categories` and `recommended_tongues` in `synthesis_matrix.json`. - Pull only the minimal set of skills required for execution. 4. Emit decodable tongue packets: - Use lexicon tokens like `ko:anchor`, `av:forge`, `ru:verify`, `ca:pulse`, `um:guard`, `dr:release`. - Decode rule: prefix maps to tongue metadata; stem maps to action semantic. 5. Execute + cross-talk: - Run selected skills in sequence. - Mirror updates into terminal lane and Obsidian lane when multi-agent handoff is required. ## Tongue/Character Guidance Use canonical mappings from generated `sacred_lexicon.json`: - KO: architect lane (clarity, system design) - AV: coder lane (creative flow, implementation) - RU: reviewer lane (discernment, quality review) - CA: tester lane (assurance, validation) - UM: security lane (vigilance, protection) - DR: deployer lane (resolve, release execution) Prefer established characters from the lexicon payload (`agentic_character`, `runtime_character`) for narrative continuity. ## Safety Rules 1. Never hardcode API keys or secrets in skill files or references. 2. Keep generated references append-safe and reproducible. 3. If a skill has invalid frontmatter, report it and continue with valid skills. 4. Keep orchestration deterministic for governance and audit paths.
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.
skill-synthesis
Compose multiple installed skills into one coordinated execution stack with ordered packets, minimal context load, and deterministic handoff artifacts. Use when tasks span multiple domains (for example HYDRA + browser + training + deploy) and you need a single combined workflow instead of invoking skills one-by-one.
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`.