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.
Best use case
scbe-claim-to-code-evidence is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using scbe-claim-to-code-evidence 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-claim-to-code-evidence/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-claim-to-code-evidence Compares
| Feature / Agent | scbe-claim-to-code-evidence | 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?
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.
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.
Related Guides
SKILL.md Source
# SCBE Claim To Code Evidence ## Overview Use this skill to turn SCBE Notion material into repo-backed evidence instead of vague positioning. Start with the local Notion corpus and existing repo manifests, then map each important page or claim to code, tests, and demo surfaces. ## Quick Start 1. Build the starter evidence packet: ```powershell python skills/scbe-claim-to-code-evidence/scripts/build_evidence_packet.py --repo-root . ``` 2. Read the generated outputs: - `artifacts/notion_claim_evidence/starter_manifest.json` - `artifacts/notion_claim_evidence/starter_manifest.md` 3. For deeper matching, run the repo-wide comparator: ```powershell python scripts/compare_notion_to_codebase.py ``` ## Workflow 1. Start from the local inventory, not live search. - Read `docs/notion/NOTION_USEFUL_PAGES_SHORTLIST_2026-03-15.md`. - Read `docs/notion/NOTION_TECH_CORPUS_INVENTORY_2026-03-15.md`. - Use `training-data/notion_raw_clean.jsonl` as the main page-text source. 2. Reuse existing repo mappings first. - Read `docs/notion_pages_manifest.json` before doing new search work. - Treat existing `verification_state` and `code_paths` as the fastest first pass. 3. Build evidence rows per page or claim. - `claim_or_page` - `notion_id` - `source_url` - `repo_code_paths` - `repo_test_paths` - `demo_or_api_paths` - `state`: `implemented|tested|partial|unmapped` - `notes` 4. Search only where the manifest is weak. - Prefer `rg` across `src`, `api`, `scripts`, `docs`, and `tests`. - Search by component nouns, not marketing phrases. - If a page is mostly architectural, map it to the narrowest concrete runtime surface available. 5. Keep proof and aspiration separate. - If a page claims something the repo does not show, mark it `partial` or `unmapped`. - Do not upgrade a claim to `implemented` without at least one concrete repo path. - Prefer explicit test linkage whenever possible. 6. Produce deterministic artifacts. - JSON manifest for machine reuse - Markdown brief for humans - short missing-proof list for next work ## Evidence Rules - Favor pages in `references/priority_pages.json` first. - Favor already-mapped pages in `docs/notion_pages_manifest.json` before new manual crosswalks. - Use `scripts/compare_notion_to_codebase.py` when the page title is known but the implementation path is not. - When a page is patent-facing, look for both code and tests before claiming reduction to practice. ## Output Contract Return: - concise summary of strongest proven pages - list of weak or unmapped pages - artifact paths for JSON and markdown outputs - explicit next mapping targets ## Resources - `references/priority_pages.json`: top Notion pages to map first - `references/evidence_schema.md`: field contract for evidence rows - `scripts/build_evidence_packet.py`: generate a starter evidence manifest from the repo shortlist and existing page manifest
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-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.
scbe-system-engine
Coordinate SCBE-AETHERMOORE math, automation, and service connectors so multi-agent systems can execute work end-to-end. Use when tasks require SCBE dimensional validation, AI-to-AI workflows, browser automation planning, Hugging Face or GitHub/Linear/Notion/Zapier integration, or self-improving skill updates.