Add Model Provider
openclaw/openclaw
Add and live-prove a model provider with non-interactive config one-liners, without exposing credentials.
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation.
Custom licenceAuto-check passed
Install Validate Provider Changes
$ npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules validate-provider-changes --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/utils/validate-provider-changes .claude/skills/validate-provider-changes && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "validate-provider-changes" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changes into .claude/skills/validate-provider-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-provider-changes", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules validate-provider-changes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/utils/validate-provider-changes .agents/skills/validate-provider-changes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validate-provider-changes" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changes into .agents/skills/validate-provider-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-provider-changes", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules validate-provider-changes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/utils/validate-provider-changes .cursor/skills/validate-provider-changes && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "validate-provider-changes" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changes into .cursor/skills/validate-provider-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-provider-changes", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/GoogleCloudPlatform/magic-modules.git --path .agents/skills/utils/validate-provider-changes--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules validate-provider-changes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/utils/validate-provider-changes .gemini/skills/validate-provider-changes && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "validate-provider-changes" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changes into .gemini/skills/validate-provider-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-provider-changes", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install GoogleCloudPlatform/magic-modules validate-provider-changesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/utils/validate-provider-changes .github/skills/validate-provider-changes && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "validate-provider-changes" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changes into .github/skills/validate-provider-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-provider-changes", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules validate-provider-changes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/GoogleCloudPlatform/magic-modules.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/utils/validate-provider-changes .opencode/skills/validate-provider-changes && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "validate-provider-changes" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/validate-provider-changes into .opencode/skills/validate-provider-changes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validate-provider-changes", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
validate-provider-changes- GitHub stars
- 974
- Token cost
- ~528 tokens
- SKILL.md length
- 203 words
- Files
- 2 (incl. scripts)
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation.
- Works in 3 steps: Run the Provider Changes Validator → Analyze the Output → Verification & Handoff
- The user wants to check for breaking changes
- SKILL.md covers Prerequisites and Execution Steps
- Runs Shell scripts from its folder
What it does
Validate Provider Changes is an agent skill from GoogleCloudPlatform/magic-modules. Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation. Use this skill when the user wants to check for breaking changes, missing tests, or missing documentation, or other problems in the downstream providers.
Its SKILL.md is about 530 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/validate_provider_changes.sh`).
The repository describes itself as: Add Google Cloud Platform support to Terraform.
When your agent uses it
- The user wants to check for breaking changes
- Missing documentation
- Other problems in the downstream providers
Example prompts
- “/validate-provider-changes”
Requirements
- A Bash shell
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Run the Provider Changes Validator
- Analyze the Output
- Verification & Handoff
What it can do on your machine
Read from SKILL.md and the folder at commit e5db069. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Validate Provider Changes loads about 528 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 203 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 203 words (~528 tokens).
“Run the script to compare your current local changes (committed or uncommitted) against the base branch (defaults to the merge base with origin/main or main):”
- name
- validate-provider-changes
Files
SKILL.md and 1 other file (scripts) in .agents/skills/utils/validate-provider-changes of GoogleCloudPlatform/magic-modules.
- SKILL.md
- scripts/validate_provider_changes.sh
Open the folder on GitHubat commit e5db069
Compare with similar skills
Validate Provider Changes next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Validate Provider Changes this skillGoogleCloudPlatform/magic-modules | 974 | — | ~528 | Automated safety check: Pass | Custom licence | |
| Add Model Provideropenclaw/openclaw | 392k | — | ~1.1k | Automated safety check: Pass | MIT | |
| OmniRoute Provider Managementdiegosouzapw/OmniRoute | 74k | — | ~2.4k | Automated safety check: Pass | MIT | |
| OmniRoute Providers CLIdiegosouzapw/OmniRoute | 74k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| LobeHub Model Provider Integrationlobehub/lobehub | 83k | — | ~2.8k | Automated safety check: Pass | Custom licence | |
| Cosmos Providerdotnet/efcore | 15k | — | ~242 | Automated safety check: Pass | MIT |
Similar skills
OmniRoute Provider Management
diegosouzapw/OmniRoute
Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.
OmniRoute Providers CLI
diegosouzapw/OmniRoute
Command reference for managing provider connections in the omniroute gateway: browse the catalog, test and validate connections, rotate API keys and read per-provider metrics.
LobeHub Model Provider Integration
lobehub/lobehub
Adds an AI model provider to LobeHub end to end: runtime integration, model cards, configuration, branding and documentation, or documentation-only updates.
- Official
Cosmos Provider
dotnet/efcore
Implementation details for the EF Core Azure Cosmos DB provider.
Provider
evanca/flutter-ai-rules
A skill your agent uses when setting up providers, consuming state, optimizing rebuilds, using ProxyProvider, or migrating from deprecated providers (Provider package).
More from GoogleCloudPlatform/magic-modules
All 30 skills in this repoRun Pre Gen Checks
GoogleCloudPlatform/magic-modules
Run fast static checks that don't require generating downstreams, including git submodule verification, gofmt formatting, YAML linting, template validation (version-guard and unused-tmpl), mmv1 core…
Add List Resource Workflow
GoogleCloudPlatform/magic-modules
Opt resource into MMv1 list-resource generation by setting generatelistresource: true and validate it locally with generated tests.
Fetch Nightly Results
GoogleCloudPlatform/magic-modules
Skill to fetch latest nightly test results and metadata for Beta or GA providers from GCS test-metadata.
Automate Test Triage
GoogleCloudPlatform/magic-modules
Skill to automatically triage failing tests by reading test-metadata status files, matching GitHub issues, and generating a multi-section failure report.
Dev Overrides
GoogleCloudPlatform/magic-modules
Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.
Generate Provider
GoogleCloudPlatform/magic-modules
Executes code generation from Magic Modules into downstream Terraform providers and optionally compiles the binary.
Questions about Validate Provider Changes
What does Validate Provider Changes do?
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation. Validate Provider Changes is an agent skill from GoogleCloudPlatform/magic-modules. Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation.
When should I use Validate Provider Changes?
Validate Provider Changes fits situations like: the user wants to check for breaking changes; missing documentation; other problems in the downstream providers.
How do I install Validate Provider Changes in Claude Code?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a claude-code`. Or copy the skill folder (.agents/skills/utils/validate-provider-changes in GoogleCloudPlatform/magic-modules) into .claude/skills/validate-provider-changes in your project. Claude Code loads it when a task matches its description.
How do I install Validate Provider Changes in Codex?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a codex`. Or copy the skill folder (.agents/skills/utils/validate-provider-changes in GoogleCloudPlatform/magic-modules) into .agents/skills/validate-provider-changes in your project. Codex loads it when a task matches its description.
Can I use Validate Provider Changes in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GoogleCloudPlatform/magic-modules --skill validate-provider-changes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validate-provider-changes, .gemini/skills/validate-provider-changes, .github/skills/validate-provider-changes and .opencode/skills/validate-provider-changes in your project.
What does Validate Provider Changes need to run?
Going by SKILL.md and its folder, Validate Provider Changes needs a shell for the scripts in its folder. Our summary lists: A Bash shell.
Does Validate Provider Changes access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Validate Provider Changes safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Validate Provider Changes use?
Validate Provider Changes has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Validate Provider Changes use?
About 528 tokens (SKILL.md is roughly 2.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Validate Provider Changes?
Skills that share tags, products or a category with Validate Provider Changes: Add Model Provider (openclaw/openclaw, 392k stars), OmniRoute Provider Management (diegosouzapw/OmniRoute, 74k stars), OmniRoute Providers CLI (diegosouzapw/OmniRoute, 74k stars) and LobeHub Model Provider Integration (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Validate Provider Changes?
GoogleCloudPlatform (a GitHub organization) maintains it in GoogleCloudPlatform/magic-modules, which has 974 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on October 7, 2026.
Source: GoogleCloudPlatform/magic-modules on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.