client-compatibility

Detect the active Copilot surface and select the correct agent spawning strategy.

Updated Apr 3, 2026

Search Tags:#vscode #cli #fallback #copilot #agent spawning #platform detection

Ready to run

npx skills add https://github.com/sachinnair90/gitgloss --skill client-compatibility-sachinnair90

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/sachinnair90/gitgloss/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/sachinnair90/gitgloss --skill client-compatibility-sachinnair90

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps coordinators work reliably across different Copilot surfaces by detecting the active environment and choosing the right execution path instead of assuming one tool set fits all.

Core Features & Use Cases

Platform Detection: Identifies whether the session is running in CLI, VS Code, or a fallback surface by checking which tools are available.
Adaptive Spawning: Switches between task-based spawning, subagent execution, or inline work so agent workflows continue to function on every supported surface.
Cross-Surface Guardrails: Avoids unsupported features such as SQL on non-CLI platforms and preserves prompt structure, parallel execution, and result handling rules.
Use Case: A coordinator can fan out multiple agents in CLI, run them concurrently in VS Code, and still complete the work directly when no spawning tool is present.

Quick Start

Use the client-compatibility skill to detect the current Copilot surface and apply the correct spawning and fallback behavior for this task.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema

How do I adapt Copilot agent spawning across different platforms like CLI and VS Code?▼

Adapting Copilot agent spawning across platforms requires detecting the active surface and selecting the correct execution path. This skill identifies whether the session is in CLI, VS Code, or a fallback surface by checking tool availability to ensure workflows continue reliably.

What is the best way to handle fallback execution when Copilot spawning tools are unavailable?▼

Handling fallback execution when spawning tools are unavailable means switching to inline work so agent workflows can still complete. This skill applies safe fallback behavior to ensure tasks finish directly when no task-based or subagent execution tools are present.

Does Copilot coordinator workflow behavior differ between VS Code and CLI?▼

Copilot coordinator workflow behavior differs significantly between VS Code and CLI due to varying tool availability and parallel execution rules. This skill applies surface-specific handling to manage these differences, avoiding unsupported features on non-CLI platforms.

Can I run SQL queries through Copilot agents in VS Code?▼

Running SQL queries through Copilot agents is not supported on non-CLI platforms like VS Code. This skill implements cross-surface guardrails that detect the active environment and avoid invoking unsupported features such as SQL outside of CLI surfaces.

Why does my Copilot coordinator workflow fail when switching environments?▼

Copilot coordinator workflows fail when switching environments because different surfaces have different tool availability and parallel execution behavior. This skill uses tool-aware branching to detect the active surface and apply the correct spawning strategy to prevent failures.