skills.rest
christianhelle
christianhelleCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

client-compatibility

Detect the active platform and spawn agents using the appropriate tool.

413|64|Updated Feb 7, 2023
Search Tags:#cli#fallback#coordinator#parallelism#vs-code#platform-detection#agent-spawning
One-click install
npx skills add https://github.com/christianhelle/refitter --skill client-compatibility-christianhelle
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/christianhelle/refitter/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/christianhelle/refitter --skill client-compatibility-christianhelle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinators running Copilot across CLI, VS Code, and other surfaces must detect the active platform and adapt agent spawning accordingly to ensure correct tooling and coordination.

Core Features & Use Cases

  • Platform Detection: Identify whether the environment supports CLI task tools, VS Code subagents, or requires inline execution and adjust spawning logic accordingly.
  • VS Code Spawn Adaptations: In VS Code mode, spawn all subagents in a single turn and rely on automatic result delivery, dropping per-spawn models and explicit read_agent steps.
  • Fallback Handling: When neither CLI nor VS Code tools are available, execute tasks inline while preserving behavior and safety constraints.

Quick Start

Detect the current platform and spawn agents using the appropriate tool for that 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 the Copilot platform and adapt agent spawning for CLI versus VS Code?▼

Platform detection reads the active environment and tool availability to identify whether Copilot runs in CLI, VS Code, or another surface, then selects the appropriate spawning tool to adapt agent coordination accordingly.

What's the best way to coordinate parallel agents across multiple Copilot surfaces?▼

Coordinating parallel agents across Copilot surfaces requires detecting the active platform and choosing the right spawning mechanism, using task for CLI, runSubagent for VS Code, or inline fallback to maintain compatibility.

Does VS Code Copilot support per-spawn model parameters for subagents?▼

VS Code Copilot does not support per-spawn model parameters. In VS Code mode, the coordinator spawns all subagents in a single turn and relies on automatic result delivery, dropping per-spawn models and explicit read_agent steps.

What happens when neither CLI nor VS Code spawning tools are available in Copilot?▼

When neither CLI nor VS Code spawning tools are available, the coordinator falls back to inline execution, preserving behavior and safety constraints while running tasks directly without dedicated subagent spawning mechanisms.

When do I need platform detection for multi-surface Copilot deployments?▼

Platform detection is needed for multi-surface Copilot deployments where a coordinator must read environment and tool availability to choose between CLI task tools, VS Code subagents, or inline fallback for correct agent spawning.

Related Skills

Explore More Software Engineering Skills→
lbouriezlbouriez

client-compatibility

Detect active Copilot surfaces and adapt agent spawning strategies.

Community
Intermediate
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
Golnaz89Golnaz89

client-compatibility

Detect the platform and adapt agent spawning across CLI, VS Code, and fallback environments.

Community
Advanced