← Back to Skills Marketplace
126
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install model-registry-manager
Description
Detect provider models, deduplicate them, remove unusable ones, register missing models into OpenClaw, and safely keep provider-native model ids/names during...
Usage Guidance
This skill appears to do what it says: read your OpenClaw config (~/.openclaw/openclaw.json), call provider /models and /chat/completions using provider.apiKey entries from that config, produce reports under reports/model-registry, update agents.defaults.models in the config, and optionally restart the gateway. Before installing or scheduling it:
- Back up ~/.openclaw/openclaw.json so you can revert config changes.
- Run a dry run first (use the --dry-run flag when running scripts) and run the validation script to confirm behavior before enabling recurring sync.
- Confirm that provider.apiKey values in your config are correct and intended to be used by this tool; the skill uses those keys to contact provider endpoints.
- Note SKILL.md asks the agent to auto-write a `.learnings/` archive; the bundled scripts do not implement that, but the instruction could be followed by an agent — decide whether you want automatic writebacks to home/workspace.
- Ensure the agent environment has a modern Node runtime (fetch is used) and that you are comfortable with the script calling 'openclaw gateway restart' when --restart is provided.
- Review and/or run the JavaScript files in a safe environment to confirm no local-policy conflicts before enabling scheduled runs.
Capability Analysis
Type: OpenClaw Skill
Name: model-registry-manager
Version: 1.3.0
The skill manages the OpenClaw model registry by reading and writing the main configuration file (openclaw.json), which contains sensitive provider API keys. It includes scripts (sync-models.js, validate-model-sync.js) that perform network requests using these keys and execute shell commands (openclaw gateway restart) to apply changes. Additionally, SKILL.md instructs the agent to establish recurring cron jobs with broad 'exec' and 'read' permissions. While these actions are aligned with the stated purpose of model synchronization, the high-privilege access to credentials and system configuration constitutes a significant security risk.
Capability Assessment
Purpose & Capability
Name/description match the implementation: scripts fetch /models from provider.baseUrl, deduplicate by provider id, probe models, update agents.defaults.models in ~/.openclaw/openclaw.json, and write reports. No unrelated credentials or tools are requested.
Instruction Scope
SKILL.md instructs the agent to inspect config, fetch remote models, validate before writing, schedule recurring jobs, and maintain a `.learnings/` archive automatically. The provided scripts implement the core fetch/deduplicate/probe/register/report behavior and write reports under the skill's reports path, but they do not implement the automatic `.learnings/` archival behavior described in SKILL.md (minor mismatch). The instructions also recommend scheduling jobs and allowing exec/read for those jobs; the sync script can run 'openclaw gateway restart' when --restart is passed, which is consistent with the recommendation but grants the skill permission to execute a restart command.
Install Mechanism
No install spec — instruction-only with two included Node scripts. Nothing is downloaded from external URLs or written during an install step.
Credentials
No required env vars are declared. The scripts read provider.apiKey entries from the OpenClaw config file (cfg.models.providers[].apiKey) to call provider endpoints; that is expected for this purpose and no unrelated secrets are requested.
Persistence & Privilege
always:false (good). The skill intentionally modifies the OpenClaw config file (~/.openclaw/openclaw.json) and can run 'openclaw gateway restart' when asked; these are within the skill's purpose but are privileged actions (configuration writes and a restart). Autonomous invocation is allowed by default (not flagged on its own).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install model-registry-manager - After installation, invoke the skill by name or use
/model-registry-manager - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.3.0
Document automatic recurring job installation for OpenClaw agent sessions via first-class cron tool; add validation safety-net and 6-hour sync scheduling guidance.
v1.2.0
Pure registry sync/validate, allowlist/denylist, diff reports, provider stats.
v1.1.0
Generalized provider-wide model sync, generic fallback selection, and merged failover policy guidance.
Metadata
Frequently Asked Questions
What is Model Registry Manager?
Detect provider models, deduplicate them, remove unusable ones, register missing models into OpenClaw, and safely keep provider-native model ids/names during... It is an AI Agent Skill for Claude Code / OpenClaw, with 126 downloads so far.
How do I install Model Registry Manager?
Run "/install model-registry-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Model Registry Manager free?
Yes, Model Registry Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Model Registry Manager support?
Model Registry Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Model Registry Manager?
It is built and maintained by Qihong (@zqh2333); the current version is v1.3.0.
More Skills