About this skill

Problem Context

The service needs to run MCP-related work across different shell environments. Mixing Unix and Windows instructions can break environment setup, call parameters, or authentication context. When MCP calls depend on call parameters and authentication state, the issue is not just script style; it can prevent the service from initializing and invoking as expected. The skill addresses this by making platform routing explicit instead of assuming one shell works everywhere.

How It Works

The skill first identifies the current environment:
- If PowerShell is detected, it uses the Windows branch and loads SKILL_windows.md
- If bash or zsh is detected, it uses the Unix branch and loads SKILL_unix.md

Both branches keep the same MCP semantics, call parameter rules, authentication flow, and security controls. The differences are limited to shell syntax, environment-variable style, and platform-specific setup scripts. It keeps platform differences at the execution layer while preserving a single invocation contract. During execution, only one platform file is loaded, preventing duplicate or conflicting runs.

Boundaries

It is best used as an execution guard for MCP service behavior, focusing on platform routing and consistent invocation rules. If the MCP meaning, authentication path, or business fields need to change, review the corresponding platform file rather than merging both shell instruction sets. It is therefore better treated as an execution boundary, not as a business-feature extension point.

Screenshots

Use Cases

Before connecting the service in a macOS terminal, route to the Unix branch and follow the correct execution notes.
When running the same MCP capability in Windows PowerShell, choose the Windows branch and follow its environment rules.
When reviewing MCP `call` parameters and authentication, confirm only shell syntax differs while semantics stay consistent.
When debugging cross-platform failures, first separate OS routing errors from MCP invocation errors and locate the right notes.

Best For

Platform engineers who need a consistent MCP execution entry across macOS/Linux and Windows, seeking to avoid shell syntax failures.
Integration engineers reviewing MCP authentication and `call` parameters, seeking to keep both platform branches consistent.
Operations engineers maintaining execution rules for the service, seeking OS-specific notes with a single execution path.
Backend engineers integrating data-analysis services across shells, seeking consistent security and invocation semantics.