client-compatibility

Name: client-compatibility
Availability: InStock
Author: waynewalterberry

Detect the active Copilot platform and adapt agent spawning methods.

Updated Mar 19, 2026

Search Tags:#automation #cli #coordination #vs-code #platform-detection #spawning

Ready to run

npx skills add https://github.com/WayneWalterBerry/MMO --skill client-compatibility-waynewalterberry

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the active Copilot platform and adapts agent spawning accordingly.

Core Features & Use Cases

Platform detection logic to identify the current surface (CLI, VS Code, or other).
Surface-specific spawning rules: CLI uses task for spawning, VS Code uses runSubagent for parallelism, and fallbacks for unsupported surfaces.
Safe, predictable orchestration across tools and environments.

Quick Start

Detect the active platform and apply the appropriate spawning strategy.

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

Platform detection logic identifies the current active surface, such as CLI, VS Code, JetBrains, or GitHub.com. This enables your system to apply the correct spawning strategy and choose the appropriate spawning method for the detected environment.

How do I spawn agents in VS Code for parallel processing?▼

To spawn agents in VS Code for parallel processing, use the runSubagent method. This surface-specific spawning rule ensures parallelism within the VS Code environment, adapting agent orchestration to the active platform correctly.

Does Copilot agent spawning work the same in CLI and VS Code?▼

Copilot agent spawning does not work the same in CLI and VS Code. The CLI surface uses the task command for spawning, while VS Code uses runSubagent for parallelism, ensuring safe and predictable orchestration across different tools and environments.

What is the fallback mechanism for unsupported surfaces during agent spawning?▼

The fallback mechanism for unsupported surfaces provides safe, predictable orchestration by applying conditional tool usage. When platform detection identifies an unsupported surface, it triggers safe fallbacks to ensure cross-environment compatibility without breaking the workflow.

How to coordinate agent spawning across multiple development environments?▼

To coordinate agent spawning across multiple development environments, implement platform detection and conditional tool usage. This applies surface-specific spawning rules across CLI, VS Code, JetBrains, and GitHub.com to ensure safe orchestration across tools.