skills.rest
sudhakrms
sudhakrmsCOMMUNITY
Explore all skills by this author →
GitHub

client-compatibility

Detect the active host surface and adapt agent spawning across CLI, VS Code, and inline modes.

1|Updated Apr 17, 2026
Search Tags:#automation#cli#cross-platform#coordinator#vs-code#platform-detection#agent-spawning
One-click install
npx skills add https://github.com/sudhakrms/CalendarControl --skill client-compatibility-sudhakrms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill client-compatibility-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform detection and adaptive spawning for multi-surface orchestration across CLI, VS Code, JetBrains, and others.

Core Features & Use Cases

  • Platform Detection: Identify the active surface (CLI, VS Code, or fallback) and switch spawning behavior accordingly.
  • VS Code Spawn Adaptations: Use appropriate subagents and parallelism to maximize responsiveness on VS Code.
  • CLI Dominant Workflow: Leverage task-based spawning when available for richer parameter control.
  • Fallback Inline Mode: Execute directly when surface tools are unavailable, ensuring continuity.

Quick Start

Detect the current platform and spawn the appropriate agents, then coordinate results across CLI, VS Code, or inline modes.

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 host platform and adapt agent spawning for CLI and VS Code?▼

Platform detection identifies the active surface, such as CLI or VS Code, and switches agent spawning behavior accordingly. It enforces compatibility by validating tool presence and preferring CLI tools when available.

What is the best way to handle cross-platform agent spawning when surface tools are unavailable?▼

Cross-platform agent spawning uses a fallback inline mode to execute tasks directly when surface tools are unavailable. This ensures continuity by operating within the detected host surface without relying on external tooling.

Does VS Code support parallel agent spawning for automation workflows?▼

VS Code supports parallel agent spawning by applying platform-specific adaptations. It uses appropriate subagents and parallelism strategies to maximize responsiveness during automation workflows.

Can I use CLI dominant workflows for richer parameter control in multi-surface orchestration?▼

CLI dominant workflows leverage task-based spawning to provide richer parameter control. The coordinator prefers CLI tools when available and validates their presence before execution to enforce compatibility.

Why does agent spawning fail when switching between CLI and editor environments?▼

Agent spawning fails when platform detection cannot validate the required tool presence before execution. The coordinator enforces compatibility by checking the active surface and falling back to inline mode if tools are missing.

Related Skills

Explore More Software Engineering Skills→
QuintenpsQuintenps

client-compatibility

Detect host environments to adapt agent spawning and tool availability.

Community
Advanced
acmelemeacmeleme

client-compatibility

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

Official
Advanced
usepowershellusepowershell
9

client-compatibility

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

Community
Advanced
olivomarcoolivomarco
66

client-compatibility

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

Community
Advanced