Install the "hz-new-project-creation" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-new-project-creation into .claude/skills/hz-new-project-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-new-project-creation", 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-new-project-creation -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "hz-new-project-creation" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-new-project-creation into .agents/skills/hz-new-project-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-new-project-creation", 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-new-project-creation -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "hz-new-project-creation" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-new-project-creation into .cursor/skills/hz-new-project-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-new-project-creation", 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-new-project-creation -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "hz-new-project-creation" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-new-project-creation into .gemini/skills/hz-new-project-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-new-project-creation", 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-new-project-creation -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "hz-new-project-creation" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-new-project-creation into .github/skills/hz-new-project-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-new-project-creation", 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-new-project-creation -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-new-project-creation" agent skill from https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-new-project-creation into .opencode/skills/hz-new-project-creation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hz-new-project-creation", 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-new-project-creation
GitHub stars
215
Token cost
~2.3k tokens
SKILL.md length
1,140 words
Files
7 (incl. references)
Skills in repo
34
Repo updated
First seen
Licence
Apache-2.0
At a glance
Scaffolds new Meta VR and Horizon OS projects after the build path is selected — Standard Android, Meta Spatial SDK, Unity, Unreal, or WebXR.
Works in 4 steps: Create a Meta developer account -- Sign… → Set up your Meta VR device for… → Enable USB debugging -- Connect your… → …
Creating a new Meta VR app from scratch
SKILL.md covers When to Use This Skill, Prerequisites, Start with the selected build… and After Choosing a Platform, plus 3 more sections
Calls git and npx
What it does
Hz New Project Creation is an agent skill from 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. Use when creating a new Meta VR app from scratch. Build paths: all; use hz-quest-verify-first to choose the path.
Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files, including reference files (for example `references/android-project.md`, `references/spatial-sdk-project.md` and `references/unity-project-manual.md`).
It sits in Game Development, covering Game development and Project scaffolding. It works with Android. 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
Creating a new Meta VR app from scratch
Tasks that involve Game development
Tasks that involve Project scaffolding
Example prompts
“Use the hz-new-project-creation skill to scaffold new Meta VR and Horizon OS projects after the build path is selected — Standard Android, Meta…”
4 steps, taken from the first numbered list in SKILL.md.
1Create a Meta developer account -- Sign up at developer.meta.com and create an organization.
2Set up your Meta VR device for development -- Enable developer mode in the Meta Horizon app on your phone under your headset's settings.
3Enable USB debugging -- Connect your Meta VR device via USB-C, put on the headset, and accept the "Allow USB debugging" prompt.
4Install metavr -- Install the standalone metavr CLI binary on your PATH (see the metavr-cli skill), or invoke it on demand via npx with no…
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:*)
Bash(npx:*)
mcp__metavr__metavr_unity_setup
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
git
npx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
developer.meta.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
Hz New Project Creation loads about 2.3k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 70 tokens; SKILL.md has 1,140 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~70
When it runs· the whole SKILL.md, loaded when a task matches
~2.3k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~14k
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-new-project-creation/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
hz-new-project-creation
description
Scaffolds new Meta VR and Horizon OS projects after the build path is selected — Standard Android, Meta Spatial SDK, Unity, Unreal, or WebXR. Use when creating a new Meta VR app from scratch. Build paths: all; use hz-quest-verify-first to choose the path.
Scaffold and configure new Meta VR projects from scratch after the build path
has been selected. This skill provides step-by-step setup instructions with
recommended settings optimized for Meta VR hardware.
When to Use This Skill
Use this skill when you need to:
Create a brand-new project targeting Meta Quest (Quest 2, Quest 3, Quest 3S, Quest Pro) and Meta VR Glasses after selecting its build path
Configure a project with the correct render settings, SDK versions, and build targets for Meta VR
Set up a project template with recommended architecture and folder structure
Follow the setup workflow for a previously selected Standard Android, Meta Spatial SDK, Unity, Unreal Engine, or WebXR project
Prerequisites
Before creating any Meta VR project, complete these steps regardless of platform:
Create a Meta developer account -- Sign up at developer.meta.com and create an organization.
Set up your Meta VR device for development -- Enable developer mode in the Meta Horizon app on your phone under your headset's settings.
Enable USB debugging -- Connect your Meta VR device via USB-C, put on the headset, and accept the "Allow USB debugging" prompt.
Install metavr -- Install the standalone metavr CLI binary on your PATH (see the metavr-cli skill), or invoke it on demand via npx with no install:bash
metavr --version
Examples below use the bare metavr command; if you use the npm distribution, prefix with npx -y.
Verify your device connection before starting any project:
bash
metavr device list
Start with the selected build path
Use hz-quest-verify-first to identify the build path before scaffolding. Do not
choose an SDK from a feature checklist: several paths can expose similar Meta VR
features, but they have different project structures and runtime models.
Build path
Choose it when
Setup reference or skill
Standard Android
The app is primarily 2D UI in one resizable Horizon OS panel, implemented with Jetpack Compose, Android Views, React Native, or Expo. This is the default for a new 2D app; Spatial SDK is not required.
Once the user has selected a platform, refer to the corresponding reference guide for detailed, step-by-step project setup:
Unity (Meta VR) -- MUST use the metavr_unity_setup MCP tool to create the project. Do NOT run Unity CLI directly. Do NOT walk the user through manual Package Manager / XR Plug-in Management steps. See Unity Project Setup. Manual fallback at unity-project-manual.md only when the MCP tool is unavailable. (Note: this guidance applies to Meta VR Unity projects only — for non-VR Unity projects use Unity Hub as normal.)
These are common pitfalls when setting up new Meta VR projects.
Android API level mismatch -- For new immersive projects, start with minimum API 32 and target API 34. Check hz-store-submit for the minimum store-acceptance floor and hz-api-upgrade for the current target range; immersive and 2D panel apps differ. Setting the wrong API level is a common reason builds fail to install or upload. Unity defaults may not match these requirements — always verify in Player Settings > Other Settings and with metavr docs search "target API".
ARM64 only, no x86 -- Meta VR devices are ARM64 (aarch64). If your build pipeline targets x86 or includes x86 native libraries, the APK will install but crash immediately on launch. In Unity, ensure "Target Architectures" has only ARM64 checked. In Android Studio, verify your ABI filters.
Gradle version compatibility -- Meta's Android and Spatial SDK samples often pin compatible Gradle, Android Gradle Plugin, Kotlin, and KSP versions. Copy the complete version set from a current official template or sample; upgrading one independently can cause obscure build failures.
Unity version matters -- Not every Unity version is compatible with the latest Meta XR SDK. Check the Meta XR SDK release notes for the supported Unity version range. Using an unsupported Unity version causes cryptic C# compilation errors or missing XR subsystem errors at runtime.
Vulkan vs. OpenGL ES -- Quest 3 supports Vulkan and it is recommended for best performance. Quest 2 also supports Vulkan but some older Meta XR SDK features had Vulkan-only bugs. If you see rendering artifacts on Quest 2 with Vulkan, try OpenGL ES 3.0 as a fallback and file a bug.
Missing Android manifest permissions -- Meta VR-specific features (hand tracking, passthrough, scene understanding, eye tracking) require explicit manifest permissions. The app will silently fail to access these features without the correct permissions. They are not added automatically by the SDK.
Forgetting to set the package name before first build -- Changing the package name after the first install on a device can cause data loss or install failures. Set the correct com.company.appname package name before your first build and deploy.
Unreal Engine: OpenXR vs. OVRPlugin -- Unreal supports both the OpenXR backend and the legacy OVRPlugin backend for Quest. New projects should use OpenXR. Mixing plugins in the same project causes undefined behavior.
Common Post-Setup Tasks
After the project is created and configured on any platform, these tasks are typically needed:
Register the App on the Developer Dashboard
Create an application entry at developer.meta.com to obtain an App ID. This is required for platform features like entitlement checks, multiplayer, achievements, and store submission.
Set Up Version Control
Initialize a Git repository and configure .gitignore for the chosen platform:
bash
git init
# Use a platform-appropriate .gitignore (Unity, Unreal, Android, or Node.js)
First Build and Deploy
Build the project and install it on a connected Meta VR device:
bash
# After building, install the APK
metavr app install path/to/build.apk
# Launch the app
metavr app launch com.yourcompany.yourapp
# Monitor logs during first run
metavr adb logcat --follow --tag yourapp
Performance Baseline
On first successful run, verify the application meets baseline performance targets:
Frame rate: 72 Hz minimum (90 Hz or 120 Hz preferred on Quest 3)
Frame timing: Consistent frame times without spikes
Thermal: No thermal throttling warnings during normal use
References
Skill References
Unity Project Setup -- One-shot Unity project setup via the metavr_unity_setup MCP tool
Hz New Project Creation 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 New Project Creation compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Hz New Project Creation this skillmeta-quest/agentic-tools
Navigation skill for genre project scaffolds: pick platformer/RPG/FPS (or other genre) then load matching template scripts and route gameplay fill to godot-genre- skills.
Provides instructions to configure, integrate, and verify third-party mediation networks (AppLovin, Meta Audience Network, Unity Ads, etc.) in GDScript and C.
A skill your agent uses when a Godot game stutters, drops frames, hitches when entering new areas, overheats a phone, or must ship: profiling and Performance monitors, CPU or GPU bound, draw calls…
Expert blueprint for mobile platforms (Android/iOS) covering touch controls, virtual joysticks, responsive UI, safe areas (notches), battery optimization, and app store guidelines.
Scaffolds new Meta VR and Horizon OS projects after the build path is selected — Standard Android, Meta Spatial SDK, Unity, Unreal, or WebXR. Hz New Project Creation is an agent skill from 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.
When should I use Hz New Project Creation?
Hz New Project Creation fits situations like: creating a new Meta VR app from scratch; tasks that involve Game development; tasks that involve Project scaffolding.
How do I install Hz New Project Creation in Claude Code?
Run `npx skills add meta-quest/agentic-tools --skill hz-new-project-creation -a claude-code`. Or copy the skill folder (skills/hz-new-project-creation in meta-quest/agentic-tools) into .claude/skills/hz-new-project-creation in your project. Claude Code loads it when a task matches its description.
How do I install Hz New Project Creation in Codex?
Run `npx skills add meta-quest/agentic-tools --skill hz-new-project-creation -a codex`. Or copy the skill folder (skills/hz-new-project-creation in meta-quest/agentic-tools) into .agents/skills/hz-new-project-creation in your project. Codex loads it when a task matches its description.
Can I use Hz New Project Creation 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-new-project-creation -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-new-project-creation, .gemini/skills/hz-new-project-creation, .github/skills/hz-new-project-creation and .opencode/skills/hz-new-project-creation in your project.
What does Hz New Project Creation need to run?
Going by SKILL.md and its folder, Hz New Project Creation needs the command-line tools its instructions call (git and npx). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Bash(metavr:*), Bash(hzdb:*), Bash(npx:*), mcp__metavr__metavr_unity_setup.
Does Hz New Project Creation access the network?
SKILL.md names 1 domain. As links in the text: developer.meta.com. This is read from the text; nothing was executed.
Is Hz New Project Creation 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 New Project Creation use?
Hz New Project Creation 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 New Project Creation use?
About 2.3k tokens (SKILL.md is roughly 9.1k 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 12k tokens, read only when the agent opens those files.
What are the alternatives to Hz New Project Creation?
Skills that share tags, products or a category with Hz New Project Creation: Godot Project Templates (thedivergentai/GD-Agentic-Skills, 821 stars), Release Manager (poingstudios/godot-admob-plugin, 632 stars), Godot Admob Troubleshoot (poingstudios/godot-admob-plugin, 632 stars) and Godot Admob Mediation (poingstudios/godot-admob-plugin, 632 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hz New Project Creation?
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.
