skills.rest
quaid-app
quaid-appOFFICIAL
Explore all skills by this author →
WebsiteGitHub

client-compatibility

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Platform detection and adaptive spawning across Copilot surfaces (CLI, VS Code, and others) to ensure the coordinator uses the right tools and timing for agent spawning.

Core Features & Use Cases

  • Detects the current surface (CLI, VS Code, JetBrains, GitHub.com) and selects the correct spawning flow.
  • CLI mode uses the task tool for full spawning control, including parameterization of agent_type, mode, model, description, and prompt.
  • VS Code mode uses runSubagent for parallel subagents with a simplified surface, and batches scribe tasks as needed.
  • Fallback mode runs inline when neither CLI nor VS Code tools are available, ensuring continued operation without external tools.

Quick Start

Use the client-compatibility skill to determine the appropriate spawning path for your current surface and begin coordinating agents.

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 for adaptive agent spawning in cross-platform environments?▼

Platform detection identifies the current surface, such as CLI, VS Code, or JetBrains, and selects the correct spawning flow. This ensures the coordinator uses the right tools and timing for agent spawning across different environments.

Can I use the task tool for agent spawning in VS Code?▼

VS Code mode uses the runSubagent tool for parallel subagents rather than the task tool. The task tool is specific to CLI mode and provides full spawning control including parameterization of agent_type, mode, model, description, and prompt.

What happens when neither CLI nor VS Code tools are available for agent coordination?▼

An inline fallback mode runs when neither CLI nor VS Code tools are available. This ensures continued operation without external tools by executing agent coordination directly within the current environment.

Does cross-platform coordination support batched scribe tasks in VS Code?▼

VS Code mode batches scribe tasks as needed using the runSubagent tool. This simplified surface handles parallel subagents effectively while adapting to the specific requirements of the VS Code environment.

Why do I need platform-specific spawning strategies for agent coordination?▼

Platform-specific spawning strategies ensure correct tool usage and timing in each environment. They provide guardrails around prompt, identity, and hygiene in agent coordination while satisfying requirements for cross-platform coordination and conditional tool use.

Related Skills

Explore More Software Engineering Skills→
arisngarisng
5

ghc-docs

Ground responses with official VS Code and Copilot documentation.

Community
Basic
DyreanDyrean

factory-basics

Orchestrate multi-agent workflows with pi-factory to spawn subagents and coordinate results.

Community
Advanced
project-axproject-ax
5

prompt-builder

Assemble AI agent prompts from ordered modules with token budget management.

Official
Advanced
snow-jallensnow-jallen

client-compatibility

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

Community
Advanced