scbe-connector-health-check

Estrelas1

Forks0

Atualizado2 de abril de 2026 às 23:21

Run safety-first connector diagnostics for MCP/services used by SCBE so outreach, research, publishing, and runtime calls do not break silently.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Fonte

issdandavis

issdandavis/scbe-aethermoore-demo

Abrir repositório GitHub Ver repositórios do creator

Download

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Administradores de redes e sistemas de computadorInformática e Matemática·SOC 15-1244

SKILL.md

readonly

name	scbe-connector-health-check
description	Run safety-first connector diagnostics for MCP/services used by SCBE so outreach, research, publishing, and runtime calls do not break silently.

SCBE Connector Health Check

Use this skill when connector reliability matters before running social research, outreach, or automation pipelines.

Operating Contract

Verify capability availability before building assumptions.
Record service state as ok, requires_auth, degraded, or down.
Prefer minimal required scope checks first, then deeper verification.
Never claim capability if tool access is not confirmed.
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

Inventory connectors
- list known local connector groups and expected services.
Availability probes
- check tool discoverability and response latency.
Auth & permission check
- confirm required env vars/tokens are configured.
- verify command-level access for critical calls.
Functionality spot-check
- run one non-destructive call per connector (read/list/search only).
Risk annotation
- tag degraded services with:
  - impact level (none/low/medium/high)
  - fallback behavior
  - owner and triage owner if available
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

Mais deste repositório

mesmo repositório

aether-phone-lane-ops

issdandavis/scbe-aethermoore-demo

Boot, recover, tune, and verify the SCBE Android emulator phone lane for AetherCode and Polly Pad. Use when Codex needs to operate the `SCBE_Pixel_6_API35` emulator, repair stale lock state, resize the phone surface, or prove the current lane state from local artifacts.

2026-04-021

aetherbrowser-arxiv-nav

issdandavis/scbe-aethermoore-demo

Navigate arXiv papers and topic searches through AetherBrowser for research extraction workflows. Use when collecting abstracts, paper metadata, and evidence snapshots from arxiv.org.

2026-04-021

aetherbrowser-github-nav

issdandavis/scbe-aethermoore-demo

Navigate GitHub repositories, pull requests, issues, and settings through AetherBrowser tentacle routing. Use when tasks require browser-based GitHub movement, page evidence capture, or coordinated lane assignment with playwriter or playwright.

2026-04-021

aetherbrowser-huggingface-nav

issdandavis/scbe-aethermoore-demo

Navigate Hugging Face models, datasets, and spaces through AetherBrowser for research, validation, and publishing workflows. Use when inspecting repo cards, files, docs, and leaderboard surfaces in browser mode.

2026-04-021

aetherbrowser-notion-nav

issdandavis/scbe-aethermoore-demo

Navigate Notion workspace pages in AetherBrowser for knowledge retrieval and workspace coordination tasks. Use when locating pages, databases, or section paths in browser mode before API operations.

2026-04-021

aetherbrowser-operator

issdandavis/scbe-aethermoore-demo

Operate AetherBrowser as the primary online task surface across search, GitHub, Codespaces, research, Notion, Hugging Face, Shopify, and general web work. Use when Codex should drive a real browser session first, coordinate with built-in search or fetch tools second, capture page-state proof, and keep online work inside the SCBE browser lane instead of defaulting to generic web automation.

2026-04-021

SCBE Connector Health Check

Use this skill when connector reliability matters before running social research, outreach, or automation pipelines.

Operating Contract

Verify capability availability before building assumptions.

Record service state as ok, requires_auth, degraded, or down.

Prefer minimal required scope checks first, then deeper verification.

Never claim capability if tool access is not confirmed.

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

Inventory connectors

list known local connector groups and expected services.

Availability probes

check tool discoverability and response latency.

Auth & permission check

confirm required env vars/tokens are configured.
verify command-level access for critical calls.

Functionality spot-check

run one non-destructive call per connector (read/list/search only).

Risk annotation

tag degraded services with:
- impact level (none/low/medium/high)
- fallback behavior
- owner and triage owner if available

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