agent-runtime-status

Reports verified direct-runtime route eligibility for all 12 descriptor-advertised agent actions.

Updated Jul 12, 2026
One-click install
npx skills add https://github.com/sumitake/agent-collab --skill agent-runtime-status-sumitake
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-runtime-status
Source: https://github.com/sumitake/agent-collab/tree/main/plugins/agent-collab/skills/agent-runtime-status
Command: npx skills add https://github.com/sumitake/agent-collab --skill agent-runtime-status-sumitake

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Determining which agent runtimes and logical actions are actually available before launching a multi-agent workflow is error-prone, and a failed dispatch mid-workflow wastes effort. This Skill verifies the installed package's direct-runtime state up front so callers know which routes current policy may consider. ## Core Features & Use Cases - Runtime readiness reporting: Runs migration_doctor.py for legacy-package and host-profile observations, then submits one planning-only routing request covering all 12 descriptor-advertised actions. - Zero-inference verification: Uses dispatch_requested=false with frontier quality and maximum effort to expose every eligible route without consuming provider attempts. - Honest status boundaries: Distinguishes descriptor eligibility from executable presence, authentication, quota, and live provider health, reporting unverified states explicitly. - Use Case: Before dispatching an independent code review across multiple agent providers, run this Skill to confirm which reviewer routes are eligible this session and avoid building a workflow on unavailable runtimes. ## Quick Start Ask the agent to check agent runtime status and list which of the 12 logical actions are currently route-eligible before starting the multi-agent workflow.

Frequently Asked Questions about agent-runtime-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check which agent runtimes are available before a multi-agent workflow?▼

Run the agent-runtime-status check, which submits one planning-only routing request with dispatch_requested=false covering all 12 descriptor-advertised actions. The result shows which routes current policy may consider without consuming any provider attempts.

How to verify an independent reviewer is available for code review?▼

Submit a runtime status request before dispatch to see reviewer route eligibility. Note that eligibility proves descriptor routing only; executable presence, authentication, and live provider health remain unverified unless separate native evidence establishes them.

Does a routing request failure mean the provider is unavailable?▼

No. A client, manifest, local permission, or protocol error is not evidence that the provider is unavailable or needs authentication. Provider state remains unknown unless native evidence establishes it, and a provider should never be invoked as a readiness probe.

What is the difference between route eligibility and live provider availability?▼

Route eligibility comes from a planning-only request and proves the descriptor allows the route under current policy. Live availability, authentication, quota, and provider health are separate facts that planning reports cannot establish.

Why does the status check use frontier quality with maximum effort?▼

Frontier quality with maximum effort exposes every route current policy may consider, making it a verification setting rather than an ordinary-work cost default. This ensures the status report reflects the full eligible route set.