skills.rest
sytone
sytoneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

client-compatibility

Detect CLI, VS Code, or other platform surfaces and route agent spawning accordingly.

2|3|Updated Apr 1, 2026
Search Tags:#cli#subagents#orchestration#coordinator#vs-code#platform-detection#agent-spawning
One-click install
npx skills add https://github.com/sytone/botnexus --skill client-compatibility-sytone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/sytone/botnexus --skill client-compatibility-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform differences across Copilot surfaces require the coordinator to detect the environment and adapt spawning behavior to optimize agent execution.

Core Features & Use Cases

  • Platform detection: Identify CLI, VS Code, or other surfaces and select appropriate spawning strategy.
  • Adaptive spawning: Use task, runSubagent, or inline execution based on detected platform.
  • Cross-surface coordination: Batch subagents in VS Code mode and maintain consistent prompts and tool access.

Quick Start

Detect the current Copilot surface and initialize the coordinator to spawn 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 detect the Copilot platform surface for adaptive agent spawning?▼

To detect the Copilot platform surface for adaptive agent spawning, the coordinator identifies whether the environment is CLI, VS Code, or another surface, then selects the appropriate spawning strategy. This ensures safe, predictable spawning without surface-specific dependencies.

Does VS Code support parallel subagent batching and CLI agent spawning?▼

VS Code supports parallel subagent batching, while the coordinator adapts spawning methods across surfaces. It selects task, runSubagent, or inline execution based on the detected platform to maintain consistent prompts and tool access.

What's the best way to coordinate cross-platform agent spawning without surface-specific dependencies?▼

The best way to coordinate cross-platform agent spawning without surface-specific dependencies is using a coordinator that detects the platform surface and conditionally routes spawning behavior, ensuring safe and predictable execution across CLI and VS Code environments.

How do I handle conditional behavior for agent spawning tools across different surfaces?▼

To handle conditional behavior for agent spawning tools across different surfaces, the coordinator detects the platform and routes spawning accordingly, selecting appropriate parallelism and session models for CLI, VS Code, or other detected environments.

Why does my subagent execution fail when switching between CLI and VS Code platforms?▼

Subagent execution may fail when switching between CLI and VS Code platforms due to surface-specific dependencies. The coordinator avoids this by detecting the platform and adapting spawning behavior to ensure safe, predictable execution across surfaces.

Related Skills

Explore More Software Engineering Skills→
lbouriezlbouriez

client-compatibility

Detect active Copilot surfaces and adapt agent spawning strategies.

Community
Intermediate
dotnetdotnet
209

client-compatibility

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

Official
Advanced
usepowershellusepowershell
9

client-compatibility

Detect runtime Copilot surfaces and adapt agent spawning across CLI, VS Code, JetBrains, and GitHub.com.

Community
Advanced
quaid-appquaid-app
3

client-compatibility

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

Official
Advanced