Install the "hz-api-upgrade" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-api-upgrade into .claude/skills/hz-api-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-api-upgrade", 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.
Type 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.
skills CLI
$ npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "hz-api-upgrade" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-api-upgrade into .agents/skills/hz-api-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-api-upgrade", 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.
skills CLI
$ npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "hz-api-upgrade" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-api-upgrade into .cursor/skills/hz-api-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-api-upgrade", 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.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "hz-api-upgrade" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-api-upgrade into .gemini/skills/hz-api-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-api-upgrade", 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.
Installs 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).
skills CLI
$ npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "hz-api-upgrade" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-api-upgrade into .github/skills/hz-api-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-api-upgrade", 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.
skills CLI
$ npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "hz-api-upgrade" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-api-upgrade into .opencode/skills/hz-api-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-api-upgrade", 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
hz-api-upgrade
GitHub stars
215
Token cost
~1.8k tokens
SKILL.md length
719 words
Files
4 (incl. references)
Skills in repo
34
Repo updated
First seen
Licence
Apache-2.0
At a glance
Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog.
Works in 6 steps: Identify Current SDK Version → Check the API Changelog → Update SDK Dependencies → …
Updating SDK versions
SKILL.md covers When to Use, General Upgrade Workflow, Platform-Specific Upgrade Paths and Common Upgrade Issues, plus 3 more sections
Calls npm and npx
What it does
Hz API Upgrade is an agent skill from meta-quest/agentic-tools. Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog. Use when updating SDK versions or fixing deprecated API warnings. Build paths: all Meta VR app stacks; use hz-quest-verify-first if the build path is unclear.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/api-changelog.md`, `references/deprecation-guide.md` and `references/sdk-migration.md`).
It sits in Development, covering Changelog and release notes and Code migrations. It works with Android, npm and Gradle. The repository describes itself as: Agent Skills for Meta Quest/Horizon OS VR Development. The licence is Apache-2.0.
When your agent uses it
Updating SDK versions
Fixing deprecated API warnings
Example prompts
“Use the hz-api-upgrade skill to upgrade Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog”
Read from SKILL.md and the folder at commit 3a8553d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(metavr:*)
Bash(hzdb:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
npm
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use npm and npx, 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
Hz API Upgrade loads about 1.8k tokens when it runs, and up to ~7k if it reads all its reference files. Until then it costs about 72 tokens; SKILL.md has 719 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~72
When it runs· the whole SKILL.md, loaded when a task matches
~1.8k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~7k
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.
Download SKILL.mdSave it as .claude/skills/hz-api-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
hz-api-upgrade
description
Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog. Use when updating SDK versions or fixing deprecated API warnings. Build paths: all Meta VR app stacks; use hz-quest-verify-first if the build path is unclear.
allowed-tools
Bash(metavr:*), Bash(hzdb:*)
license
Apache-2.0
Horizon API Upgrade Skill
For Unity projects using the Meta XR SDK, use the dedicated
hz-unity-sdk-upgrade skill. Continue
here for Unreal, native Android or Spatial SDK, Web or IWSDK, and general
cross-platform upgrade planning.
When to Use
Use this skill when:
Upgrading an existing Meta VR application to a newer Horizon OS SDK version
Fixing deprecated API warnings or compilation errors after an SDK update
Migrating between major API versions (e.g., VrApi to OpenXR)
Understanding what changed between SDK releases
Planning an upgrade path for a project that has fallen behind on SDK versions
General Upgrade Workflow
Every SDK upgrade, regardless of platform, follows the same high-level process:
1. Identify Current SDK Version
Determine what version the project currently targets:
Unity: Check Packages/manifest.json or the Package Manager UI for com.meta.xr.* package versions
Unreal: Check the Meta XR Plugin version in .uplugin files or the Plugins browser
Spatial SDK / Android: Check build.gradle or build.gradle.kts for com.meta.spatial:* dependency versions
Web / IWSDK: Check package.json for @meta-spatial-sdk/* or @iwsdk/* package versions
2. Check the API Changelog
Before upgrading, review what changed between your current version and the target version. See references/api-changelog.md for a summary of recent changes.
Ensure the upgrade did not introduce performance regressions:
bash
metavr perf capture
Platform-Specific Upgrade Paths
Unity: Meta XR SDK
The Meta XR SDK for Unity is distributed as UPM packages. Upgrades are performed through the Unity Package Manager. Key packages include com.meta.xr.sdk.core, com.meta.xr.sdk.interaction, and com.meta.xr.sdk.platform.
Meta has progressively moved from Oculus.* and OVR* namespaces to Meta.* namespaces. After an upgrade, you may see compilation errors due to renamed classes or moved packages.
Removed APIs
APIs that were deprecated in previous versions may be fully removed in newer versions. If you skipped intermediate upgrades, you may encounter missing symbols. Always upgrade incrementally.
New Required Permissions
Newer Horizon OS versions may require additional permissions in your AndroidManifest.xml. Common additions include:
com.oculus.permission.HAND_TRACKING for hand tracking features
horizonos.permission.HEADSET_CAMERA for passthrough camera access
New <meta-data> entries for feature declarations
Manifest Changes
Newer SDK versions may require updated <meta-data> entries in AndroidManifest.xml, such as com.oculus.supportedDevices or updated minSdkVersion values.
Android SDK Targeting Requirement
New binary uploads for Meta Horizon apps must set targetSdkVersion within the supported range.
What's required
Set targetSdkVersion to API level 32-34 for immersive apps (or 32-36 for 2D panel apps)
minSdkVersion can remain at API level 32
Applies to all new binary uploads for both new and existing apps
Existing published apps continue to work without changes
How to update
Unity: Use the Project Setup Tool in the Meta XR SDK -- it can update API versions automatically. Or manually set in Player Settings -> Other Settings -> Target API Level.
Unreal: Use the Project Setup Tool in the Meta XR Plugin. Or set in Project Settings -> Android -> Target SDK Version.
Gradle (Spatial SDK / Native):
groovy
android {
defaultConfig {
targetSdkVersion 34 // 32-34 for immersive, 32-36 for 2D panel apps
minSdkVersion 32
}
}
Using metavr for Documentation Lookup
The metavr tool provides documentation search to help during upgrades. Invoke via metavr <args> (published as the npm package metavr; if metavr is not on PATH, run npx -y metavr <args>) — no global install needed.
bash
# Search for migration-related documentation
metavr docs search "migration guide"
metavr docs search "deprecated API"
metavr docs search "breaking changes v73"
# Search for specific API replacements
metavr docs search "OVRManager replacement"
metavr docs search "vrapi openxr migration"
Hz API Upgrade 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.
Use EVERY time the user asks to update / bump the version catalogs, "сделать обновление", "обновить каталог(и)", "обнови версии", "оформи изменения", "update the catalog", or to record dependency…
Summarize and execute civ-game version update workflow, including change classification, changelog entry authoring, release highlights, and verification steps.
A skill your agent uses when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.
Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog. Hz API Upgrade is an agent skill from meta-quest/agentic-tools. Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog.
When should I use Hz API Upgrade?
Hz API Upgrade fits situations like: updating SDK versions; fixing deprecated API warnings.
How do I install Hz API Upgrade in Claude Code?
Run `npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a claude-code`. Or copy the skill folder (skills/hz-api-upgrade in meta-quest/agentic-tools) into .claude/skills/hz-api-upgrade in your project. Claude Code loads it when a task matches its description.
How do I install Hz API Upgrade in Codex?
Run `npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a codex`. Or copy the skill folder (skills/hz-api-upgrade in meta-quest/agentic-tools) into .agents/skills/hz-api-upgrade in your project. Codex loads it when a task matches its description.
Can I use Hz API Upgrade 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 meta-quest/agentic-tools --skill hz-api-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hz-api-upgrade, .gemini/skills/hz-api-upgrade, .github/skills/hz-api-upgrade and .opencode/skills/hz-api-upgrade in your project.
What does Hz API Upgrade need to run?
Going by SKILL.md and its folder, Hz API Upgrade needs the command-line tools its instructions call (npm and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(metavr:*), Bash(hzdb:*).
Does Hz API Upgrade access the network?
SKILL.md contains no URLs. Its commands use npm and npx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Hz API Upgrade 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 Hz API Upgrade use?
Hz API Upgrade is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hz API Upgrade use?
About 1.8k tokens (SKILL.md is roughly 7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.2k tokens, read only when the agent opens those files.
What are the alternatives to Hz API Upgrade?
Skills that share tags, products or a category with Hz API Upgrade: Update Version Catalog (RedMadRobot/gradle-version-catalogs, 118 stars), Project Gradle Third Party Version Upgrade (afkT/DevUtils, 1.6k stars), Version Update Workflow (HkingAuditore/civ-game, 113 stars) and Docs Engineering (hiroshiyui/GuilelessBopomofo, 135 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hz API Upgrade?
meta-quest (a GitHub organization) maintains it in meta-quest/agentic-tools, which has 215 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on September 24, 2026.
Source: meta-quest/agentic-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.