React Sync
vercel/next.js
Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.
Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
Custom licenceAuto-check passed
Install Check Sync Provider
$ npx skills add GoogleCloudPlatform/magic-modules --skill check-sync-provider -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules check-sync-provider --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/check-sync-provider .claude/skills/check-sync-provider && 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 "check-sync-provider" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/check-sync-provider into .claude/skills/check-sync-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sync-provider", 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/check-sync-providerType 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 check-sync-provider -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules check-sync-provider --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/check-sync-provider .agents/skills/check-sync-provider && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "check-sync-provider" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/check-sync-provider into .agents/skills/check-sync-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sync-provider", 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 check-sync-provider -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules check-sync-provider --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/check-sync-provider .cursor/skills/check-sync-provider && 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 "check-sync-provider" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/check-sync-provider into .cursor/skills/check-sync-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sync-provider", 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/check-sync-provider--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 check-sync-provider -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules check-sync-provider --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/check-sync-provider .gemini/skills/check-sync-provider && 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 "check-sync-provider" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/check-sync-provider into .gemini/skills/check-sync-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sync-provider", 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 check-sync-providerInstalls 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 check-sync-provider -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/check-sync-provider .github/skills/check-sync-provider && 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 "check-sync-provider" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/check-sync-provider into .github/skills/check-sync-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sync-provider", 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 check-sync-provider -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 check-sync-provider --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/check-sync-provider .opencode/skills/check-sync-provider && 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 "check-sync-provider" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/check-sync-provider into .opencode/skills/check-sync-provider/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-sync-provider", 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
check-sync-provider- GitHub stars
- 974
- Token cost
- ~273 tokens
- SKILL.md length
- 131 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
- Works in 3 steps: Identify Magic Modules Base Commit → Find the Matching Downstream Commit → Compare and Report
- Calls git
What it does
Check Sync Provider is an agent skill from GoogleCloudPlatform/magic-modules. Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
Its SKILL.md is about 270 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Add Google Cloud Platform support to Terraform.
Example prompts
- “Use the check-sync-provider skill to check if the downstream provider repository is aligned with the correct Magic Modules base commit”
- “/check-sync-provider”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Identify Magic Modules Base Commit
- Find the Matching Downstream Commit
- Compare and Report
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
Shell commands in SKILL.md call:
git
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.
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
Check Sync Provider loads about 273 tokens when it runs. Until then it costs about 30 tokens; SKILL.md has 131 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); files beside SKILL.md 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 131 words (~273 tokens).
“Use this skill to verify if the downstream repository is at the correct baseline commit before generating code or running tests.”
- name
- check-sync-provider
Files
Just SKILL.md in .agents/skills/utils/check-sync-provider of GoogleCloudPlatform/magic-modules.
Open the folder on GitHubat commit e5db069
Compare with similar skills
Check Sync Provider 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 |
|---|---|---|---|---|---|---|
| Check Sync Provider this skillGoogleCloudPlatform/magic-modules | 974 | — | ~273 | Automated safety check: Pass | Custom licence | |
| React Syncvercel/next.js | 143k | — | ~486 | Automated safety check: Pass | MIT | |
| Correctcursor/plugins | 10k | 3 repos | ~612 | Automated safety check: Pass | None | |
| 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 |
Similar skills
- Official
- Official
Correct
cursor/plugins
Find the mistakes agents keep repeating in this repo and make each one impossible.
Add Model Provider
openclaw/openclaw
Add and live-prove a model provider with non-interactive config one-liners, without exposing credentials.
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.
Ccs Align
thedotmack/claude-mem
Run the CCS Align seat's hourly breathing cycle — prove the local claude-mem worker is healthy, pull needle observations through search → timeline → getobservations, land them in a seat-owned middle…
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…
Validate Provider Changes
GoogleCloudPlatform/magic-modules
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation.
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.
Questions about Check Sync Provider
What does Check Sync Provider do?
Checks if the downstream provider repository is aligned with the correct Magic Modules base commit. Check Sync Provider is an agent skill from GoogleCloudPlatform/magic-modules. Checks if the downstream provider repository is aligned with the correct Magic Modules base commit.
How do I install Check Sync Provider in Claude Code?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill check-sync-provider -a claude-code`. Or copy the skill folder (.agents/skills/utils/check-sync-provider in GoogleCloudPlatform/magic-modules) into .claude/skills/check-sync-provider in your project. Claude Code loads it when a task matches its description.
How do I install Check Sync Provider in Codex?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill check-sync-provider -a codex`. Or copy the skill folder (.agents/skills/utils/check-sync-provider in GoogleCloudPlatform/magic-modules) into .agents/skills/check-sync-provider in your project. Codex loads it when a task matches its description.
Can I use Check Sync Provider 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 check-sync-provider -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-sync-provider, .gemini/skills/check-sync-provider, .github/skills/check-sync-provider and .opencode/skills/check-sync-provider in your project.
What does Check Sync Provider need to run?
Going by SKILL.md and its folder, Check Sync Provider needs the command-line tools its instructions call (git).
Does Check Sync Provider access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Check Sync Provider 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. Review the folder before installing.
What licence does Check Sync Provider use?
Check Sync Provider 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 Check Sync Provider use?
About 273 tokens (SKILL.md is roughly 1.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 Check Sync Provider?
Skills that share tags, products or a category with Check Sync Provider: React Sync (vercel/next.js, 143k stars), Correct (cursor/plugins, 10k stars), Add Model Provider (openclaw/openclaw, 392k stars) and OmniRoute Provider Management (diegosouzapw/OmniRoute, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Check Sync Provider?
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.