agentleFS
mirzaaghazadehmirzaaghazadeh/iwsdk-webxr-skills/skills/custom/horizon-store-listing-assets/SKILL.md

horizon-store-listing-assets

Skill1 starsChanged 32 days agoMITView on GitHub

Prepare and validate the Meta Horizon Store listing for a WebXR / IWSDK PWA or a 2D PWA: art specs (covers, Hero, Mini Landscape, Logo, Icon, Spatialized tile, screenshots, trailer, 360 preview), asset VRCs, metadata limits, specs (play area, input, comfort, internet), age group and IARC, privacy policy and Data Use Checkup, pricing, price A/B tests, Try Before You Buy limits, web IAP limits (WebXR PWAs only, no subscriptions), sales, keys, Early Access, pre-orders, Store analytics, and what Meta VR Glasses change. Includes an image checker. Use when the user asks for "store assets for my web app", "cover art size", "screenshots of my WebXR game", "trailer requirements", "store description", "age rating / IARC", "privacy policy for my Quest PWA", "can my PWA sell items", "set the price", "A/B test my price", "free trial", "run a sale", "generate keys", or "early access". Replaces the asset table in Meta's hz-store-submit, which has wrong dimensions and limits.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Meta VR Glasses (spring 2027) don't change the listing: no new asset type, metadata field or VRC as of 2026-10-17.

    line 40
  2. Distinctive:

    After the user sets the age group on the Build tab, it reads "Teens and adults (13+ or applicable age in user's region)".

    line 214

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Horizon Store listing for web apps: assets, metadata, rating, pricing

Made by Navid Mirzaaghazadeh · part of iwsdk-webxr-skills · MIT

A PWA's store listing uses the same Developer Dashboard forms, art specs and VRCs as a native app; the asset VRCs apply to both the Store and Store (2D) columns. What differs for web apps: how you capture screenshots, the internet requirement, and monetization (no app price, only add-ons through the Digital Goods API, WebXR PWAs only). Policy detail: references/policy-pricing.md; what Connect 2026 changed: this repo's docs/meta-reference/store-2026.md.

Correction to Meta's hz-store-submit: it lists a 1024 px icon, a 2560 × 1440 hero, a 3-screenshot minimum and 30/150/4000-character name/short/long. The live pages give the values below. If this skill is older than "Last verified", run metavr docs fetch https://developers.meta.com/vr/resources/asset-guidelines/.

Meta VR Glasses (spring 2027) don't change the listing: no new asset type, metadata field or VRC as of 2026-10-17. The Store shows hand-capable titles first to VR Glasses owners without controllers (Connect recap, 2026-09-24), and every Bubblewrap TWA declares controllers and hands in its manifest, so make hands-only play work before you list hands.

1. Art assets (Asset design guidelines, updated 2026-05-11)

AssetSize (W × H)RatioFormatRules
Cover Landscape2560 × 144016:924-bit PNGSame design family as the other covers and the Hero
Cover Square1440 × 14401:124-bit PNGSame design family
Cover Portrait1008 × 14407:1024-bit PNGSame design family
Hero Cover3000 × 90010:324-bit PNGBranding or title centred (Asset.4); title text must match the app title
Mini Landscape1080 × 3603:124-bit PNGIn the spec table; the page gives no usage notes (check the Dashboard form)
Logovariable, max 9000 × 1440-32-bit PNGTransparent background (Asset.1)
Icon512 × 5121:124-bit PNGSolid, no transparency
Spatialized tile180 × 180 background + 180 × 180 foreground1:1PNGForeground transparent, inside the safe area with 18 dp padding, no shadow (Meta adds one). Optional: without layers the existing asset is brought forward
Screenshots2560 × 144016:924-bit PNG5, no duplicates, real in-app content, no added text or logos (Asset.5)
Trailer1080p min, 2K max16:9MP4 / H.264 / AAC30 s to 2 min (Asset.7: ≤ 2 min); follow hardware safety guidelines (wrist straps, play area)
Trailer cover2560 × 144016:924-bit PNG
360 previewcubestrip 12288 × 2048 (6:1) or equirect 7680 × 3840 (2:1)PNG, JPEG (quality ≥ 80), KTX≤ 2.3 MB; Meta suggests rendering 2048 × 2048 faces or an 8192 × 4096 source
Immersive Image Layers (Object Left, Object Right, Logo)not on the guidelines page (unverified)Transparent backgrounds (Asset.9)

"All assets support 24 and 32-bit PNGs ... the 8-bit alpha layer is ignored unless it's for the Logo." Keep titles and focal points in the safe area (templates: https://metaque.st/storetemplates; no pixel values on the page). Branded assets carry the exact app title; only the icon is exempt. Each extra store language needs localized assets. Test cover art with the Dashboard's creative A/B test on the product page (ab-testing-instructions, 2024-12-16).

Uploading assets by browser automation (Claude in Chrome, observed 2026-10-25):

  • The Assets form has no <input type=file> until "choose file on your device" is clicked, and that click opens a native picker an agent can't use. Patch HTMLInputElement.prototype.click so the file input stays in the page (appended, hidden, labelled), then attach with file_upload.
  • The first attach to a fresh input sometimes didn't register; clicking the same link and attaching again worked. A cover then opens its Safe area preview: click Use image.
  • file_upload takes at most 10 MB per call. Five 2560 × 1440 screenshots (about 3 MB each) go in two calls, 3 and 2, and the list appends.
  • The list showed them in a different order from the upload (3, 1, 2, 4, 5), and a synthetic drag on the row handles didn't reorder them. Reorder by hand if the order matters.

Covers made from a screenshot plus the title with ImageMagick: after a -compose multiply vignette, set -compose over again before compositing the logo. The compose setting carries into the logo's -layers merge and darkens it. End with -alpha off -define png:color-type=2 for a 24-bit file.

Asset VRCs to self-review: Asset.2 (cover art: branding only, no taglines or banners), Asset.3 (Rec: no text in the top or bottom 20% of covers), Asset.5, Asset.6 (no other VR platforms' hardware or logos anywhere), Asset.8 (Rec: text ≥ 24 pt), Asset.10 (Rec: "Captured on Meta Quest Pro." on Pro-only footage), Functional.6 (only Meta Quest hardware).

Validate a folder: scripts/check-store-assets.sh <dir> checks sizes, alpha, screenshot count and duplicates, and the trailer's codec, size and length (sips or ImageMagick, ffprobe). Expected names: cover_landscape.png, cover_square.png, cover_portrait.png, hero.png, mini_landscape.png, logo.png, icon.png, tile_background.png, tile_foreground.png, screenshot_*.png, trailer.mp4, trailer_cover.png.

The Store icon is separate from the PWA's manifest icons (192/512 px any and maskable) that Bubblewrap turns into the launcher icon; see horizon-web-store-publish.

2. Capturing screenshots and trailer footage from a web app

  • Capture in the installed TWA on a headset, not a desktop tab or the IWER / Immersive Web Emulator view. Reviewers compare screenshots with the real app (hz-store-submit) and emulator chrome would break Asset.5.
  • metavr capture screenshot -o shots/s1.png --width 2560 --height 1440 (default output is 1024 × 1024; check the real size and crop or scale to 16:9 without adding text). MQDH can also capture screenshots and video (browser-mqdh).
  • Hide debug HUDs, FPS counters, IWSDK dev overlays and Stats panels. In 2D PWAs no URL bar should be visible: if it is, asset links are broken (fix that first).
  • Show only Meta Quest controllers or hands (Functional.6, Asset.6).

3. Metadata (Providing App Metadata, updated 2025-08-20)

FieldLimit / rule
Namemax 40 characters (Publishing.4). Independent of the manifest name and Bubblewrap's 12-character launcher name, but keep them consistent
Short descriptionmax 500 characters (Publishing.5)
Long descriptionmax 1500 characters (Publishing.6)
Search keywordsoptional, up to 5, relevant only (Publishing.7). The field picks from suggestions and rejected a keyword with a space ("hand tracking")
CategorizationCategory (Apps or Games) + a required primary genre + up to 2 more. Optional for Games (2026-10-25): Art style and Game theme (up to 3 each), Gameplay challenge, Gameplay mechanics. Game genres offered: Action, Adventure, Education, Hangout, Narrative, Party game, Puzzle, Rhythm, Role playing, Sandbox, Simulation, Sports. There is no Casual or Arcade genre: put those in keywords
SpecsGame Modes, Supported Controllers, Play Area, Supported Player Modes, Comfort Level, Internet Connection, Subscription, Purchase-blocked devices, Social Features, Supported Languages in App, Early Access. The Dashboard pre-fills Internet Connection from the APK. It came pre-filled as not required for a PWA (2026-10-24) and as required for a native APK (2026-10-25). A PWA that loads from the web should say Required. The options are in the Specs list below the table
DetailsDeveloper and Publisher (64 characters each; Developer defaults to the team name until "Use team name" is unticked), Website (Publishing.1, must resolve), Privacy Policy (Privacy.1-4), optional External Support (Publishing.2) and Terms of Service (Publishing.3)
Content ratingDeveloper contact email (shared with IARC) + IARC certificate

Dashboard layout (observed 2026-10-24): a submission has four tabs, Submission, Pricing, Build and App metadata. App metadata has Name, Categorization, Specs, Details, Assets and Content rating, each saved on its own. Metadata preview shows the product page in the Store, the phone app and the headset for an hour, visible only to you.

Specs: what each field offers (observed 2026-10-25 on a native Quest app; the form is the same for every app type):

FieldOptions and behaviour
Early AccessEnable or Disable. It can be added only in the first submission, and removed later
Player modesMulti-select: Asynchronous multiplayer, Co-op, Local multiplayer, Massively multiplayer, Multiplayer, PvE, PvP, Single player
Supported inputAuto-filled from the binary: "Touch controller and Hands" for handtracking required="false", which every Bubblewrap TWA declares
Play areaMovement or No Movement. The older Stationary/Roomscale wording is gone from this field
Supported physical modesSitting, Standing, Roomscale (multi-select)
Comfort levelComfortable, Comfort: Moderate, Comfort: Intense
Internet connectionAuto-filled, editable (see the Specs row above)
SubscriptionNot required, Required for some content, Required
Purchase-blocked devicesPreselected: Quest (the first one). Offers Quest 2, Quest Pro, Quest 3 family. Blocking a device that the production build targets shows a warning; change the build's Supported devices too (horizon-web-store-publish §7a)
Social featuresYes or No

Web-specific: a PWA loads from your server, so declare the internet requirement truthfully and handle offline (Functional.7, Rec). Declare only input modalities that work alone from launch (Tracking.2) and a play area that matches (Tracking.1); remember the TWA's manifest always declares controllers and hands (app-compatibility, 2026-10-13). Web deploys change the app without review; keep descriptions and media matching what is live (Content.2). Purchase-Blocked Devices hides the app from a device's Store (target-builds-by-device, 2026-09-04).

Copywriting: the first sentence says what the player does; every claim is visible in the build; no other platforms' names; Meta brands only per the Brand Guidelines (Publishing.8); no keyword stuffing, all-caps titles, or price text in the name or art. Comfort Level (App policies §5.1, 2026-03-10): Comfortable generally avoids camera movement, player motion and disorienting effects (typically a fixed camera); Moderate has more camera and player motion; Intense usually has first-person camera motion, acceleration or significant movement.

4. Age group and rating

  • IARC rating from the Content Rating step; free and instant. Apps released in South Korea also need a GRAC rating (App policies §5.2.1, 2026-03-10).
  • Age group self-certification is separate and mandatory: Teens and Adults (13+), Mixed Ages (10-12 plus 13+), Children (10-12); no users under 10. The same value goes in every ovr-platform-util --age-group upload.
  • Mixed Ages WebXR PWA: implement DigitalGoodsService.getUserAccountAgeCategory() and call it "every time your WebXR PWA launches" (ps-iap, 2026-10-14). Implement within 30 days of self-certification or risk removal; after 60 days without it, some Platform SDK features stop (age-groups, 2026-04-02). 2D PWAs have no Digital Goods service: Mixed Ages may not be workable for a 2D PWA (unverified; ask Meta support).
  • Children apps may not use the Get Age Category API or any Platform SDK feature.

In the Dashboard (observed 2026-10-24):

  • Age group is set on the submission's Build tab ("Before you can submit this app for review, you must self-certify its age group"). Its last step is a legal self-certification in the user's name; leave Confirm to the user. The build upload dialog also warns that it's "required before publishing a binary".
  • IARC: Content rating > country of origin and contact email > Add certificate opens the IARC questionnaire in a new tab, and the user accepts IARC's terms there. A free-to-try game with one durable unlock answers Digital Purchases Yes > "Purchases of digital goods" (no random items, no trading). That came back as ESRB Everyone, PEGI 3, with the "In-Game Purchases" notice. The tab ends on "IARC Certificate Created".
  • The IARC questions for a Game (hosted at web.iarcservices.com, 2026-10-25). The first page asks the app type; the second asks, each Yes or No:

    • violence, blood or gore;
    • fear;
    • sexuality, suggestiveness or dating;
    • gambling;
    • offensive language;
    • drugs, alcohol or tobacco;
    • crude humour;
    • digital purchases, cash rewards or NFTs;
    • users interacting or exchanging content;
    • sharing precise location;
    • Nazi symbols;
    • content eroding Korean national identity;
    • advocating terrorism;
    • "realistic descriptions of crimes … or techniques that can be used in criminal offenses".

    A Yes to the crime question adds two more: likely to be imitated by youths, and detailed techniques. The last page shows every rating and needs a box ticked: "I hereby agree to the IARC Terms of Use and I agree that I am the age of majority". That's the user's agreement.

  • Crime themes move the regional ratings a lot. A non-violent game in which characters offer bribes and the player can keep them (crime Yes, both follow-ups No) came back as:

    • ESRB Everyone, PEGI 3, USK Everyone, ClassInd All ages, Generic 3+;
    • ACB Mature (Mature Themes), GRAC 15+ (Crime), DGSC PG15 (Anti-society), Russia 16+ (descriptor "Violence").

    Expect this for any game in which the player can commit or depict an offence (bribery, fraud, smuggling), even with no violence.

  • After the user sets the age group on the Build tab, it reads "Teens and adults (13+ or applicable age in user's region)". Each app has its own age group, IARC certificate and sharing preferences, so check the app name at the top left before starting.
  • Sharing preferences: the Submission tab shows "Please confirm your app sharing preferences before submitting". Those are streaming and capture by players, under Meta's Sharing Terms, which the user accepts or declines.
  • "Does your app contain ads?" on the Build tab stayed greyed out for an immersive PWA, even after the age group was set (cause unknown). On a paid native app the same locked question has the tooltip "This app cannot contain ads based on our Advertising Policy" (2026-10-25). Hover over it to read the PWA's reason.

5. Privacy policy and Data Use Checkup

Host a privacy policy at a stable URL covering (Privacy.1-4): who you are and a privacy contact; what you collect (Meta user ID and age category if used, purchases, analytics, crash reporting, cookies and local storage, voice); how it is used and shared (each third-party SDK, retention); how users request deletion. 2D PWAs share cookies and site data with Quest Browser (pwa-2d-support): say so if it matters for your data.

Data Use Checkup is required for the WebXR PWA platform features: Digital Goods IAP and getLoggedInUserId() (User ID / User Profile grant) (ps-iap). DUC requests are approved automatically during development; submitting for review or raising release-channel limits ends that; recertify yearly or the app is removed. Test users can call these features before DUC approval, except getting the logged-in user. DUC compliance also gates the User Demographics dashboard.

Filling it in (Requirements > Data Use Checkup, observed 2026-10-24; the user signs it):

  1. Add each feature you use. For an IAP-only game that's just "In-app purchases and/or downloadable content"; the page recommends User ID and User Profile "if you wish to use the Platform SDK", which a PWA that only sells an unlock doesn't need. Each request asks for a use case, a description of how the feature adds value, optional screenshots, and an "If approved, I agree…" checkbox before Add to request becomes active. If the button stays disabled after pasting text, type a character.
  2. Submit requests, then Data handling: data processors or service providers with access to Meta user data (a static web host that only serves files: No); the responsible person or entity and its country; whether you gave users' data to public authorities in the past 12 months; which policies you have for such requests (Required review, Provisions for challenging, Data minimization, Documentation, None of the above, or "prohibited from answering", which Meta warns may restrict access); the organization's country.
  3. Review requests, then Submit: the privacy policy URL is reviewed with it, and a final "I certify compliance with all applicable Meta terms and policies…" box (the user's). While it is under review, no other checkup can be submitted.

These are statements in the developer's name. An agent can fill them in, but should leave the certification boxes to the user and not claim policies the developer doesn't have.

6. Pricing, experiments and monetization (summary; details in references)

  • App price: free or $0.99-$299.99 MSRP; add-ons $0.99-$99.99; local pricing per country. A PWA can only be free: the Pricing tab says "PWAs are always free on Meta Horizon Store, but you can still sell add-ons and in-app purchases", and Paid app shows an empty price list (observed 2026-10-24). Pricing tab for a PWA: Listing type Full release, Price type Free app. Listing type offers Coming soon, Pre-order or Full release, and can't be changed after submission (2026-10-25). For paid apps, Full release adds "Prices are locked on approval and cannot be changed for 30 days", with a default price per region that can be overridden per country.
  • Web IAP: Digital Goods API + Payment Request with https://quest.meta.com/billing, WebXR PWAs only, subscriptions not supported, available only when installed from the Store (ALPHA and BETA count). Manage products under Monetization > Add-ons. 2D PWAs have neither a price nor Store IAP: free, or ads within Ads.1-7.
  • Pay once, the WebXR way: a free download with a durable unlock add-on, for example the first levels free (setup and code: references/policy-pricing.md §8). The IARC questionnaire then needs Digital Purchases = Yes, and the descriptions should say "free to try" and what the purchase unlocks (Content.2).
  • Price A/B test (US only; page 2025-10-01): Growth > Price A/B Testing; starts ≥ 3 days after setup, runs up to 90 days, can't be edited after submission, and can cost sale eligibility if it ends within 30 days of a sale. Connect 2026 listed "A/B Pricing" as new; no page describes changes yet.
  • Try Before You Buy (2026-06-29): not available for 2D apps. For an immersive PWA it is undocumented (unverified): time-based trials need no code; achievement-based trials need a "simple" achievement, which a web app can only unlock server-to-server (web ps-achievements, 2026-10-14).
  • Sales (Growth > Manage Promotions; bundles can now join store-wide sales), promo codes (Growth > Promo Codes, not for free apps), keys (up to 250 per request, 2,000 per 6 months), Early Access (new apps only; turning it off is irreversible), Coming Soon (up to 360 days) and pre-orders (up to 90 days), both only during the initial submission. Meta Credits no longer work for Store purchases (since 2026-06-09).

7. After launch: analytics

Benchmarks (> 100 lifetime active users), User Demographics (≥ 100 and DUC compliance) and alerts (threshold alerts: crash rate > 5%, Quest 3 FPS < 72, 1-star ratings, startup > 19 s) live under Analytics in the Dashboard. Performance analytics are not available for web apps, and the alerts page says alerts "are not enabled on MQDH or web" (ambiguous for PWAs; check the Dashboard). The read-only Meta AI Developer Assistant (icon after Help) answers metrics and reviewer-feedback questions; suggest it to the user. Details: references/policy-pricing.md §9.

Sources

Pages moved from developers.meta.com/horizon/ to /vr/ (old links redirect).

Last verified: 2026-10-25 (Specs, Pricing, IARC and the Assets upload in the Dashboard); 2026-10-24 (the rest)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.