vendor-status

Check vendor availability, CLI installation, API keys, and dispatch modes.

4|1|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/jankneumann/agentic-coding-tools --skill vendor-status-jankneumann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vendor-status
Source: https://github.com/jankneumann/agentic-coding-tools/tree/main/.agents/skills/vendor-status
Command: npx skills add https://github.com/jankneumann/agentic-coding-tools --skill vendor-status-jankneumann

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rapidly determine whether all configured third-party vendors required by the development environment are reachable and correctly configured, reducing time spent diagnosing integration failures before running multi-agent tasks.

Core Features & Use Cases

  • Consolidated Health Check: Runs a single check across all configured vendors to report API reachability, CLI installation, and API key presence.
  • Dispatch Mode & Agent Configuration Validation: Detects missing or unsupported dispatch modes in agents.yaml and highlights agents that cannot be used for routing.
  • Actionable Recommendations: Produces human-readable tables or JSON output with clear remediation steps such as installing a CLI, setting an environment variable, or fixing agents.yaml entries.

Quick Start

Ask the assistant to run the vendor-status skill to perform a consolidated health check and return a human-readable table or JSON summary.

Frequently Asked Questions about vendor-status

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

FAQPage Schema
How do I check vendor API key validity and CLI installation status before running multi-agent tasks?

To check vendor API key validity and CLI installation status, run a consolidated health check across all configured vendors to report API reachability, CLI presence, and key validation before executing multi-agent tasks.

How do I validate agent dispatch modes and third-party vendor configurations in agents.yaml?

Validate agent dispatch modes by detecting missing or unsupported entries in agents.yaml, highlighting agents that cannot be used for routing, and providing actionable remediation steps to fix configuration issues.

What's the best way to diagnose third-party vendor integration failures across multiple services?

Diagnose third-party vendor integration failures by running a single consolidated health check that tests API reachability, detects installed CLIs, verifies environment variables, and outputs clear remediation steps.

Can I get JSON output from a vendor health check for automated infrastructure diagnostics?

Yes, you can get JSON output from a vendor health check for automated infrastructure diagnostics, alongside human-readable tables, by requesting JSON format when running the consolidated status check.

Do I need the parallel-infrastructure vendor_health.py script to check vendor availability?

Yes, you need access to the parallel-infrastructure vendor_health.py script and agents.yaml file to perform vendor availability checks, detect installed CLIs, and validate dispatch mode support.

Why does my multi-agent task fail when vendor API keys are missing or misconfigured?

Multi-agent tasks fail when vendor API keys are missing or misconfigured because dispatch modes in agents.yaml become unsupported, preventing routing to agents that require valid third-party vendor credentials and reachable APIs.