client-compatibility

Detect the runtime surface and spawn agents adaptively across CLI and VS Code.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/Leep-GH/Lee-s-squad --skill client-compatibility-leep-gh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/Leep-GH/Lee-s-squad/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/Leep-GH/Lee-s-squad --skill client-compatibility-leep-gh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects the current runtime surface and adapts agent spawning to the available tooling, ensuring reliable orchestration across CLI and VS Code.

Core Features & Use Cases

  • Platform Detection: identifies the active surface (CLI or VS Code) and selects the correct spawning flow.
  • Adaptive Spawning: uses task-based spawning in CLI mode and runSubagent-based spawning in VS Code mode.
  • Safe Fallbacks: provides inline execution when neither surface tools are available, with graceful degradation.
  • Use Case: deploying agents in a local development environment with VS Code, or in a CLI CI pipeline without IDE integration.

Quick Start

Detect your environment and spawn agents using the appropriate tool.

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 runtime surface and adapt agent spawning for CLI and VS Code?

Platform detection identifies the active surface and selects the correct spawning flow, using task-based spawning in CLI mode and runSubagent-based spawning in VS Code mode.

What happens to cross-platform agent orchestration when neither CLI nor VS Code tools are available?

When neither surface tool is available, adaptive spawning provides safe fallbacks through inline execution with graceful degradation to maintain cross-surface orchestration.

Can I use subagents in a CLI CI pipeline without VS Code IDE integration?

Yes, you can deploy agents in a CLI CI pipeline without IDE integration, as platform detection identifies the CLI surface and applies task-based spawning accordingly.

How does adaptive spawning handle parameter passing across different development surfaces?

Adaptive spawning requires awareness of available tools and applies proper parameter handling alongside cross-surface safety rules to ensure reliable orchestration across surfaces.

When should I use inline execution fallback instead of runSubagent spawning?

Inline execution fallback should be used when platform detection determines that neither CLI task-based spawning nor VS Code runSubagent-based spawning tools are available.