← Back to Skills Marketplace
patrick-erichsen-2

Migrate Model Defaults

by Patrick Erichsen · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
45
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install migrate-model-defaults
Description
Find, classify, and update hardcoded default-like model references in a repo. Use when the user wants to replace model strings, audit model defaults, central...
README (SKILL.md)

Migrate Model Defaults

Workflow

Be terse. Minimal prose. Ask only necessary questions.

Ask first:

  • Existing model string to replace?
  • New model string to use?

Then search for the old string and likely variants:

  • If old is provider/model, also search bare model.
  • If old is bare, ask whether to include provider-qualified forms.
  • Pay special attention to .github/workflows/**; this repo often has workflow defaults in env, action with.model, and shell args such as --model, --alt-model, and --candidate-label.

Ignore expected noise up front unless it controls default behavior:

  • changelog text
  • tests and fixtures
  • QA mock fixtures and mock catalogs
  • provider catalogs and model availability lists
  • model capability, compatibility, or alias handling
  • generated schema examples
  • plain docs examples

Keep only default-like references:

  • configured defaults or fallback defaults
  • workflow/action defaults
  • CI, QA, release, E2E, or smoke default models
  • i18n/docs generation defaults
  • hardcoded runtime feature defaults

Group candidates semantically, then present a concise checklist with repo-root-relative file refs and one short reason each. Do not edit until the user selects items.

When editing:

  • Update only selected items.
  • Preserve whether each site expects a bare model id or provider-qualified ref.
  • If centralizing repeated workflow defaults, prefer repository variables such as OPENCLAW_CI_OPENAI_MODEL, OPENCLAW_CI_OPENAI_MODEL_BARE, and an explicit alt-model variable when needed.
  • If centralizing source defaults, prefer an existing shared defaults module before adding a new one.
  • Ask if string shape or ownership is unclear.

Validation:

  • Run the repo-required first pass before searching when applicable.
  • For workflow edits, run actionlint if available or via go run github.com/rhysd/actionlint/cmd/actionlint@latest \x3Cfiles>.
  • Run the repo’s changed gate with the correct base. If the default base points at a stale fork, rerun against the real upstream base and report that.
  • Scan the touched surface for remaining old-model literals.
Usage Guidance
Install this if you want help auditing and changing hardcoded model defaults. Review the proposed checklist carefully before approving edits, because changing defaults can affect CI, tests, release workflows, or runtime behavior.
Capability Assessment
Purpose & Capability
The skill can guide edits to model defaults in source and workflow files, which can affect CI or runtime behavior, but that capability directly matches its stated purpose.
Instruction Scope
It tells the agent to ask for the old and new model strings, classify candidates, present a checklist, and edit only user-selected items.
Install Mechanism
The artifact contains only a SKILL.md and a small YAML interface file, with no executable scripts, declared dependencies, or install-time commands.
Credentials
Repository searching, workflow-focused review, actionlint, and repo validation are disclosed and proportionate for updating model defaults, though users should expect normal repo test/check commands to run when approved.
Persistence & Privilege
No artifact-backed evidence shows background workers, persistence hooks, credential or session access, privilege escalation, network exfiltration, or hidden behavior.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install migrate-model-defaults
  3. After installation, invoke the skill by name or use /migrate-model-defaults
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of migrate-model-defaults - Finds, classifies, and updates hardcoded model default references in a repository. - Guides users to identify an existing model string to replace and a new string to use. - Filters out noise (such as changelogs, tests, and docs examples) to focus on default-like references. - Groups candidate references semantically and presents a concise checklist for user selection—no edits until review. - Centralizes workflow and source defaults using repository variables or shared modules when applicable. - Provides workflow-aware validation, including optional actionlint and repo-required checks, and scans for remaining old-model literals.
Metadata
Slug migrate-model-defaults
Version 1.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Migrate Model Defaults?

Find, classify, and update hardcoded default-like model references in a repo. Use when the user wants to replace model strings, audit model defaults, central... It is an AI Agent Skill for Claude Code / OpenClaw, with 45 downloads so far.

How do I install Migrate Model Defaults?

Run "/install migrate-model-defaults" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Migrate Model Defaults free?

Yes, Migrate Model Defaults is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Migrate Model Defaults support?

Migrate Model Defaults is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Migrate Model Defaults?

It is built and maintained by Patrick Erichsen (@patrick-erichsen-2); the current version is v1.0.0.

💬 Comments