skills.rest
usepowershell
usepowershellCOMMUNITY
Explore all skills by this author →
Website𝕏@usepowershellGitHub

client-compatibility

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

9|1|Updated Jul 21, 2025
Search Tags:#vscode#cli#sql#platform-detection#agent-spawning#scribe#runsubagent
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill client-compatibility-usepowershell
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill client-compatibility-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinators must run reliably across multiple Copilot surfaces (CLI, VS Code, JetBrains, GitHub.com) despite differing tool availability and semantics. This Skill ensures the coordinator detects the runtime surface and adapts spawning, model selection, and tooling usage so agent orchestration works consistently without runtime failures.

Core Features & Use Cases

  • Platform detection: Probe for task, runSubagent/agent, and other tools to determine CLI vs VS Code vs fallback mode.
  • Surface-specific spawning: Use task with background+read_agent on CLI, use runSubagent with parallel single-turn groups on VS Code, or execute inline as a fallback when spawning tools are unavailable.
  • Safety and compatibility rules: Avoid SQL on non-CLI surfaces, batch scribe as the last subagent in parallel groups, preserve prompt structure, and prefer task when both options exist.
  • Use Case: Run a coordinator that launches multiple analysis subagents in parallel from either a developer's VS Code session or an automated CI environment without changing prompts.

Quick Start

Detect the current Copilot surface and spawn agents using task on CLI, runSubagent on VS Code, or execute inline as a fallback.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I run Copilot coordinators across VS Code and CLI without changing prompts?▼

Copilot agent spawning differs across surfaces. This compatibility layer detects the runtime environment and selects task on CLI, runsubagent on VS Code, or inline execution as a fallback, ensuring consistent orchestration without altering your original prompts.

What is the best way to handle agent spawning when tools differ between Copilot surfaces?▼

The best way to handle differing tool availability is platform detection. By probing for task and runsubagent, the system prefers task when both exist, uses runsubagent for parallel single-turn groups on VS Code, and executes inline when spawning tools are unavailable.

Can I use SQL tools in my Copilot coordinator on VS Code or JetBrains?▼

No, you cannot use SQL tools on VS Code or JetBrains. The compatibility rules explicitly avoid SQL on non-CLI surfaces to prevent runtime failures, restricting SQL execution to CLI environments where the tool is properly supported.

How do I batch scribe agents when running parallel subagents on VS Code?▼

To batch scribe agents correctly, the system automatically schedules scribe as the last subagent in parallel groups. This preserves prompt structure and response ordering while adapting the parallel execution to VS Code runsubagent semantics.

Does Copilot agent orchestration work if runsubagent and task are unavailable?▼

Yes, Copilot agent orchestration works by executing inline as a fallback. When spawning tools like task and runsubagent are unavailable, the system degrades gracefully to inline execution to ensure the coordinator completes its tasks without runtime failures.

Why does my Copilot coordinator fail when run in different environments?▼

Copilot coordinators fail across environments due to differing tool semantics and availability. Without platform detection, a coordinator may attempt to use unsupported tools like SQL on VS Code or fail to spawn agents, causing runtime orchestration failures.

Related Skills

Explore More Software Engineering Skills→
olivomarcoolivomarco
66

client-compatibility

Detect the active Copilot platform and spawn agents via the appropriate API.

Community
Advanced
vosslabvosslab
2

html-game-parallel-builder

Coordinate parallel subagent tasks for building TypeScript browser games.

Community
Advanced
christianhellechristianhelle
413

client-compatibility

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

Community
Intermediate
jperezdelrealjperezdelreal

client-compatibility

Detect platform and spawn agents via task, runSubagent, or inline fallback.

Community
Advanced