Agent skill

Vitexec

by pmndrs in pmndrs/viverse

A skill your agent uses when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured…

Custom licenceAuto-check passedGame Development

Install Vitexec

skills CLI
$ npx skills add pmndrs/viverse --skill vitexec -a claude-code

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

GitHub CLI
$ gh skill install pmndrs/viverse vitexec --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/pmndrs/viverse.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/vitexec .claude/skills/vitexec && 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
vitexec
GitHub stars
132
Token cost
~2.5k tokens
SKILL.md length
1,265 words
Files
5 (incl. references)
Skills in repo
2
Repo updated
First seen
Licence
Custom licence

At a glance

A skill your agent uses when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured…

  • Works in 4 steps: Identify the page path if it is not /. → Write the smallest snippet that performs… → Run vitexec '', adding --path, --gpu,… → …
  • An AI agent needs to inspect
  • SKILL.md covers References, Workflow and Guidance
  • Calls npm and pnpm

What it does

Vitexec is an agent skill from pmndrs/viverse. Use this skill when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured artifacts. Use for client state after interactions, imported app modules, DOM state, human-like input, canvas/WebGL/Three.js state, screenshots, videos, CPU/network/performance/heap analysis, WebXR/Three.js XR with IWER, and runtime-only behavior without editing app files.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/inputs.md` and `references/performance.md`).

It sits in Game Development, covering 3D graphics and WebGL. It works with Three.js, Vite and npm. The repository describes itself as: ⟁ Toolkit for building Three.js and React Three Fiber Apps for VIVERSE and beyond.

When your agent uses it

  • An AI agent needs to inspect
  • Profile a live Vite app by running temporary snippets inside the browser page and reading browser logs
  • Captured artifacts
  • Client state after interactions

Example prompts

  • “/vitexec”

Requirements

  • Node.js

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Identify the page path if it is not /.
  2. Write the smallest snippet that performs the user-like action or reads the browser-only state.
  3. Run vitexec '', adding --path, --gpu, --screenshot, --record, --cpu-profile, --network-trace, --performance-trace, --heap-snapshot…
  4. Treat stdout as browser logs. It starts with logs:.

What it can do on your machine

Read from SKILL.md and the folder at commit b88c0e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm
    • pnpm

    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 pnpm, 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

Vitexec loads about 2.5k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 116 tokens; SKILL.md has 1,265 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~116
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~3.8k

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,265 words (~2,496 tokens).

“Use vitexec when the truth lives in the running browser: client state, imported app modules, DOM, canvas/WebGL, screenshots, recordings, or browser-only errors.”

— opening of SKILL.md by pmndrs, Custom licence
name
vitexec

Read the full SKILL.md on GitHub

Files

SKILL.md and 4 other files (references) in .agents/skills/vitexec of pmndrs/viverse.

  • SKILL.md
  • agents/openai.yaml
  • references/inputs.md
  • references/performance.md
  • references/webxr.md

Open the folder on GitHubat commit b88c0e7

Compare with similar skills

Vitexec 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.

Vitexec compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Vitexec this skillpmndrs/viverse132—~2.5kAutomated safety check: PassCustom licence
Threejs Gameplay Systemsvalkor-ai/loom1.2k1 repos~1.4kAutomated safety check: PassApache-2.0
New ExperimentTresjs/tres3.8k—~782Automated safety check: PassMIT
Threejs Gameplay Systemscorosolto/client257—~1.5kAutomated safety check: PassAGPL-3.0
Deploycyanfish-x/tellux207—~1.1kAutomated safety check: NotesMIT
Hz Iwsdk Webxrmeta-quest/agentic-tools213—~3kAutomated safety check: PassApache-2.0

Similar skills

  • Build and iterate playable Three.js game systems: starter scaffold, architecture, design briefs, core loops, level and encounter design, entities, input, camera, collision and physics, scoring…

    1.2k GitHub starsUsed in 1 repo~1.4k tokens
    Game DevelopmentAuto-check passed
  • New Experiment

    Tresjs/tres

    Create a new experiment in TresJS Lab with all necessary files

    3.8k GitHub stars~782 tokensUpdated today
    Game DevelopmentAuto-check passed
  • Threejs Gameplay Systems

    corosolto/client

    Build and iterate playable Three.js game systems. An agent skill from corosolto/client.

    257 GitHub stars~1.5k tokensUpdated today
    Game DevelopmentAuto-check passed
  • Deploy

    cyanfish-x/tellux

    Deploy tellux examples/docs sites via project scripts — one local command (pnpm run deploy) rclone-syncs to the self-hosted site then Wrangler Direct Uploads to Cloudflare Pages.

    207 GitHub stars~1.1k tokensUpdated 17 days ago
    Game DevelopmentAuto-check: notes
  • 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.

    213 GitHub stars~3k tokensUpdated 13 days ago
    Game DevelopmentAuto-check passed
  • Tinyworld Single File

    jasonkneen/tiny-world-builder

    A skill your agent uses when editing the Tiny World Builder repo, especially tiny-world-builder.html, to preserve the static classic-script Three.js r185 app structure and local edit/reload workflow.

    1.6k GitHub stars~1k tokensUpdated today
    Game DevelopmentAuto-check passed

More from pmndrs/viverse

  • Pmndrs Viverse

    pmndrs/viverse

    Build, modify, debug, or publish VIVERSE-ready web games and 3D apps with Three.js, React Three Fiber, @pmndrs/viverse, @react-three/viverse, VIVERSE SDK integrations, character controllers…

    132 GitHub stars~1.7k tokensUpdated 6 days ago
    Auto-check passed

Works with

Questions about Vitexec

What does Vitexec do?

A skill your agent uses when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured…. Vitexec is an agent skill from pmndrs/viverse. Use this skill when an AI agent needs to inspect, verify, debug, or profile a live Vite app by running temporary snippets inside the browser page and reading browser logs or captured artifacts.

When should I use Vitexec?

Vitexec fits situations like: an AI agent needs to inspect; profile a live Vite app by running temporary snippets inside the browser page and reading browser logs; captured artifacts; client state after interactions.

How do I install Vitexec in Claude Code?

Run `npx skills add pmndrs/viverse --skill vitexec -a claude-code`. Or copy the skill folder (.agents/skills/vitexec in pmndrs/viverse) into .claude/skills/vitexec in your project. Claude Code loads it when a task matches its description.

How do I install Vitexec in Codex?

Run `npx skills add pmndrs/viverse --skill vitexec -a codex`. Or copy the skill folder (.agents/skills/vitexec in pmndrs/viverse) into .agents/skills/vitexec in your project. Codex loads it when a task matches its description.

Can I use Vitexec 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 pmndrs/viverse --skill vitexec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vitexec, .gemini/skills/vitexec, .github/skills/vitexec and .opencode/skills/vitexec in your project.

What does Vitexec need to run?

Going by SKILL.md and its folder, Vitexec needs the command-line tools its instructions call (npm and pnpm). Our summary lists: Node.js.

Does Vitexec access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Vitexec 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 Vitexec use?

Vitexec has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Vitexec use?

About 2.5k tokens (SKILL.md is roughly 10k 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 1.4k tokens, read only when the agent opens those files.

What are the alternatives to Vitexec?

Skills that share tags, products or a category with Vitexec: Threejs Gameplay Systems (valkor-ai/loom, 1.2k stars), New Experiment (Tresjs/tres, 3.8k stars), Threejs Gameplay Systems (corosolto/client, 257 stars) and Deploy (cyanfish-x/tellux, 207 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Vitexec?

pmndrs (a GitHub organization) maintains it in pmndrs/viverse, which has 132 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 2, 2026.

Source: pmndrs/viverse on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.