API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents.
Install Verify API Schema
$ npx skills add GoogleCloudPlatform/magic-modules --skill verify-api-schema -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules verify-api-schema --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/verify-api-schema .claude/skills/verify-api-schema && 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 "verify-api-schema" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/verify-api-schema into .claude/skills/verify-api-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-api-schema", 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/verify-api-schemaType 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 verify-api-schema -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules verify-api-schema --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/verify-api-schema .agents/skills/verify-api-schema && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "verify-api-schema" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/verify-api-schema into .agents/skills/verify-api-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-api-schema", 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 verify-api-schema -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules verify-api-schema --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/verify-api-schema .cursor/skills/verify-api-schema && 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 "verify-api-schema" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/verify-api-schema into .cursor/skills/verify-api-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-api-schema", 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/verify-api-schema--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 verify-api-schema -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install GoogleCloudPlatform/magic-modules verify-api-schema --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/verify-api-schema .gemini/skills/verify-api-schema && 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 "verify-api-schema" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/verify-api-schema into .gemini/skills/verify-api-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-api-schema", 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 verify-api-schemaInstalls 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 verify-api-schema -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/verify-api-schema .github/skills/verify-api-schema && 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 "verify-api-schema" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/verify-api-schema into .github/skills/verify-api-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-api-schema", 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 verify-api-schema -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 verify-api-schema --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/verify-api-schema .opencode/skills/verify-api-schema && 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 "verify-api-schema" agent skill from https://github.com/GoogleCloudPlatform/magic-modules/tree/main/.agents/skills/utils/verify-api-schema into .opencode/skills/verify-api-schema/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-api-schema", 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
verify-api-schema- GitHub stars
- 974
- Token cost
- ~421 tokens
- SKILL.md length
- 180 words
- Files
- 1
- Skills in repo
- 30
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents.
- Works in 3 steps: Verification → The Core Commands → Verification & Handoff
- Tasks that involve OpenAPI specifications
- SKILL.md covers Prerequisites and Execution Steps
- Calls jq and curl; reaches googleapis.com
What it does
Verify API Schema is an agent skill from GoogleCloudPlatform/magic-modules. Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents.
Its SKILL.md is about 420 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering OpenAPI specifications and REST APIs. It works with Google Cloud. The repository describes itself as: Add Google Cloud Platform support to Terraform.
When your agent uses it
- Tasks that involve OpenAPI specifications
- Tasks that involve REST APIs
Example prompts
- “/verify-api-schema”
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Verification
- The Core Commands
- 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
Shell commands in SKILL.md call:
jqcurl
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
googleapis.com
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
Verify API Schema loads about 421 tokens when it runs. Until then it costs about 31 tokens; SKILL.md has 180 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 180 words (~421 tokens).
“Provide the exact bash commands the agent should run to verify the prerequisites.”
- name
- verify-api-schema
Files
Just SKILL.md in .agents/skills/utils/verify-api-schema of GoogleCloudPlatform/magic-modules.
Open the folder on GitHubat commit e5db069
Compare with similar skills
Verify API Schema 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 |
|---|---|---|---|---|---|---|
| Verify API Schema this skillGoogleCloudPlatform/magic-modules | 974 | — | ~421 | Automated safety check: Pass | Custom licence | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 | |
| Use Yaakmountain-loop/yaak | 19k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Old Coder API DesignAmazingAng/old-coder | 749 | 1 repos | ~3.4k | Automated safety check: Pass | MIT | |
| API CallerNVIDIA/SkillEvaluator | 548 | 1 repos | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
Use Yaak
mountain-loop/yaak
A skill your agent uses when the user mentions Yaak, a Yaak workspace, or the yaak command, or asks to call, hit, or smoke test HTTP/REST endpoints, save or organize API requests for reuse or manual…
Old Coder API Design
AmazingAng/old-coder
Reviews or designs an HTTP/JSON API's endpoints, auth, pagination, versioning and deprecations, guarding against inventing a bespoke interface or silently breaking consumers.
- Official
API Caller
NVIDIA/SkillEvaluator
Call any REST API dynamically. An agent skill from NVIDIA/SkillEvaluator.
API Generating
huangjia2019/claude-code-engineering
Generate API endpoint code and documentation from specifications.
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.
Related
Works with
Categories
Questions about Verify API Schema
What does Verify API Schema do?
Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents. Verify API Schema is an agent skill from GoogleCloudPlatform/magic-modules. Verify if an MMv1 YAML property matches the live GCP REST API JSON payload using the Discovery Documents.
When should I use Verify API Schema?
Verify API Schema fits situations like: tasks that involve OpenAPI specifications; tasks that involve REST APIs.
How do I install Verify API Schema in Claude Code?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill verify-api-schema -a claude-code`. Or copy the skill folder (.agents/skills/utils/verify-api-schema in GoogleCloudPlatform/magic-modules) into .claude/skills/verify-api-schema in your project. Claude Code loads it when a task matches its description.
How do I install Verify API Schema in Codex?
Run `npx skills add GoogleCloudPlatform/magic-modules --skill verify-api-schema -a codex`. Or copy the skill folder (.agents/skills/utils/verify-api-schema in GoogleCloudPlatform/magic-modules) into .agents/skills/verify-api-schema in your project. Codex loads it when a task matches its description.
Can I use Verify API Schema 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 verify-api-schema -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-api-schema, .gemini/skills/verify-api-schema, .github/skills/verify-api-schema and .opencode/skills/verify-api-schema in your project.
What does Verify API Schema need to run?
Going by SKILL.md and its folder, Verify API Schema needs the command-line tools its instructions call (jq and curl).
Does Verify API Schema access the network?
SKILL.md names 1 domain. In commands or code: googleapis.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Verify API Schema 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 Verify API Schema use?
Verify API Schema 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 Verify API Schema use?
About 421 tokens (SKILL.md is roughly 1.7k 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 Verify API Schema?
Skills that share tags, products or a category with Verify API Schema: API Designer (Jeffallan/claude-skills, 12k stars), OpenAPI to MCP Server (mcp-use/mcp-use, 11k stars), Use Yaak (mountain-loop/yaak, 19k stars) and Old Coder API Design (AmazingAng/old-coder, 749 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verify API Schema?
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.