llm-switcher_skill

Overview

This skill changes OpenClaw's global default LLM model in the config, validates the selected model with a session-only override, and restarts the gateway only after explicit user confirmation. It safeguards configuration by testing availability first, writing the new default only after verification, and confirming restart success before reporting completion.

How this skill works

The skill reads current config keys and lists configured model options and the active default. It asks the user to pick one of the configured aliases or provider/model IDs, then applies a session-only override and runs a short live prompt to confirm the model responds. If the session test passes, the skill updates the global default in config and verifies the change; it will only restart the gateway after the user explicitly agrees and then verifies gateway status.

When to use it

• You want to change the global default LLM for future sessions.
• You need to validate a configured model before committing it as the default.
• You prefer to avoid downtime and want explicit confirmation before gateway restart.
• You need a safe, reversible check that prevents writing a misconfigured default.
• You manage multiple configured model aliases and want to pick one reliably.

Best practices

• Show the current default and all valid configured model choices before prompting for selection.
• Accept only configured aliases or full provider/model IDs; reject unknown names and repeat the valid list.
• Always run a session-only override and require an actual model reply before writing config.
• Verify the config set command by reading back the value and report verification output.
• Ask explicitly for permission to restart the gateway and verify gateway status after restart; do not restart without clear consent.

Example use cases

• Switch the default from one provider/model to another after adding a new model to config and verifying it responds in-session.
• Test a recently added alias (for example codex or opus) by applying a session override, confirming a live reply, and then making it the global default.
• Safely roll back to a previously working default by testing it in-session before writing config and restarting gateway.
• Perform a configuration change during maintenance windows where you only restart the gateway after administrator approval.