model-switch-cobuddy

Switch Hermes profiles to deprecated baidu/cobuddy:free model routing.

4|1|Updated May 15, 2026
One-click install
npx skills add https://github.com/Yasuui/hermes-community-skills --skill model-switch-cobuddy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-switch-cobuddy
Source: https://github.com/Yasuui/hermes-community-skills/tree/main/skills/community/model-switch-cobuddy
Command: npx skills add https://github.com/Yasuui/hermes-community-skills --skill model-switch-cobuddy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It documents how to switch all Hermes profiles to the deprecated baidu/cobuddy:free model so you can understand (or undo) historical configuration changes.

Core Features & Use Cases

  • One-time historical model routing record: Captures the Before → After mapping of chief, forge, intel, and pulse to baidu/cobuddy:free.
  • Config change documentation: Records the specific root config keys affected (default_tier_1 and profile_overrides primaries).
  • Deprecation guidance for current systems: Explains that model routing was removed during 2026-05-18 hardening and that Chief now uses deepseek/deepseek-v4-flash:free instead.

Quick Start

Review the listed profile changes and config keys in this skill to understand what was switched on 2026-05-18, without attempting to apply it to current systems.

Frequently Asked Questions about model-switch-cobuddy

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

FAQPage Schema
How do I find the historical model routing configuration for Hermes profiles before deprecation?

Historical Hermes profile model routing is captured by mapping chief, forge, intel, and pulse profiles to the deprecated baidu/cobuddy:free model. This provides exact per-profile before-and-after mappings for configuration forensics.

What config.yaml fields were changed when retiring Cobuddy model routing?

Retiring Cobuddy model routing changed the default_tier_1 and profile_overrides primaries fields in config.yaml. These root config keys document the specific assignments affected across all Hermes profiles.

Can I still use the baidu/cobuddy:free model routing for current Hermes profile assignments?

No, baidu/cobuddy:free model routing is deprecated and marked tested as not-applicable. Model routing was removed during 2026-05-18 hardening, with Chief now using deepseek/deepseek-v4-flash:free instead.

Why does my Hermes configuration audit show mismatched profile model assignments dated around 2026-05-18?

Configuration audits show mismatches because all Hermes profiles were switched to the deprecated baidu/cobuddy:free state around 2026-05-18. This historical model switch affects chief, forge, intel, and pulse profile assignments.

What is the best way to document a deprecated model routing state for configuration forensics?

The best way is recording exact per-profile before-and-after model mappings alongside the specific config.yaml keys changed. This documents the deprecated baidu/cobuddy:free state without applying it to current systems.

What replaced the deprecated Cobuddy model routing in the Chief profile?

The deprecated Cobuddy model routing in the Chief profile was replaced by deepseek/deepseek-v4-flash:free. Model routing was fully removed during the 2026-05-18 hardening process.