skills.rest
jperezdelreal
jperezdelrealCOMMUNITY
Explore all skills by this author →
GitHub

client-compatibility

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

Updated Apr 6, 2026
Search Tags:#automation#vscode#cli#cross-platform#coordinator#platform-detection#agent-spawning
One-click install
npx skills add https://github.com/jperezdelreal/GymBro --skill client-compatibility-jperezdelreal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/jperezdelreal/GymBro/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/jperezdelreal/GymBro --skill client-compatibility-jperezdelreal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform-detection and adaptive spawning for Copilot across CLI, VS Code, and other surfaces to ensure the coordinator chooses the correct tool and orchestration flow.

Core Features & Use Cases

  • Platform detection: identify whether CLI task tool is available, VS Code runSubagent/agent is available, or neither, and choose the appropriate spawning strategy.
  • VS Code spawning adaptations: in VS Code mode, spawn all concurrent subagents in a single turn and avoid per-spawn model selection, with results returned inline.
  • Fallback handling: gracefully execute inline when no platform tools are available.

Quick Start

Detect the current surface and spawn agents with the correct tool (task for CLI, runSubagent for VS Code) or execute inline when neither is available.

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 current platform and spawn Copilot subagents correctly across CLI and VS Code?▼

Platform detection identifies whether CLI task tools or VS Code runSubagent tools are available, then chooses the correct spawning strategy. It automatically selects the appropriate tool to ensure Copilot orchestration works across different surfaces.

What is the best way to handle cross-platform agent spawning when neither CLI nor VS Code tools are available?▼

Cross-platform agent spawning falls back to executing inline when neither platform tools are available. This graceful fallback handling ensures orchestration workflows continue running safely without relying on specific surface-specific tools.

Does VS Code spawning support per-spawn model selection for concurrent subagents?▼

VS Code spawning does not support per-spawn model selection. It spawns all concurrent subagents in a single turn and returns results inline, adapting the orchestration flow to fit VS Code surface constraints.

Why does Copilot orchestration fail when using SQL commands on non-CLI surfaces?▼

Copilot orchestration fails because platform-detection rules enforce safe fallback behavior to avoid SQL on non-CLI surfaces. The coordinator detects the active platform and restricts tools to prevent incompatible command execution.

How to ensure a coordinator chooses the correct tool for Copilot orchestration workflows?▼

To ensure correct tool selection, platform detection checks for CLI task availability and VS Code runSubagent availability, then applies preferred tools and safe fallback behavior. This enforces precise tool selection across surfaces.

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
mcampbellrmcampbellr

gsd-fast

Execute simple one-sentence tasks inline without planning or subagent spawning.

Community
Basic
arisngarisng
5

ghc-docs

Ground responses with official VS Code and Copilot documentation.

Community
Basic
PlagueHOPlagueHO
2

client-compatibility

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

Community
Intermediate