skills.rest
ronniegeraghty
ronniegeraghtyCOMMUNITY
Explore all skills by this author →
GitHub

client-compatibility

Detect execution surface and adapt Copilot agent spawning for CLI, VS Code, or fallback.

3|5|Updated Mar 19, 2026
Search Tags:#automation#cli#orchestration#copilot#vs-code#platform-detection#spawning
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill client-compatibility-ronniegeraghty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.agents/skills/client-compatibility
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill client-compatibility-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform detection and adaptive spawning for Copilot across CLI, VS Code, JetBrains, and other surfaces, ensuring the coordinator uses the correct tools and timing for agent spawning.

Core Features & Use Cases

  • Platform detection rules to select the appropriate spawning method: CLI task-based spawning, VS Code runSubagent parallel spawning, or inline fallback execution.
  • VS Code-specific behavior that spawns all subagents in parallel and batches Scribe operations for result handling.
  • Robust cross-surface orchestration with safe fallbacks for multi-surface Copilot deployments.

Quick Start

Detect your platform (CLI, VS Code, or other) and spawn Copilot agents with the correct tool for your surface.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I spawn Copilot agents consistently across CLI and VS Code surfaces?▼

VS Code Copilot orchestration spawns all subagents in parallel and batches Scribe operations for result handling, while CLI spawning uses the full parameter surface to manage agent tasks sequentially.

What happens to Copilot orchestration when the execution platform is unrecognized?▼

Platform detection rules identify the execution surface and select the appropriate spawning method, enabling safe fallbacks for multi-surface Copilot deployments across CLI, VS Code, and other environments.

How does platform detection work for adapting Copilot interactions to different surfaces?▼

VS Code-specific behavior includes spawning all subagents in parallel and batching Scribe operations for result handling, ensuring robust cross-surface orchestration with safe fallbacks for multi-surface deployments.

Can I use Copilot spawning orchestration across CLI, VS Code, and other surfaces simultaneously?▼

This ensures the coordinator uses the correct tools and timing for agent spawning across CLI, VS Code, JetBrains, and other surfaces, with safe fallbacks for robust orchestration.

Why do Copilot subagents fail to spawn correctly when switching between VS Code and CLI environments?▼

Adaptive spawning solves this by detecting the execution surface and applying VS Code parallel spawning with batched Scribe operations, or CLI full parameter spawning, ensuring robust cross-surface compatibility.

Related Skills

Explore More Software Engineering Skills→
arisngarisng
5

ghc-docs

Ground responses with official VS Code and Copilot documentation.

Community
Basic
usepowershellusepowershell
9

client-compatibility

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

Community
Advanced
lbouriezlbouriez

client-compatibility

Detect active Copilot surfaces and adapt agent spawning strategies.

Community
Intermediate
snow-jallensnow-jallen

client-compatibility

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

Community
Advanced