scbe-government-contract-intelligence
Investigate and prioritize U.S. federal and prime-contractor opportunities for SCBE swarm, autonomy, navigation, and AI-governance technologies. Use when evaluating SAM.gov/DIU/AFWERX/SBIR pathways, validating policy/news claims, producing capture plans, or preparing outreach packets for government-adjacent revenue.
Best use case
scbe-government-contract-intelligence is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Investigate and prioritize U.S. federal and prime-contractor opportunities for SCBE swarm, autonomy, navigation, and AI-governance technologies. Use when evaluating SAM.gov/DIU/AFWERX/SBIR pathways, validating policy/news claims, producing capture plans, or preparing outreach packets for government-adjacent revenue.
Teams using scbe-government-contract-intelligence 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-government-contract-intelligence/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-government-contract-intelligence Compares
| Feature / Agent | scbe-government-contract-intelligence | 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?
Investigate and prioritize U.S. federal and prime-contractor opportunities for SCBE swarm, autonomy, navigation, and AI-governance technologies. Use when evaluating SAM.gov/DIU/AFWERX/SBIR pathways, validating policy/news claims, producing capture plans, or preparing outreach packets for government-adjacent revenue.
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 Government Contract Intelligence ## Quick Start 1. Validate market/policy claims first: - check official sources in `references/federal-opportunity-sources.md` before writing positioning copy. - label unverified claims as unverified. 2. Run a source scan: - `python scripts/gov_contract_scan.py --keywords "swarm,autonomy,navigation,ai safety"` - write outputs to `artifacts/contracts/`. 3. Build a capture packet: - use `references/capture-packet-template.md`. - keep a one-page summary per target lane (SBIR, DIU CSO, prime subcontract, OTA/BAA). 4. Produce monetization output: - ranked lane list (where to bid first), - top 5 leads with one-message outreach draft each, - next 14-day action plan with owners. ## Workflow ### 1) Reality Check - verify current events and policy claims with primary or top-tier reporting. - separate facts from assumptions in every output. ### 2) Route Selection - SBIR/STTR path: fast for R&D prototypes and phase funding. - DIU/CSO path: faster transition lane for commercial tech. - Prime subcontract path: near-term revenue through established contractors. - Direct federal prime path: longer cycle, stronger compliance burden. ### 3) Qualification Gate - confirm SAM entity registration readiness and basic compliance posture. - ensure architecture claims map to demonstrable repo artifacts. - reject claims that cannot be linked to code/tests/docs evidence. ### 4) Offer Framing - position SCBE as risk-reduction and interoperability infrastructure: - AI-to-AI coordination - resilient navigation/control logic - governance/auditability layer - autonomous workflow orchestration ### 5) Capture Output - ship a concise packet: - problem statement - capability map - deployment model - integration plan - proof references - pricing hypothesis ## Scripts - `scripts/gov_contract_scan.py`: fetch official lane pages, score keyword relevance, emit JSON/MD briefs. ## References - `references/federal-opportunity-sources.md`: official portals and what each is best for. - `references/capture-packet-template.md`: one-page structure for qualified opportunities. ## Guardrails - do not present rumor as policy. - do not claim contract eligibility that is not verified. - do not claim benchmarks without reproducible evidence. - do not include secrets or private credentials in artifacts.
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.