skills.rest
CarlosSardo
CarlosSardoCOMMUNITY
Explore all skills by this author →
GitHub

client-compatibility

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

Updated Aug 23, 2026
Search Tags:#cli#subagents#orchestration#vs-code#platform-detection#agent-spawning
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill client-compatibility-carlossardo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/client-compatibility
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill client-compatibility-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Platform detection and conditional spawning logic for CLI (task), VS Code (runSubagent/agent), and fallback inline execution.
  • VS Code-specific adaptations: parallel subagents, session-model handling, and batched scribe in the last turn; automatic result delivery without read_agent.
  • Guardrails for cross-platform compatibility and safe operation across surfaces.

Quick Start

Run the coordinator in your current environment and observe it automatically select the correct spawning method.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema
How do I adapt agent spawning for VS Code and CLI environments?▼

Agent spawning adapts to VS Code and CLI by detecting the active platform and applying conditional logic to choose between task, runSubagent, or inline fallback execution for safe cross-surface orchestration.

What is the best way to manage parallel subagents in VS Code?▼

Managing parallel subagents in VS Code involves using runSubagent for spawning, handling session-model configurations, and batch scribing in the last turn to deliver results automatically without requiring read_agent.

Does cross-surface orchestration support fallback execution when specific tools are unavailable?▼

Cross-surface orchestration supports fallback inline execution when the coordinator detects that specific spawning tools like task or runSubagent are unavailable in the current environment.

How do I run platform detection for Copilot surfaces to choose the correct execution method?▼

Platform detection runs automatically when the coordinator starts, identifying the active Copilot surface to select the correct method between task, runSubagent, or inline execution based on available tools.

Why do I need platform detection logic for subagent orchestration?▼

Platform detection logic is needed for subagent orchestration to ensure safe, parallel subagent management and apply guardrails that maintain compatibility across different execution surfaces like CLI and VS Code.

Related Skills

Explore More Software Engineering Skills→
snow-jallensnow-jallen

client-compatibility

Detect host surfaces and adapt agent spawning across CLI, VS Code, and inline fallbacks.

Community
Advanced
elbrunoelbruno
2

client-compatibility

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

Community
Advanced
khetansarveshkhetansarvesh
1

nanoclaw-repl

Operates and extends the session-aware REPL for maintaining claw.js workflows with zero dependencies.

Community
Intermediate
miethemiethe

workflow-authoring

Author and validate SkillMeat Dynamic Workflow scripts against orchestration contracts.

Community
Advanced