skills.rest
acmeleme
acmelemeOFFICIAL
Explore all skills by this author →
GitHub

client-compatibility

Detect execution surfaces and select agent spawning strategies across CLI and VS Code.

Updated Nov 11, 2025
Search Tags:#cli#cross-platform#coordinator#platform-detection#agent-spawning#visual-studio-code
One-click install
npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill client-compatibility-acmeleme
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator/tree/main/.squad/templates/skills/client-compatibility
Command: npx skills add https://github.com/acmeleme/Conversation-Knowledge-Mining-Solution-Accelerator --skill client-compatibility-acmeleme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform detection and adaptive spawning for CLI vs VS Code and other Copilot surfaces to ensure correct agent orchestration.

Core Features & Use Cases

  • Platform detection and surface-aware spawning logic.
  • VS Code spawn adaptations and parallelism behavior; CLI fallback path.
  • Cross-surface coordination to maintain consistent user experience.

Quick Start

Run the coordinator on the target surface and verify correct spawning behavior for CLI and VS Code.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How does cross-platform agent spawning work across CLI and VS Code?▼

Cross-platform agent spawning detects the current execution surface and routes to the appropriate strategy, prioritizing CLI tools and adhering to VS Code subagent conventions to maintain a consistent user experience.

What happens when CLI tools are unavailable during agent spawning?▼

When CLI tools are unavailable, agent spawning gracefully falls back to inline execution, ensuring tasks still run while maintaining cross-surface coordination across environments like JetBrains and GitHub.com.

Can I coordinate Copilot agent spawning across multiple environments?▼

Yes, platform-aware routing coordinates tool availability, timing, and resource usage across CLI, VS Code, JetBrains, and GitHub.com environments to ensure correct agent orchestration.

How do I detect the execution surface before spawning a subagent?▼

Platform detection identifies the active execution surface before spawning, allowing the system to select the correct strategy, whether that is a CLI task, a VS Code subagent, or an inline fallback.

Does VS Code spawning support parallelism behavior?▼

Yes, the system applies VS Code spawn adaptations and manages parallelism behavior, prioritizing CLI tools when available and falling back to inline execution when tools are missing.

Why do I need adaptive spawning for Copilot surfaces?▼

Adaptive spawning solves platform detection issues by routing tasks to the correct execution surface, preventing orchestration failures and maintaining consistent behavior across CLI, VS Code, and other Copilot environments.

Related Skills

Explore More Software Engineering Skills→
PlagueHOPlagueHO
2

client-compatibility

Detect Copilot platform and adapt agent spawning across CLI, VS Code, and other surfaces.

Community
Intermediate
CommunityToolkitCommunityToolkit
619

client-compatibility

Detect Copilot platform and adapt agent spawning behavior and tool usage.

Official
Advanced
quaid-appquaid-app
3

client-compatibility

Detect the host surface and adapt agent spawning for CLI, VS Code, or fallback.

Official
Advanced
webmaxruwebmaxru
49

client-compatibility

Detect the Copilot platform and adapt spawning behavior across CLI, VS Code, JetBrains, and GitHub.com.

Community
Advanced