skills.rest
lbouriez
lbouriezCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

client-compatibility

Detect active Copilot surfaces and adapt agent spawning strategies.

Updated Mar 27, 2026
Search Tags:#vscode#cli#orchestration#platform-detection#agent-spawning#copilot-surface
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill client-compatibility-lbouriez
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill client-compatibility-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the active Copilot surface and adapts agent spawning accordingly.

Core Features & Use Cases

  • Platform detection that identifies CLI, VS Code, and other surfaces and selects the optimal spawning path.
  • Adaptive spawning strategies for CLI (task tool), VS Code (runSubagent and parallel subagents), and inline fallback.
  • Use Case: ensure seamless agent coordination whether the user runs from the terminal, VS Code, or another environment.

Quick Start

Determine the current surface and spawn the appropriate agents using the platform-detection logic.

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 surface is active so agents spawn correctly?▼

Platform detection identifies the active Copilot surface—CLI, VS Code, JetBrains, or GitHub.com—and selects the optimal spawning path for distributed agents based on tool availability and environment.

Can I spawn parallel subagents in VS Code using the runSubagent tool?▼

Yes, in VS Code the platform detection logic applies the runSubagent tool to enable parallel subagent spawning, while CLI mode prioritizes the task tool for distributed agent orchestration.

What happens to agent spawning when task or runSubagent tools are unavailable?▼

When task and runSubagent tools are unavailable, the platform detection logic implements an inline fallback strategy, ensuring agent coordination continues seamlessly without dedicated spawning tools.

Does agent spawning work across both CLI and VS Code Copilot environments?▼

Yes, the platform detection logic applies adaptive spawning strategies across CLI, VS Code, JetBrains, and GitHub.com Copilot surfaces, handling platform checks and tool availability for seamless agent coordination.

Why does CLI mode get prioritized over VS Code for agent spawning?▼

CLI mode is prioritized because the platform detection logic checks for the task tool first, selecting the terminal as the optimal spawning path before evaluating VS Code parallel subagent capabilities or inline fallback.

Related Skills

Explore More Software Engineering Skills→
olivomarcoolivomarco
66

client-compatibility

Detect the active Copilot platform and spawn agents via the appropriate API.

Community
Advanced
snow-jallensnow-jallen

client-compatibility

Detect host surfaces and adapt agent spawning across CLI, VS Code, and inline fallbacks.

Community
Advanced
jperezdelrealjperezdelreal

client-compatibility

Detect platform and spawn agents via task, runSubagent, or inline fallback.

Community
Advanced
PlagueHOPlagueHO
2

client-compatibility

Detect Copilot platform and adapt agent spawning across CLI, VS Code, and other surfaces.

Community
Intermediate