scbe-connector-health-check
Run safety-first connector diagnostics for MCP/services used by SCBE so outreach, research, publishing, and runtime calls do not break silently.
Best use case
scbe-connector-health-check is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Run safety-first connector diagnostics for MCP/services used by SCBE so outreach, research, publishing, and runtime calls do not break silently.
Teams using scbe-connector-health-check 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-connector-health-check/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scbe-connector-health-check Compares
| Feature / Agent | scbe-connector-health-check | 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?
Run safety-first connector diagnostics for MCP/services used by SCBE so outreach, research, publishing, and runtime calls do not break silently.
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 Connector Health Check
Use this skill when connector reliability matters before running social research, outreach, or automation pipelines.
## Operating Contract
1. Verify capability availability before building assumptions.
2. Record service state as `ok`, `requires_auth`, `degraded`, or `down`.
3. Prefer minimal required scope checks first, then deeper verification.
4. Never claim capability if tool access is not confirmed.
5. Always return explicit next action for each degraded connector.
## Scope
Use this for:
- checking MCP server/tool availability
- verifying API auth and endpoint reachability
- validating connector prerequisites for marketing/outreach workflows
- periodic health snapshots for SCBE runbooks
## Quick Health Workflow
1. Inventory connectors
- list known local connector groups and expected services.
2. Availability probes
- check tool discoverability and response latency.
3. Auth & permission check
- confirm required env vars/tokens are configured.
- verify command-level access for critical calls.
4. Functionality spot-check
- run one non-destructive call per connector (read/list/search only).
5. Risk annotation
- tag degraded services with:
- impact level (none/low/medium/high)
- fallback behavior
- owner and triage owner if available
6. Publish health record
- provide compact checklist and ordered repair steps.
## Output Contract
- `inventory`: expected services + owner intent.
- `status`: per-connector status map.
- `checks`: quick probe results and timestamps.
- `failures`: auth or dependency blockers with exact error text.
- `next_steps`: prioritized remediation commands or decisions.
- `ready_for_live_use`: true only if primary services are green.
## Connector Priority Matrix (example)
- primary: GitHub, Notion, Obsidian, HF, browser service.
- secondary: Linear, Discord/Slack, Telegram, marketplace tools.
- tertiary: optional APIs used only for enrichment.
## Recovery Patterns
- If `requires_auth`: document missing scopes, rotate creds, rerun spot-check.
- If `degraded`: reduce non-critical calls, queue retries, add backoff and cache.
- If `down`: disable workflow branch and use fallback runbook with explicit user visibility.
## References
- `references/connector-health-checklist.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-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.