client-compatibility

Name: client-compatibility
Availability: InStock
Author: nicolehaugen

Detect platform compatibility across CLI, VS Code, JetBrains, and GitHub.com.

Updated Apr 8, 2026

Search Tags:#CLI #VS Code #Copilot #agent spawning #platform detection

Ready to run

npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill client-compatibility-nicolehaugen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: client-compatibility
Source: https://github.com/nicolehaugen/CustomMetricsDashboard/tree/main/.squad/templates/skills/client-compatibility
Command: npx skills add https://github.com/nicolehaugen/CustomMetricsDashboard --skill client-compatibility-nicolehaugen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures seamless platform detection and adaptive spawning for CLI, VS Code, and other surfaces, optimizing the orchestration of agent behavior across various Copilot environments.

Core Features & Use Cases

Platform Detection: Identifies and adapts to different Copilot surfaces like CLI, VS Code, JetBrains, and GitHub.com.
Conditional Logic: Implements conditional behavior for agent spawning, SQL usage, and response timing based on the platform.
VS Code Adaptations: Specific spawn and behavior modifications for VS Code environment to optimize performance.
Feature Degradation Table: Provides a clear guide on how features behave across different platforms, ensuring minimal impact on user experience.
Security and Safety: Ensures that scripts and prompts are secure and do not pose risks to user systems or data.

Quick Start

Use the client-compatibility skill to detect and adapt spawning behavior across different Copilot environments.

Frequently Asked Questions about client-compatibility

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

FAQPage Schema

How do I detect which Copilot platform I am running in to adjust agent spawning behavior?▼

Platform detection identifies and adapts to different Copilot surfaces like CLI, VS Code, JetBrains, and GitHub.com. This ensures seamless agent spawning and task execution by implementing conditional logic based on the detected environment.

Can I use the same agent workflow across CLI, VS Code, and JetBrains Copilot environments?▼

Yes, you can orchestrate multi-platform agent workflows across CLI, VS Code, JetBrains, and GitHub.com. The skill optimizes agent behavior and task execution to ensure efficient and secure completion across these different Copilot surfaces.

How do I handle feature degradation for Copilot agents when switching between VS Code and CLI?▼

A feature degradation table provides a clear guide on how features behave across different platforms. This ensures minimal impact on user experience by defining specific spawn and behavior modifications for environments like VS Code.

What is the best way to orchestrate multi-platform agent workflows securely across different Copilot surfaces?▼

Orchestrating multi-platform agent workflows securely requires adapting agent spawning with conditional logic based on platform detection. This approach ensures scripts and prompts remain secure and do not pose risks to user systems or data.

Does Copilot agent spawning require conditional logic for SQL usage and response timing across different platforms?▼

Yes, conditional logic is required to manage SQL usage and response timing based on the detected platform. Implementing these platform-specific rules optimizes agent performance and task execution across various Copilot environments.

Why does my agent spawning behavior change when moving from VS Code to GitHub.com?▼

Agent spawning behavior changes because the platform detection implements environment-specific adaptations. VS Code has specific spawn and behavior modifications designed to optimize performance, which differ from other surfaces like GitHub.com.