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.
Best use case
scbe-document-management is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using scbe-document-management 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-document-management/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-document-management Compares
| Feature / Agent | scbe-document-management | 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?
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.
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 Document Management Use this skill when documentation is drifting, duplicated, or too mixed to trust quickly. ## Workflow 1. Read `AGENTS.md`. 2. Read `CANONICAL_SYSTEM_STATE.md`. 3. Read `REPO_SURFACE_MAP.md`. 4. Read `docs/operations/DOCUMENT_MANAGEMENT_OPERATING_MODEL.md`. 5. Identify the target topic and classify every relevant file as canonical, operational, public, runtime reference, exploratory, historical, or generated. 6. Consolidate toward the highest-authority valid destination. 7. Leave lower-authority files as pointers, legacy notes, or historical context instead of letting them silently redefine the system. ## Working Rules - Update canonical docs before public docs. - Treat runtime code and proving tests as stronger than explanatory notes. - Do not let generated outputs, corpora, or storage-heavy folders define the repo narrative. - If one topic has multiple “master” files, reduce it to one authority file and demote the rest. - Prefer small consolidation passes over giant rewrites. ## River Map Rules Use the document channels from `references/document-channels.md`: - main channel = canonical + operational - side channel = useful support docs - archive channel = preserved history - dry channel = exploratory notes - gated channel = generated evidence and storage-heavy outputs When in doubt, move the working truth toward the main channel and keep everything else explicitly downstream of it. ## Good Targets Use this skill for: - formula drift cleanup - status-language cleanup - repo startup map cleanup - funding / proposal contact consolidation - converting scattered notes into one operator file - deciding whether a doc belongs in `docs/`, `notes/`, or a generated path ## Avoid These Mistakes - Do not treat `README.md` as mathematical authority. - Do not promote research notes straight into canonical docs without checking runtime/test reality. - Do not delete historical files just because they are stale; demote them first. - Do not use storage-heavy folders as the source of truth for process or architecture. ## Optional Future Extension If a stateful document registry is later built with Cloudflare Agents SDK, keep it as an operator over this manual model: - stateful registry of document classes - workflow-based promotion from exploratory → canonical - audit trail for document authority changes That future agent should enforce this model, not invent a second one. ## References - `references/document-authority.md` - `references/document-channels.md` - `references/cloudflare-doc-registry-agent.md`
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-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.
cloud-storage-local-storage-management
Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.
shopify-management-ops
Run Shopify management from terminal with audit-first checks, product sync, storefront gate control, and optional live publish. Use when the user asks to manage Shopify products, storefront state, or monetization operations.
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`.