What problem does it solve?
This Skill solves the friction of making external command-line tools available and reliable inside Hermes agent profiles, especially when a CLI works for the human operator but fails inside isolated agent home directories.
Core Features & Use Cases
- Cross-profile CLI setup: Explains how to make Gemini, Claude Code, and OpenCode accessible across separate agent HOME environments.
- Environment-specific diagnosis: Helps identify whether a tool is installed on Mac local, OVH server, or both, and clarifies which path and auth method applies in each place.
- Model and provider governance: Enforces the approved engine hierarchy, including the rule that code generation must use Claude Opus, Gemini 3.1 Pro, or OpenCode GLM 5.1, and warns against misattributing model provenance.
- Operational troubleshooting: Covers common failures such as isolated credentials, broken symlinks, TUI-only behavior, background-mode issues, and partial binary corruption.
- Use Case: A team member installs Gemini on the server, but agent tasks cannot see it until the correct HOME, credentials, and symlinks are configured for each profile.
Quick Start
Ask the skill to diagnose which of the three approved CLIs is available in the target Hermes environment and to tell you the exact setup needed for agent access.