skills.rest
seiggy
seiggyCOMMUNITY
Explore all skills by this author →
GitHub

client-compatibility

Detects Copilot platform and adapts agent spawning behavior for CLI, VS Code, and fallback surfaces.

1|Updated Jul 7, 2026
Search Tags:#cli#subagents#orchestration#vs code#copilot#agent spawning#platform detection
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill client-compatibility-seiggy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/client-compatibility
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill client-compatibility-seiggy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Multi-agent orchestration logic breaks when the same coordinator runs on different Copilot surfaces, because spawning tools, model selection, and SQL availability differ between CLI, VS Code, JetBrains, and GitHub.com. ## Core Features & Use Cases - Platform Detection: Identifies the runtime surface by checking for the task, runSubagent, or agent tools before spawning agents. - Adaptive Spawning: Adjusts parameters per platform, dropping agent_type, mode, model, and description on VS Code while keeping full prompt structure intact. - Feature Degradation Guidance: Provides a table mapping CLI features to VS Code equivalents, including parallel fan-out, Scribe batching, and SQL tool restrictions. - Use Case: A coordinator spawning three parallel agents detects runSubagent on VS Code, issues all three subagent calls in one turn, batches Scribe last, and skips read_agent polling entirely. ## Quick Start Detect the current Copilot platform and spawn the parallel agents using the correct tool and parameters for this surface.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I detect which Copilot platform my agent is running on?▼

Check which spawning tools are available before spawning agents. The `task` tool indicates CLI mode, `runSubagent` or `agent` indicates VS Code mode, and neither means fallback mode where you work inline.

How to spawn parallel subagents in VS Code Copilot?▼

Issue multiple `runSubagent` calls in a single turn with the full prompt as the only parameter. They run concurrently automatically, and results return with the response, so `read_agent` polling is unnecessary.

Does the SQL tool work on VS Code or GitHub.com Copilot?▼

No, the `sql` tool is CLI-only and does not exist on VS Code, JetBrains, or GitHub.com. Cross-platform workflows must use filesystem-based state in `.squad/` files instead of SQL-dependent logic.

Can I select a specific model per subagent in VS Code?▼

No, per-spawn model selection only works on CLI. On VS Code, all subagents use the session model chosen in the model picker, so accept it and log the original intent instead.

Why does fire-and-forget Scribe fail on VS Code?▼

VS Code subagents are synchronous and return results automatically, so background fire-and-forget is impossible. Batch Scribe as the last subagent in any parallel group, since its file operations are light enough to tolerate blocking.

Related Skills

Explore More Software Engineering Skills→
quaid-appquaid-app
3

client-compatibility

Detect the host surface and adapt agent spawning for CLI, VS Code, or fallback.

Official
Advanced
cegit27cegit27
3

checkpoint

Capture and restore git working state with decisions and tasks.

Official
Advanced
CommunityToolkitCommunityToolkit
622

client-compatibility

Detects Copilot platform and adapts agent spawning for CLI, VS Code, and fallback surfaces.

Official
Intermediate
dotnetdotnet
209

client-compatibility

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

Official
Advanced