本文へ移動
cccskills
無料GitHub で公開

provider-health

Starter: one-screen provider health summary — availability, auth method, version drift, and cost posture for every seatable provider

インストール方法を見る

含まれるファイル(2)

  • SKILL.md1.9 KB
  • agents/openai.yaml164 B

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Provider Health Check Summary (Starter Pack)

Produce a one-screen health summary of every provider Octopus can seat, so the user knows what a workflow will actually dispatch to before spending money.

When to use

The user asks "what providers do I have?", a workflow banner showed (unavailable - skipping), or a session is starting on a new machine.

Steps

  1. Detect. Run ${CLAUDE_PLUGIN_ROOT}/scripts/helpers/check-providers.sh and ${CLAUDE_PLUGIN_ROOT}/scripts/helpers/check-versions.sh.
  2. Summarize per provider. For each seat report: available or not, auth method (env key, oauth session, subscription), and the model it would resolve to today. Include the claude-sdk seat when CLAUDE_SDK_API_KEY is set (Agent SDK, Opus 5 by default, 1M context). Flag Claude Code older than v2.1.280 for Opus 5.5, older than v2.1.219 for Opus 5, and Codex CLI older than v0.144.0 for GPT-5.6.
  3. Flag problems, ranked. Expired auth first (breaks dispatch), then version drift (behavior skew), then missing optional providers (reduced diversity). One line each with the exact fix command (grok login, opencode auth login, key export).
  4. State the cost posture. Split the roster into included (Claude, agy, copilot, ollama, cursor-agent) versus billed (codex, perplexity, grok, openrouter, atlascloud, claude-sdk) so the user can predict what a multi-provider workflow costs before running it.

Output shape

A single table, one row per provider, columns: Provider, Status, Auth, Model, Cost. Below it, at most three ranked fix-it lines. No prose beyond that.

Guardrails

  • Report only what the detection scripts return this session. A provider that worked yesterday but fails detection now is DOWN; do not soften it.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Starter: interpret a council run's verdict artifacts — quorum, dissent, cross-lab validity, and what to do next

日本語の概要は準備中です。原文の説明を表示しています。

nyldn/claude-octopus4,2152026年10月11日 更新

Starter: frame a decision as a multi-model debate — picks sides, seats providers, and launches /octo:debate with a well-formed motion

日本語の概要は準備中です。原文の説明を表示しています。

nyldn/claude-octopus4,2152026年10月11日 更新

Multi-AI requirements scoping using available external providers (Double Diamond Define phase). Priority triggers: octo define, octo scope, co-define, co-scope. DO NOT use for implementation, research, review/validation, or built-in commands.

日本語の概要は準備中です。原文の説明を表示しています。

nyldn/claude-octopus4,2152026年10月11日 更新

Multi-AI validation, scoring, and review using available external providers (Double Diamond Deliver phase)

日本語の概要は準備中です。原文の説明を表示しています。

nyldn/claude-octopus4,2152026年10月11日 更新

Multi-AI implementation using available external providers (Double Diamond Develop phase). DO NOT use for simple code edits, reading/reviewing code, built-in commands, or trivial single-file changes.

日本語の概要は準備中です。原文の説明を表示しています。

nyldn/claude-octopus4,2152026年10月11日 更新

Multi-AI research using available external providers (Double Diamond Discover phase) - Questions about best practices, patterns, or ecosystem research PRIORITY TRIGGERS (always invoke): "octo research", "octo discover", "co-research", "co-discover" DO NOT use for: simple file searches (use Read/Grep), questions Claude can answer directly, debugging issues (use skill-debug), or "what are my options" for decision support.

日本語の概要は準備中です。原文の説明を表示しています。

nyldn/claude-octopus4,2152026年10月11日 更新

nyldn のスキルをすべて見る

このスキルの問題を報告する