hz-quest-verify-first

Verify Meta Quest VR code against authoritative Meta sources with metavr CLI/MCP.

176|17|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/meta-quest/agentic-tools --skill hz-quest-verify-first
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hz-quest-verify-first
Source: https://github.com/meta-quest/agentic-tools/tree/main/skills/hz-quest-verify-first
Command: npx skills add https://github.com/meta-quest/agentic-tools --skill hz-quest-verify-first

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires metavr, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that all questions and code related to Meta Quest VR headsets and apps are verified against authoritative Meta sources, preventing stale knowledge and deprecated APIs from being used.

Core Features & Use Cases

  • Pre-flight Verification: Checks for deprecated APIs, broken Android manifests, and store-rejected builds.
  • Automated Source Validation: Uses metavr CLI/MCP to verify against Meta's official documentation and device information.
  • Real-time Validation: Ensures that Unity SDK references and AndroidManifest files are up-to-date and compliant.
  • Use Case: Before writing or recommending any Quest-specific code or answer, this Skill automatically runs checks to ensure accuracy and compliance.

Quick Start

Verify your Quest development environment by running the hz-quest-verify-first skill.

Frequently Asked Questions about hz-quest-verify-first

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify Meta Quest VR app integrity and check for deprecated APIs?

Verify Meta Quest VR app integrity by running automated pre-flight checks against authoritative Meta sources. This process detects deprecated APIs, validates AndroidManifest files, and prevents store-rejected builds before deployment.

Why does my Unity SDK integration fail Meta Quest headset validation?

Unity SDK integration fails Quest validation when using outdated references or broken AndroidManifest files. Automated source validation checks your Unity SDK integration against Meta's official documentation to ensure real-time compliance and prevent stale knowledge.

Do I need the metavr CLI to validate my AndroidManifest for Quest development?

Yes, you need the metavr CLI or MCP for AndroidManifest validation and Quest development checks. This dependency provides the authoritative Meta source verification required to confirm code integrity and catch deprecated APIs.

What's the best way to prevent store-rejected builds for Meta Quest VR apps?

Prevent store-rejected builds by automating pre-flight checks that validate your Quest VR app against authoritative Meta sources. This verifies AndroidManifest compliance and detects deprecated APIs before submission.

Can I check for outdated knowledge and deprecated APIs in Meta Quest VR development automatically?

Yes, you can check for outdated knowledge and deprecated APIs automatically. The Skill runs real-time validation against Meta's official documentation and device information, ensuring all Quest-specific code and answers are accurate and compliant.

When do I need to run AndroidManifest validation for Meta Quest VR development?

Run AndroidManifest validation before writing or recommending any Quest-specific code. Apply these automated pre-flight checks during VR headset and app development to verify Unity SDK references and ensure AndroidManifest files are up-to-date and compliant.