client-compatibility

Detect the hosting surface and select the matching agent spawning pathway.

Updated Apr 14, 2026

Search Tags:#cli #coordinator #parallelism #vs-code #platform-detection #agent-spawning #multi-surface

Ready to run

npx skills add https://github.com/robpitcher/eShopOnWeb --skill client-compatibility-robpitcher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill client-compatibility-robpitcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-agnostic coordination of agent spawning by detecting the hosting surface and adapting behavior for CLI, VS Code, or other environments.

Core Features & Use Cases

Surface detection to tailor agent spawning logic (CLI vs VS Code vs other surfaces).
Conditional spawning pathways for different tools (task, runSubagent, agent).
Safe fallbacks when tools are unavailable, ensuring operations continue.

Quick Start

Detect the current hosting surface and invoke the corresponding agent-spawning path.

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 hosting surface before spawning parallel agents?▼

Detecting the hosting surface involves checking the current environment before spawning parallel agents. This Skill identifies whether the environment is CLI, VS Code, or another surface, then selects the appropriate conditional spawning pathway for multi-surface squads.

What's the best way to handle cross-platform tool availability checks for agent coordination?▼

Handling cross-platform tool availability checks requires enforcing platform detection logic and verifying tool support. This Skill ensures safe fallbacks when tools are unavailable, allowing operations to continue by adapting surface-specific tool usage for task, runSubagent, or agent spawning.

Can I use different agent spawning tools across CLI and VS Code environments?▼

You can use different agent spawning tools across CLI and VS Code environments by applying surface-specific prompts. The Skill detects the hosting surface and routes execution to the appropriate tool pathway, ensuring safe fallbacks when a specific tool is unavailable.

Why does multi-surface squad spawning fail when tools are unavailable?▼

Multi-surface squad spawning fails when tools are unavailable because the environment lacks the required surface-specific tool usage. The Skill prevents this by enforcing platform detection logic and applying safe fallbacks, ensuring operations continue even if a preferred tool is missing.

Do I need platform detection logic to run parallel agents in VS Code?▼

You need platform detection logic to run parallel agents in VS Code because it ensures the correct agent spawning pathway is selected. The Skill detects the hosting surface and applies surface-specific prompts to coordinate parallel spawning safely.

What is surface-specific tool usage in multi-surface agent coordination?▼

Surface-specific tool usage in multi-surface agent coordination means selecting the correct tool pathway, such as task, runSubagent, or agent, based on the detected hosting surface. The Skill enforces this detection logic to tailor agent spawning for CLI or VS Code.