Agent skill

Hz API Upgrade

by meta-quest in meta-quest/agentic-tools

Upgrades Meta VR apps to newer Horizon OS SDK versions — migration guides, deprecated API replacements, changelog.

Apache-2.0Auto-check passedDevelopment

Install Hz API Upgrade

skills CLI
$ npx skills add meta-quest/agentic-tools --skill hz-api-upgrade -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install meta-quest/agentic-tools hz-api-upgrade --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/meta-quest/agentic-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hz-api-upgrade .claude/skills/hz-api-upgrade && rm -rf skills-src

Use ~/.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/

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”
  • “/hz-api-upgrade”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Bash(metavr:*), Bash(hzdb:*)

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Identify Current SDK Version
  2. Check the API Changelog
  3. Update SDK Dependencies
  4. Fix Deprecated API Calls
  5. Test on Device
  6. Run Performance Check

What it can do on your machine

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.

SKILL.md

The full file from meta-quest/agentic-tools at commit 3a8553d, republished under its Apache-2.0 licence (© meta-quest). 719 words, ~1,757 tokens.

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.

Use the device hub to search documentation:

bash
metavr docs search "release notes v72"
metavr docs search "migration guide openxr"
3. Update SDK Dependencies

Update the version numbers in your project configuration:

  • Unity: Update via Package Manager or edit manifest.json directly
  • Unreal: Download and install the new plugin version
  • Gradle projects: Bump version strings in build.gradle
  • npm projects: Run npm update or edit package.json
4. Fix Deprecated API Calls

After updating, compile the project and address errors and warnings. See references/deprecation-guide.md for common replacements.

bash
# Search project for known deprecated APIs
grep -rn "vrapi_" --include="*.c" --include="*.cpp" --include="*.h" src/
grep -rn "OVRManager" --include="*.cs" Assets/
5. Test on Device

Deploy and verify functionality on a connected Meta VR device:

bash
metavr app install ./build/output.apk
metavr app launch com.yourcompany.yourapp
6. Run Performance Check

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.

See references/sdk-migration.md for the step-by-step Unity upgrade guide.

Unreal Engine: Meta XR Plugin

The Meta XR Plugin for Unreal is distributed as an engine plugin. Upgrades involve downloading the new plugin version and regenerating project files.

See references/sdk-migration.md for the step-by-step Unreal upgrade guide.

Android / Spatial SDK

The Meta Spatial SDK is distributed as Gradle dependencies. Upgrades involve bumping version numbers in your Gradle build files.

See references/sdk-migration.md for the step-by-step Spatial SDK upgrade guide.

Web / IWSDK

The Immersive Web SDK is distributed as npm packages. Upgrades involve updating package versions in package.json.

See references/sdk-migration.md for the step-by-step IWSDK upgrade guide.

Common Upgrade Issues

Show full SKILL.md (292 more words)Show less
Namespace Changes

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"

References

© meta-quest, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (references) in skills/hz-api-upgrade of meta-quest/agentic-tools.

  • SKILL.md
  • references/api-changelog.md
  • references/deprecation-guide.md
  • references/sdk-migration.md

Open the folder on GitHubat commit 3a8553d

Compare with similar skills

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.

Hz API Upgrade compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hz API Upgrade this skillmeta-quest/agentic-tools215—~1.8kAutomated safety check: PassApache-2.0
Update Version CatalogRedMadRobot/gradle-version-catalogs118—~9.5kAutomated safety check: PassMIT
Project Gradle Third Party Version UpgradeafkT/DevUtils1.6k—~1.2kAutomated safety check: PassApache-2.0
Version Update WorkflowHkingAuditore/civ-game113—~742Automated safety check: PassNone
Docs Engineeringhiroshiyui/GuilelessBopomofo135—~806Automated safety check: PassGPL-3.0
Release Engineeringhiroshiyui/GuilelessBopomofo135—~1.6kAutomated safety check: PassGPL-3.0

Similar skills

  • Update Version Catalog

    RedMadRobot/gradle-version-catalogs

    Use EVERY time the user asks to update / bump the version catalogs, "сделать обновление", "обновить каталог(и)", "обнови версии", "оформи изменения", "update the catalog", or to record dependency…

    118 GitHub stars~9.5k tokensUpdated 6 days ago
    DevelopmentAuto-check passed
  • 对 DevUtils 工程(DEPSROOT=file/gradle、DEPSMANIFEST=file/deps)中定义的第三方库 GAV 依赖做版本查证与升级;结合 Maven Central、Google Maven、Gradle Plugin Portal、 JitPack 与 GitHub Releases/README 交叉校验「最新可用版本」;必要时修正…

    1.6k GitHub stars~1.2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Version Update Workflow

    HkingAuditore/civ-game

    Summarize and execute civ-game version update workflow, including change classification, changelog entry authoring, release highlights, and verification steps.

    113 GitHub stars~742 tokensUpdated 16 days ago
    DevelopmentAuto-check passed
  • Docs Engineering

    hiroshiyui/GuilelessBopomofo

    Writing/updating project documentation (README, PRIVACY-POLICY, NOTICES, changelogs) and maintaining F-Droid metadata.

    135 GitHub stars~806 tokensUpdated 12 days ago
    DevelopmentAuto-check passed
  • Release Engineering

    hiroshiyui/GuilelessBopomofo

    Release engineering tasks including version bumping, building release APKs, creating git tags, writing changelogs, and preparing F-Droid releases.

    135 GitHub stars~1.6k tokensUpdated 12 days ago
    DevelopmentAuto-check passed
  • Play Billing Library Version Upgrade

    arindamxd/camerax-android

    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.

    132 GitHub starsUsed in 5 repos~1.4k tokens
    DevelopmentAuto-check passed

More from meta-quest/agentic-tools

All 34 skills in this repo
  • Hz Android 2D Porting

    meta-quest/agentic-tools

    Guides porting existing Android 2D apps to Meta VR and Horizon OS — input adaptation, panel layout, and design requirements.

    215 GitHub stars~2.1k tokensUpdated 14 days ago
    Auto-check passed
  • Hz Iwsdk Webxr

    meta-quest/agentic-tools

    Builds WebXR experiences for Meta VR and Horizon OS using the Immersive Web SDK (IWSDK) — ECS architecture, Three.js integration, spatial UI.

    215 GitHub stars~3k tokensUpdated 14 days ago
    Auto-check passed
  • Hz Metavrx Layout SDK

    meta-quest/agentic-tools

    Build multi-window Meta Horizon OS experiences with the MetaVrx Layout SDK in Jetpack Compose or React Native.

    215 GitHub stars~855 tokensUpdated 14 days ago
    Auto-check passed
  • Hz New Project Creation

    meta-quest/agentic-tools

    Scaffolds new Meta VR and Horizon OS projects after the build path is selected — Standard Android, Meta Spatial SDK, Unity, Unreal, or WebXR.

    215 GitHub stars~2.3k tokensUpdated 14 days ago
    Auto-check passed
  • Hz Perfetto Debug

    meta-quest/agentic-tools

    Analyzes Meta VR and Horizon OS VR performance using Perfetto traces — frame timing, CPU/GPU bottlenecks, render pass analysis.

    215 GitHub stars~2.8k tokensUpdated 14 days ago
    Auto-check passed
  • Hz React Native Expo

    meta-quest/agentic-tools

    Build and iterate on React Native apps for Meta VR / Horizon OS with Expo.

    215 GitHub stars~2.8k tokensUpdated 14 days ago
    Auto-check passed

Questions about Hz API Upgrade

What does Hz API Upgrade do?

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.