hudl-model-switch

Switch OpenClaw's active model via the hudl provider and restart the gateway.

2|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/Huddle01/openclaw-skills --skill hudl-model-switch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hudl-model-switch
Source: https://github.com/Huddle01/openclaw-skills/tree/main/hudl-model-switch
Command: npx skills add https://github.com/Huddle01/openclaw-skills --skill hudl-model-switch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

OpenClaw agents often need to switch their active LLM or provider model quickly to adapt to tasks, costs, or availability. This skill centralizes the workflow to validate GRU gateway config, map user intent to a hudl model, update agent defaults, restart the gateway, and report the before/after state.

Core Features & Use Cases

  • Validates that a hudl provider exists and points at gru.huddle01.io, ensuring safe switching.
  • Resolves the target model from user input using the GRU catalog, normalizes to hudl/ prefixed IDs, and updates both the active agent and defaults.
  • Restarts OpenClaw after applying changes and reports the before/after model alignment and provider catalog status.

Quick Start

Ask OpenClaw to switch to a model like opus and the skill will validate the GRU gateway, switch to hudl/claude-opus-4.6, and restart the gateway.

Frequently Asked Questions about hudl-model-switch

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

FAQPage Schema
How do I switch the active model in OpenClaw?

To switch the OpenClaw active model, ask the agent to use a new model like opus. The system validates the GRU gateway, maps your intent to a hudl model ID, updates the config, and restarts the gateway.

What is the GRU gateway used for in OpenClaw model switching?

The GRU gateway routes model requests through gru.huddle01.io. Switching models requires validating that a hudl provider exists in the config and points to this gateway before applying updates and restarting.

Do I need jq to switch models via the GRU gateway?

Yes, jq is required as a dependency to switch models via the GRU gateway. The skill uses script-driven updates to normalize catalog IDs and modify the OpenClaw config during the model switch.

How does OpenClaw normalize user intent when switching to a different model?

OpenClaw normalizes user intent by resolving the target model from the GRU catalog and enforcing a hudl/ prefix. This ensures the requested model maps correctly to a valid hudl model ID before updating defaults.

Why does my OpenClaw model switch require a gateway restart?

An OpenClaw model switch requires a gateway restart to apply the updated config defaults. The script executes an openclaw restart and reports the before and after model alignment along with the provider catalog status.