New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Webgpu Utils Lookup

by oframe in oframe/ogpu

Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding.

UnlicenseAuto-check passedDevelopment

Install Webgpu Utils Lookup

skills CLI
$ npx skills add oframe/ogpu --skill webgpu-utils-lookup -a claude-code

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

GitHub CLI
$ gh skill install oframe/ogpu webgpu-utils-lookup --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/oframe/ogpu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/webgpu-utils-lookup .claude/skills/webgpu-utils-lookup && 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
webgpu-utils-lookup
GitHub stars
151
Token cost
~1.4k tokens
SKILL.md length
618 words
Files
3 (incl. references)
Skills in repo
7
Repo updated
First seen
Licence
Unlicense

At a glance

Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding.

  • Works in 4 steps: Local types — authoritative for the… → Local implementation — when behavior… → GitHub repo — for rationale, latest… → …
  • Task touches a webgpu-utils function
  • SKILL.md covers Lookup order, How to apply what you find and The two highest-traffic areas
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Webgpu Utils Lookup is an agent skill from oframe/ogpu. Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding. Use whenever a question or task touches a webgpu-utils function, class, or option — makeShaderDataDefinitions, makeStructuredView, createBuffersAndAttributesFromArrays, createTextureFromImage(s)/Source(s), generateMipmap, primitives., setStructuredView, the reflected uniform/storage views, bind-group-layout generation, attribute/buffer creation, mip generation, or anything imported from 'webgpu-utils'. In…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `evals/trigger-eval.json` and `references/api-map.md`).

It sits in Development. The repository describes itself as: Minimal WebGPU Library. The licence is Unlicense.

When your agent uses it

  • Task touches a webgpu-utils function
  • Option — makeShaderDataDefinitions
  • MakeStructuredView
  • CreateBuffersAndAttributesFromArrays

Example prompts

  • “webgpu-utils”
  • “/webgpu-utils-lookup”

Workflow steps

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

  1. Local types — authoritative for the installed version. The .d.ts files
  2. Local implementation — when behavior isn't clear from the type alone.
  3. GitHub repo — for rationale, latest source, history, issues. Use when the
  4. Typedoc site — human-readable index / cross-links. Good for browsing the

What it can do on your machine

Read from SKILL.md and the folder at commit 65e0a1a. 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

    No scripts in the folder and no shell commands in SKILL.md.

    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):

    • github.com
    • greggman.github.io

    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

Webgpu Utils Lookup loads about 1.4k tokens when it runs, and up to ~2.5k if it reads all its reference files. Until then it costs about 216 tokens; SKILL.md has 618 words of instructions outside code blocks.

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

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

The full file from oframe/ogpu at commit 65e0a1a, republished under its Unlicense licence (© oframe). 618 words, ~1,382 tokens.

Download SKILL.mdSave it as .claude/skills/webgpu-utils-lookup/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
webgpu-utils-lookup
description
Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding. Use whenever a question or task touches a webgpu-utils function, class, or option — makeShaderDataDefinitions, makeStructuredView, createBuffersAndAttributesFromArrays, createTextureFromImage(s)/Source(s), generateMipmap, primitives.*, setStructuredView, the reflected uniform/storage views, bind-group-layout generation, attribute/buffer creation, mip generation, or anything imported from 'webgpu-utils'. In the OGPU engine this library backs RenderPipeline, ComputeShader, Geometry, Texture, and IBLUtils, so it surfaces constantly — consult it before claiming a signature, option name, default, or behavior, rather than guessing from memory. Trigger even when the user doesn't name the library, if the symbol clearly belongs to it.

Answer webgpu-utils questions from the source, not from memory

webgpu-utils is small but full of non-obvious behavior: functions that mutate a passed-in view in place, reflection that keys uniforms by declared name, helpers that silently pick a texture view dimension for you, options whose defaults matter (mips, usage, viewDimension). Memory of "roughly how it works" is exactly where wrong answers come from — a misremembered option name or a stale signature compiles fine and then breaks at runtime with no error. The cost of checking is a few seconds; the cost of guessing is a silent garbage texture or a buffer written to the wrong offset. So check first.

This codebase pins webgpu-utils 1.11.0 (dist/1.x). The installed copy is the ground truth for this project — prefer it over anything you recall or find online, because online docs track latest and may have drifted.

Lookup order

  1. Local types — authoritative for the installed version. The .d.ts files carry full signatures, option-object shapes, defaults, and the doc-comments (often with usage examples). Read these first:

    node_modules/webgpu-utils/dist/1.x/<module>.d.ts

    references/api-map.md maps every exported symbol to its .d.ts module so you can jump straight to the right file.

  2. Local implementation — when behavior isn't clear from the type alone. Questions like "does it mutate the argument or return a copy?", "what does it default the format to?", "how does it decide cube vs 2d-array?" are answered by reading the compiled source:

    node_modules/webgpu-utils/dist/1.x/webgpu-utils.module.js

    It's readable ES — grep -n 'function <name>' to find the definition.

  3. GitHub repo — for rationale, latest source, history, issues. Use when the local copy doesn't settle it, when the user asks about a version newer than 1.11.0, or when "why does it do this" needs the original TypeScript / commit context: https://github.com/greggman/webgpu-utils (source under src/, one file per module mirroring the .d.ts names). Fetch with WebFetch.

  4. Typedoc site — human-readable index / cross-links. Good for browsing the API surface or linking the user somewhere: https://greggman.github.io/webgpu-utils/docs/. Fetch with WebFetch.

You do not need to walk all four every time. Stop at the first level that answers the question authoritatively — for a signature, level 1 alone is usually enough; reach for the repo/site only when local source can't answer it (design intent, newer versions, changelog).

Show full SKILL.md (252 more words)Show less

How to apply what you find

  • Quote the real thing. When you state a signature, option, or default, make it match the .d.ts you just read — exact option names, exact defaults. If you paraphrase, say so.
  • Mind the version. If you cite the GitHub/typedoc surface and it differs from local 1.11.0, flag the gap — the user runs 1.11.0.
  • Respect OGPU's wrappers. This engine rarely calls webgpu-utils raw; it wraps it (RenderPipeline → makeShaderDataDefinitions + makeStructuredView; Geometry → createBuffersAndAttributesFromArrays; Texture/IBLUtils → texture + mip helpers). When a question is really "how do I do X in OGPU", check how the wrapper already uses the helper (src/core/, src/utils/) before reaching for the raw call — the convention may already exist. The reflection-by-name rules (uniform block named uniforms, vs/fs entry points, t<Name> texture prefix) are OGPU conventions layered on top of the library's name-keyed reflection — see CLAUDE.md.

The two highest-traffic areas

Most OGPU questions land in one of these; know where they live.

  • WGSL reflection & structured writes (data-definitions.d.ts): makeShaderDataDefinitions(code) parses WGSL into defs; makeStructuredView(def, buffer?) builds a typed view whose .set({...}) writes by field name into an ArrayBuffer; setStructuredView/ setStructuredValues write into an existing view; makeBindGroupLayoutDescriptors derives layouts. This is how every pipeline's uniforms get written — name mismatches fail silently, so verify field names against the struct.

  • Geometry / vertex buffers (attribute-utils.d.ts): createBuffersAndAttributesFromArrays packs arrays into GPU buffers and emits bufferLayouts; @location is assigned by declaration order in the input object, not by name. Confirm order before trusting a binding.

For the full symbol → module table and the texture/mipmap/primitives groups, see references/api-map.md.

© oframe, Unlicense. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .claude/skills/webgpu-utils-lookup of oframe/ogpu.

  • SKILL.md
  • evals/trigger-eval.json
  • references/api-map.md

Open the folder on GitHubat commit 65e0a1a

Compare with similar skills

Webgpu Utils Lookup 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.

Webgpu Utils Lookup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Webgpu Utils Lookup this skilloframe/ogpu151—~1.4kAutomated safety check: PassUnlicense
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k24 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 24 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • Guidelines

    akash-network/node

    Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.

    1.1k GitHub starsUsed in 22 repos~577 tokens
    DevelopmentAuto-check passed

More from oframe/ogpu

  • Scaffold Shader

    oframe/ogpu

    Scaffold a new simple WGSL shader for the OGPU engine, wired for a RenderPipeline + Mesh.

    151 GitHub stars~1.4k tokensUpdated 11 days ago
    Auto-check passed

  • Scaffold App

    oframe/ogpu

    Scaffold a new OGPU example/app from scratch — a Renderer + Camera + Orbit + update loop and a single spinning cube wired through the vanilla Box primitive - RenderPipeline - Mesh setup.

    151 GitHub stars~1.1k tokensUpdated 11 days ago
    Auto-check passed

  • Naga Setup

    oframe/ogpu

    Get naga WGSL validation working in a repo — installs the naga/jq toolchain, a PostToolUse hook that compiles every .wgsl on write, and a batch validate-shaders script, so shader checking then…

    151 GitHub stars~1.9k tokensUpdated 11 days ago
    Auto-check passed

  • Webgpu Spec Lookup

    oframe/ogpu

    Ground any answer about the WebGPU platform itself — browser support/compatibility, feature availability, limits, what's shipping or behind a flag, and exact spec behavior — in the live Chrome…

    151 GitHub stars~1.3k tokensUpdated 11 days ago
    Auto-check passed

  • Pbr Shading

    oframe/ogpu

    Fold PBR/IBL shading into a RenderPipeline in the OGPU engine.

    151 GitHub stars~1.6k tokensUpdated 11 days ago
    Auto-check passed

  • Shadow Mapping

    oframe/ogpu

    Fold real-time shadow mapping into an existing RenderPipeline/shader in the OGPU engine.

    151 GitHub stars~1.9k tokensUpdated 11 days ago
    Auto-check passed

Categories

Questions about Webgpu Utils Lookup

What does Webgpu Utils Lookup do?

Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding. Webgpu Utils Lookup is an agent skill from oframe/ogpu. Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding.

When should I use Webgpu Utils Lookup?

Webgpu Utils Lookup fits situations like: task touches a webgpu-utils function; option — makeShaderDataDefinitions; makeStructuredView; createBuffersAndAttributesFromArrays.

How do I install Webgpu Utils Lookup in Claude Code?

Run `npx skills add oframe/ogpu --skill webgpu-utils-lookup -a claude-code`. Or copy the skill folder (.claude/skills/webgpu-utils-lookup in oframe/ogpu) into .claude/skills/webgpu-utils-lookup in your project. Claude Code loads it when a task matches its description.

How do I install Webgpu Utils Lookup in Codex?

Run `npx skills add oframe/ogpu --skill webgpu-utils-lookup -a codex`. Or copy the skill folder (.claude/skills/webgpu-utils-lookup in oframe/ogpu) into .agents/skills/webgpu-utils-lookup in your project. Codex loads it when a task matches its description.

Can I use Webgpu Utils Lookup 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 oframe/ogpu --skill webgpu-utils-lookup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/webgpu-utils-lookup, .gemini/skills/webgpu-utils-lookup, .github/skills/webgpu-utils-lookup and .opencode/skills/webgpu-utils-lookup in your project.

What does Webgpu Utils Lookup need to run?

SKILL.md names no scripts, command-line tools or credentials: Webgpu Utils Lookup is instructions for the agent only.

Does Webgpu Utils Lookup access the network?

SKILL.md names 2 domains. As links in the text: github.com and greggman.github.io. This is read from the text; nothing was executed.

Is Webgpu Utils Lookup 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 Webgpu Utils Lookup use?

Webgpu Utils Lookup is published under the Unlicense licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Webgpu Utils Lookup use?

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

What are the alternatives to Webgpu Utils Lookup?

Skills that share tags, products or a category with Webgpu Utils Lookup: Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars), PR Babysitter (openinterpreter/openinterpreter, 69k stars) and Code Review Checklist (shareAI-lab/learn-claude-code, 78k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Webgpu Utils Lookup?

oframe (a GitHub organization) maintains it in oframe/ogpu, which has 151 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 26, 2026.

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