client-compatibility

Detect the active Copilot platform and spawn agents via the appropriate API.

66|41|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill client-compatibility-olivomarco
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill client-compatibility-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate Copilot-style orchestration across multiple surfaces by automatically detecting the active platform (CLI, VS Code, or other surfaces) and adapting agent spawning, tooling usage, and timing to ensure correct behavior.

Core Features & Use Cases

  • Platform detection: determine availability of task, runSubagent, or agent tools and select the appropriate spawning path.
  • Cross-surface coordination: support CLI, VS Code, and fallback inline execution with deterministic results.
  • Guardrails: honor constraints like SQL tool caveats and parallelism behavior to preserve compatibility across surfaces; provide safe fallbacks when tools are unavailable.

Quick Start

Detect the current Copilot surface and spawn the appropriate agents automatically.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I detect the active Copilot platform and adjust agent spawning accordingly?

Detect the active Copilot platform by checking the availability of task, runSubagent, or agent tools, then select the correct spawning API to adjust agent spawning for CLI, VS Code, or fallback inline execution.

Can I coordinate multi-surface Copilot orchestration across both CLI and VS Code environments?

Yes, multi-surface Copilot orchestration coordinates across CLI, VS Code, and fallback inline execution by detecting the active platform and applying deterministic cross-surface coordination with safe fallbacks when tools are unavailable.

What is the best way to handle parallel spawning and model selection across different Copilot surfaces?

The best way to handle parallel spawning and model selection is to use adaptive platform detection to select the appropriate spawning path, ensuring timing constraints and tool availability checks are honored across different Copilot surfaces.

Why does the SQL tool not work when spawning agents on non-CLI surfaces like VS Code?

The SQL tool has specific limitations on non-CLI surfaces, requiring compatibility guardrails that honor these caveats and provide safe fallback inline execution to preserve correct behavior across VS Code and other platforms.

Do I need to manually check tool availability before spawning subagents in Copilot?

No, you do not need to manually check tool availability because adaptive platform detection automatically determines the availability of task, runSubagent, or agent tools and selects the appropriate spawning path with safe fallbacks.

What happens to agent spawning when task or runSubagent tools are unavailable in my environment?

When task or runSubagent tools are unavailable, the system applies fallback inline execution, ensuring deterministic results by adapting agent spawning, tooling usage, and timing to the detected platform's constraints.