skills.rest
dotnet
dotnetOFFICIAL
Explore all skills by this author →
Website𝕏@dotnetfdnGitHub

client-compatibility

Select platform-appropriate agent spawning behavior for CLI, VS Code, and fallback surfaces.

209|27|Updated Mar 10, 2026
Search Tags:#concurrency#orchestration#copilot#agent spawning#platform detection#vs code integration#sql compatibility
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill client-compatibility-dotnet
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/dotnet/maui-labs --skill client-compatibility-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents brittle orchestration by ensuring the coordinator adapts agent spawning behavior correctly across different Copilot surfaces (CLI vs VS Code vs other environments).

Core Features & Use Cases

  • Platform detection: Selects the right spawning mechanism based on available tools, enabling the same workflow to run reliably across surfaces.
  • Surface-specific spawn adaptations: Uses the correct parameter conventions (e.g., CLI task parameters vs VS Code runSubagent prompt-only) and appropriate concurrency strategy.
  • Safe feature degradation: Avoids unsupported capabilities like the CLI-only sql tool and preserves response ordering requirements when needed.
  • Use case: When an agent workflow must run concurrently (e.g., multiple analysis subagents plus a final Scribe step), this skill coordinates parallel execution correctly without relying on read_agent in VS Code mode.

Quick Start

Ask the coordinator to detect the current surface and then spawn the required subagents using the surface-appropriate tool and parameter rules.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I handle multi-agent orchestration across different Copilot surfaces?▼

Multi-agent orchestration across Copilot surfaces requires platform detection to select the correct agent spawning behavior for CLI, VS Code, and fallback environments. This ensures consistent prompt structure and predictable concurrency handling across different platforms.

Can I spawn parallel subagents in VS Code without using read_agent?▼

Yes, you can spawn parallel subagents in VS Code without read_agent by using the runSubagent prompt-only parameter convention. This approach maintains response ordering requirements while enabling inline parallel execution for multi-agent task scenarios.

Why does my agent workflow fail when moving from CLI to VS Code?▼

Agent workflows fail when moving from CLI to VS Code due to unsupported capabilities like the CLI-only sql tool and different parameter conventions. Cross-platform orchestration requires surface-specific spawn adaptations and safe feature degradation to prevent brittle execution.

What is the best way to detect the current platform for agent spawning?▼

The best way to detect the current platform for agent spawning is performing tool availability checks within the coordinator. This allows the workflow to select the right spawning mechanism and apply surface-specific parameter rules automatically.

Does Copilot CLI support background fan-out for concurrent subagent execution?▼

Yes, Copilot CLI supports background fan-out for concurrent subagent execution by using richer task parameters. This enables advanced concurrency strategies that differ from VS Code's inline parallel subagent spawning approach.

Related Skills

Explore More Software Engineering Skills→
Golnaz89Golnaz89

client-compatibility

Detect the platform and adapt agent spawning across CLI, VS Code, and fallback environments.

Community
Advanced
huangwb8huangwb8
47

multi-agent-coordinator

Coordinate subagents to execute plan tasks with quality gates.

Community
Advanced
vertexcover-iovertexcover-io
4

constitution

Prepend a non-negotiable constitution to every sub-agent prompt.

Official
Advanced
robpitcherrobpitcher

client-compatibility

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

Community
Intermediate