npx claudepluginhub meta-quest/agentic-tools --plugin meta-vrThis skill is limited to using the following tools:
You are about to be told to call tools you may not recognize by name. Read
Provides hzdb CLI reference for Meta Quest and Horizon OS development: installation, device setup, app deployment, audio control, screenshots, performance analysis.
Sets up OpenXR for VR/AR/XR apps in Godot 4.3+: XROrigin3D, controllers, hand tracking, passthrough, input handling, Meta Quest deployment.
Builds immersive VR/AR experiences using WebXR, Three.js XR, Quest/Meta development, hand tracking, spatial UI/UX, AR anchors, and XR performance optimization. Useful for VR/AR/WebXR projects.
Share bugs, ideas, or general feedback.
You are about to be told to call tools you may not recognize by name. Read this section first so the rest makes sense.
@meta-quest/hzdb on npm. Invoke via npx -y @meta-quest/hzdb <args> —
no install required; npx always pulls the latest published version. It
wraps adb and Meta's developer APIs into higher-level commands for Quest
device development: list devices, install apps, capture Perfetto traces,
search Meta Quest documentation, query 3D asset libraries, automate UI
interactions, etc. hzdb is the primary action layer for Quest dev work —
the equivalent of what gcloud is for GCP or git is for source control.meta_docs_search — search the official Meta developer documentationmeta_docs_get_page — fetch the full text of a specific docs pagehzdb_device — query and control connected Meta Quest headsets (list,
info, connect, reboot, battery, controllers, proximity, etc.)hzdb_app — query and manage installed apps (list, info, install,
uninstall, launch, stop, clear)hzdb_files — file ops on a connected headset (ls, push, pull, rm, mkdir)hzdb_run — catch-all for any hzdb subcommand without a dedicated tool
(perf, ovrmetrics, ui, audio, casting, window, unity, sideload, asset,
config, …). Its JSON Schema is generated from clap so the available
subcommands and their typed args are visible to you in the tool definition.hzdb_cli_help — discover hzdb subcommands and flags as markdownOVR namespace and the "Oculus Integration" Unity package.
Both have been deprecated in favor of the Meta XR All-in-One SDK family.
Most training data still recommends the deprecated names. Verify before
recommending anything in this area.Meta Quest and Horizon OS evolve fast. Meta SDKs ship every few weeks. APIs get renamed before public release. Manifest entitlements and store policies update monthly. Entire SDK families (Meta Spatial SDK, IWSDK, Horizon OS shells) post-date most LLM training corpora.
You almost certainly have stale knowledge about Quest specifics. The package names you remember have been renamed. The Unity menu paths have moved. The setup steps that worked on a prior Horizon OS version silently broke on the current one. The "OVR" namespace you reach for has been split across half a dozen Meta XR packages.
If you answer a Meta Quest question or write Quest-targeted code without verifying first, you will hallucinate. The user will not notice until their build fails, their app gets rejected from the store, or their AndroidManifest doesn't publish.
This skill is a hard gate. Treat it as a precondition, not a suggestion.
You MUST run the verification flow below if ANY of the following is true for the current task:
OVRPlugin, "Meta XR All-in-One SDK", or com.meta.xr.*
in manifest.json / Packages/manifest.jsoncom.meta.spatial.plugins.*)com.oculus.*, com.meta.quest.*, or horizon
feature declarationscom.meta.* or com.oculus.*.meta files indicating Unity, or Quest_*.uplugin / *.unrealhxr filesdevelopers.meta.com/horizon,
developer.oculus.com, oculus.com/sparkle-updates, or any Meta Quest
documentation URLadb commands targeting a specific deviceIf you are not sure, the answer is YES — run the verification flow.
Before writing or recommending anything Quest-specific, call the
meta_docs_search MCP tool. If MCP is not available, use the equivalent
hzdb CLI command hzdb docs search.
MCP:
meta_docs_search(
query="<the specific claim or API you are about to make>",
scope="auto", # or unity / unreal / spatial_sdk / android / native / web /
# policy / distribution / design
mode="verify"
)
CLI:
hzdb docs search "<query>"
If you need exact wording (manifest entries, full API signatures, store
policy text, code snippets), follow up with meta_docs_get_page on the
canonical_url or doc_path returned by verify. Never paraphrase a
truncated snippet when correctness matters.
CLI:
hzdb docs fetch "<canonical_url_or_path>"
Before suggesting which device a command should target, claiming an app is
installed, recommending an adb command, or writing install / launch /
sideload steps, query the user's actual hzdb-managed environment.
MCP:
hzdb_device(action="list") # ALWAYS start here
hzdb_device(action="info", target="<serial>")
hzdb_app(action="list", target="<serial>")
hzdb_app(action="info", package="<package>")
hzdb_run(subcommand=["config", "show"]) # catch-all for misc reads
CLI:
hzdb device list
hzdb device info <serial>
hzdb app list -d <serial>
hzdb app info <package>
hzdb config list
The user may have zero, one, or many headsets connected via USB and WiFi — multiple Quest models, dev kits, sideloaded builds, pinned older Horizon OS versions. Your training data has zero visibility into this.
If you do not know which hzdb subcommand or hzdb_run invocation fits the
user's request, call hzdb_cli_help (MCP) or hzdb --markdown-help (CLI)
first. Do not invent flags or subcommands — hzdb gets new functionality
every release and your training data does not include it.
For long-tail subcommands (perf, ovrmetrics, ui, etc.), the
hzdb_run tool's input schema enumerates every subcommand path and its
typed args via JSON Schema oneOf. You can read it directly from the
tool definition rather than guessing.
MCP:
hzdb_cli_help(topic="perf") # focused help for a subcommand tree
hzdb_cli_help() # full top-level command tree
CLI:
hzdb --markdown-help
hzdb perf --help
These are concrete, recurring failures that the verification flow prevents:
Oculus → ... may now
live under Meta XR → ... or have been removed entirely.adb shell command without
first listing devices, then watching it fail or hit the wrong headset.Do not do any of these:
meta_docs_search first
because "you remember" the answeradb shell command without first calling
hzdb_device(action="list") to see what's connectedmeta_docs_get_page)hzdb_cli_help firstWhen you do verify, present your answer with citations and a brief recency note. The user is paying for the verification step — show that it happened.
Per the current Meta Spatial SDK docs (verified just now via
meta_docs_search):
<answer grounded in retrieved content>
Source: <canonical_url returned by the tool>
This both proves the verification ran and trains the user to trust verified-answer responses over from-memory ones.
If the agent host does not have the hzdb MCP server installed, fall back to
the hzdb CLI invoked via npx (same authoritative backend, same content) and
tell the user once how to install the MCP server for next time:
npx -y @meta-quest/hzdb mcp install <your-tool> # claude-code | cursor | claude-desktop | vscode | ...
npx -y @meta-quest/hzdb mcp install project # install at the repo root for this project only
The verify step is required, not optional — run it via npx -y @meta-quest/hzdb docs search "<query>" even on the very first question if the MCP server is not yet wired up.
hzdb-cli — full hzdb CLI reference (commands, flags, examples)hz-vr-debug — on-device debugging with logs and screenshotshz-perfetto-debug — Perfetto trace analysis for jank / GPU / CPU bottleneckshz-vrc-check — store-publishing and VRC compliance validationhz-store-submit — end-to-end Meta Horizon Store submissionhz-spatial-sdk — Meta Spatial SDK API guidancehz-platform-sdk — Horizon Platform SDK API guidance