Client Compatibility

Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces

45 stars 11 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Azure-Samples/agent-skills-dotnet-demo --skill client-compatibility
Manual install
git clone --depth 1 https://github.com/Azure-Samples/agent-skills-dotnet-demo.git /tmp/agent-skills-dotnet-demo
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills-dotnet-demo/.squad/templates/skills/client-compatibility ~/.claude/skills/client-compatibility

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

## Context

Squad runs on multiple Copilot surfaces (CLI, VS Code, JetBrains, GitHub.com). The coordinator must detect its platform and adapt spawning behavior accordingly. Different tools are available on different platforms, requiring conditional logic for agent spawning, SQL usage, and response timing.

## Patterns

### Platform Detection

Before spawning agents, determine the platform by checking available tools:

1. **CLI mode** — `task` tool is available → full spawning control. Use `task` with `agent_type`, `mode`, `model`, `description`, `prompt` parameters. Collect results via `read_agent`.

2. **VS Code mode** — `runSubagent` or `agent` tool is available → conditional behavior. Use `runSubagent` with the task prompt. Drop `agent_type`, `mode`, and `model` parameters. Multiple subagents in one turn run concurrently (equivalent to background mode). Results return automatically — no `read_agent` needed.

3. **Fallback mode** — neither `task` nor `runSubagent`/`agent` available → work inline. Do not apologize or explain the limitation. Execute the task directly.

If both `task` and `runSubagent` are available, prefer `task` (richer parameter surface).

### VS Code Spawn Adaptations

When in VS Code mode, the coordinator changes behavior in these ways:

- **Spawning tool:** Use `runSubagent` instead of `task`. The prompt is the only required parameter — pass the full agent prompt (charter, identity, task, hygiene, response order) exactly as you would on CLI.
Read the full skill on GitHub

Details

Skill name
client-compatibility
Path
.squad/templates/skills/client-compatibility/SKILL.md
License
MIT
Repo updated
10 April 2026

FAQ

What does the Client Compatibility skill do?

Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces

How do I install the Client Compatibility skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Azure-Samples/agent-skills-dotnet-demo --skill client-compatibility. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Client Compatibility popular?

It lives in Azure-Samples/agent-skills-dotnet-demo, which has 45 GitHub stars and 11 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.