client-compatibility

Detect the Copilot platform and spawn agents via CLI task, VS Code runSubagent, or inline fallback.

Updated Mar 18, 2022
One-click install
npx skills add https://github.com/mpaulosky/dotfiles --skill client-compatibility-mpaulosky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/mpaulosky/dotfiles --skill client-compatibility-mpaulosky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-agnostic coordination for Copilot surfaces requires detecting the active environment and adapting agent spawning behavior to available tools, ensuring reliable task orchestration across CLI, VS Code, and other surfaces.

Core Features & Use Cases

  • Platform detection to choose the optimal spawning path (CLI task, VS Code runSubagent, or inline execution).
  • VS Code adaptations to spawn all concurrent subagents in a single turn and skip per-spawn model selection.
  • Fallback and safety to operate inline when tools are unavailable and maintain guardrails across surfaces.

Quick Start

Configure the coordinator to detect the current Copilot surface and spawn the appropriate agents accordingly.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I coordinate subagent spawning across CLI and VS Code environments?

Detect the active Copilot surface and adapt agent spawning to available tooling, preferring task when both task and runSubagent exist, falling back to inline execution when tools are unavailable.

What is cross-platform agent spawning and when do I need it?

Cross-platform agent spawning detects the active environment and chooses the optimal execution path, ensuring reliable task orchestration across CLI, VS Code, and other surfaces when subagent coordination is required.

Does VS Code support parallel subagent execution for Copilot?

VS Code adaptations spawn all concurrent subagents in a single turn and skip per-spawn model selection, enabling parallel execution where supported while maintaining safety guardrails across surfaces.

What happens when task or runSubagent tools are unavailable?

When task or runSubagent tools are unavailable, the system operates inline as a fallback mode, maintaining guardrails and avoiding prompt injection or unsafe operations by design.

Can I use inline execution as a fallback for agent coordination?

Yes, inline execution serves as a robust fallback when task or runSubagent tools are unavailable, ensuring the coordinator still operates safely while avoiding prompt injection or unsafe operations.

What is the best way to detect platform availability before spawning agents?

The best way to detect platform availability is checking for task or runSubagent availability first, preferring task when both exist, then adjusting spawning behavior to match the detected Copilot surface.