client-compatibility

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

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/elbruno/md-to-slides --skill client-compatibility-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/elbruno/md-to-slides --skill client-compatibility-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves cross-platform orchestration failures by ensuring the coordinator detects the active Copilot surface (CLI, VS Code, or other) and chooses compatible agent-spawning mechanics.

Core Features & Use Cases

  • Platform detection & adaptive spawning: Selects the correct coordination path based on available tools (CLI task, VS Code runSubagent/agent, or inline fallback).
  • Surface-specific execution semantics: Applies VS Code parallelism, drops unsupported parameters (like agent_type, mode, model for subagents), and batches Scribe as the last subagent.
  • Safety guardrails for tool availability: Prevents cross-platform workflows from depending on CLI-only tools like SQL, avoiding silent failures.

Quick Start

Ask the coordinator to detect the current Copilot surface and spawn agents using the compatible strategy 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 adapt multi-agent orchestration for Copilot in VS Code versus CLI?

Multi-agent orchestration adapts to each Copilot surface by detecting available tools and selecting compatible spawning mechanics. The coordinator prefers CLI `task` when present, or uses VS Code `runSubagent` for parallel spawning with unsupported parameters dropped.

Why does agent spawning fail when running cross-platform Copilot workflows?

Agent spawning fails across Copilot surfaces when workflows depend on CLI-only tools like SQL or pass unsupported parameters. The coordinator prevents these silent failures by detecting the active platform and applying surface-specific execution semantics with safety guardrails.

Can I use parallel subagent spawning in VS Code without the CLI task tool?

Yes, parallel subagent spawning works in VS Code without the CLI `task` tool by using single-turn `runSubagent` execution. The coordinator drops unsupported parameters like `agent_type`, `mode`, and `model`, batching Scribe as the last subagent for consistent prompt structure.

What is the best way to handle Scribe agents in coordinator-driven multi-agent workflows?

Handling Scribe agents in coordinator-driven workflows requires batching Scribe as the last subagent during parallel fan-out. This ensures consistent prompt structure across Copilot surfaces and prevents orchestration failures when adapting spawning behavior for CLI versus VS Code environments.

When should I not use SQL-dependent logic in Copilot agent orchestration?

SQL-dependent logic should not be used in Copilot agent orchestration outside the CLI environment. Cross-platform workflows disallow SQL to avoid silent failures, applying safety guardrails that prevent workflows from depending on CLI-only tools when VS Code or fallback execution is active.