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.
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…
Install Webgpu Spec Lookup
$ npx skills add oframe/ogpu --skill webgpu-spec-lookup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install oframe/ogpu webgpu-spec-lookup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/oframe/ogpu.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/webgpu-spec-lookup .claude/skills/webgpu-spec-lookup && rm -rf skills-srcUse ~/.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/
Install the "webgpu-spec-lookup" agent skill from https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookup into .claude/skills/webgpu-spec-lookup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webgpu-spec-lookup", 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.
$skill-installer install https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookupType 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.
$ npx skills add oframe/ogpu --skill webgpu-spec-lookup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install oframe/ogpu webgpu-spec-lookup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oframe/ogpu.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/webgpu-spec-lookup .agents/skills/webgpu-spec-lookup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "webgpu-spec-lookup" agent skill from https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookup into .agents/skills/webgpu-spec-lookup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webgpu-spec-lookup", 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.
$ npx skills add oframe/ogpu --skill webgpu-spec-lookup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install oframe/ogpu webgpu-spec-lookup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oframe/ogpu.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/webgpu-spec-lookup .cursor/skills/webgpu-spec-lookup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "webgpu-spec-lookup" agent skill from https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookup into .cursor/skills/webgpu-spec-lookup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webgpu-spec-lookup", 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.
$ gemini skills install https://github.com/oframe/ogpu.git --path .claude/skills/webgpu-spec-lookup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add oframe/ogpu --skill webgpu-spec-lookup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install oframe/ogpu webgpu-spec-lookup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oframe/ogpu.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/webgpu-spec-lookup .gemini/skills/webgpu-spec-lookup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "webgpu-spec-lookup" agent skill from https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookup into .gemini/skills/webgpu-spec-lookup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webgpu-spec-lookup", 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.
$ gh skill install oframe/ogpu webgpu-spec-lookupInstalls 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).
$ npx skills add oframe/ogpu --skill webgpu-spec-lookup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/oframe/ogpu.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/webgpu-spec-lookup .github/skills/webgpu-spec-lookup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "webgpu-spec-lookup" agent skill from https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookup into .github/skills/webgpu-spec-lookup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webgpu-spec-lookup", 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.
$ npx skills add oframe/ogpu --skill webgpu-spec-lookup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install oframe/ogpu webgpu-spec-lookup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/oframe/ogpu.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/webgpu-spec-lookup .opencode/skills/webgpu-spec-lookup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "webgpu-spec-lookup" agent skill from https://github.com/oframe/ogpu/tree/main/.claude/skills/webgpu-spec-lookup into .opencode/skills/webgpu-spec-lookup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "webgpu-spec-lookup", 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
webgpu-spec-lookup- GitHub stars
- 151
- Token cost
- ~1.3k tokens
- SKILL.md length
- 632 words
- Files
- 2
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Unlicense
At a glance
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…
- Works in 2 steps: Chrome WebGPU docs / "What's New" —… → W3C WebGPU spec — authoritative API…
- A question is about WebGPU as a platform rather than OGPUs own code: is X supported in Chrome/Safari/Firefox
- SKILL.md covers Sources, Worked example: "are 64-bit…, Tie back to OGPU and How to apply what you find
- Runs Python scripts from its folder; reaches w3.org
What it does
Webgpu Spec Lookup is an agent skill from 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 WebGPU docs and the W3C spec before responding, instead of answering from memory. Use whenever a question is about WebGPU as a platform rather than OGPU's own code: "is X supported in Chrome/Safari/Firefox", "are 64-bit atomics available", "what's the default maxStorageBufferBindingSize", "does WebGPU have feature Y yet"…
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `update_spec.py`).
It sits in Development. The repository describes itself as: Minimal WebGPU Library. The licence is Unlicense.
When your agent uses it
- A question is about WebGPU as a platform rather than OGPUs own code: is X supported in Chrome/Safari/Firefox
- Are 64-bit atomics available
- Whats the default maxStorageBufferBindingSize
- Does WebGPU have feature Y yet
Example prompts
- “s own code:”
- “are 64-bit atomics available”
- “s the default maxStorageBufferBindingSize”
- “/webgpu-spec-lookup”
Requirements
- Python 3
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Chrome WebGPU docs / "What's New" — reality of what's shipped. (WebFetch)
- W3C WebGPU spec — authoritative API surface. (local cache, grep — not WebFetch)
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
Ships script files (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
w3.org
Also links to:
developer.chrome.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
Webgpu Spec Lookup loads about 1.3k tokens when it runs. Until then it costs about 190 tokens; SKILL.md has 632 words of instructions outside code blocks.
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). 632 words, ~1,326 tokens.
Download SKILL.mdSave it as
.claude/skills/webgpu-spec-lookup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- webgpu-spec-lookup
- description
- 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 WebGPU docs and the W3C spec before responding, instead of answering from memory. Use whenever a question is about WebGPU as a platform rather than OGPU's own code: "is X supported in Chrome/Safari/Firefox", "are 64-bit atomics available", "what's the default maxStorageBufferBindingSize", "does WebGPU have feature Y yet", "what's new in WebGPU", "is timestamp-query / shader-f16 / float32-filterable shipping", origin-trial/flag status, or whether some API is in the spec at all. WebGPU moves fast and memory goes stale — fetch the sources first.
Answer WebGPU-platform questions from the live docs, not from memory
WebGPU is a moving target: features ship per Chrome milestone, limits get raised, things sit behind flags or origin trials, and the spec adds capabilities on a rolling basis. Whatever you recall about "is X supported" or "what's the default limit" is liable to be months stale, and a confident wrong answer about browser support or a feature name wastes the user's time. The cost of fetching is a few seconds. So for platform questions, check the sources before answering.
This skill is for questions about WebGPU the platform — support, features,
limits, spec behavior. It is NOT for questions about OGPU's own engine code
(that's the codebase) or the webgpu-utils library (that's the
webgpu-utils-lookup skill).
Sources
Two sources answer different things — query each its own way:
Chrome WebGPU docs / "What's New" — reality of what's shipped. (WebFetch) https://developer.chrome.com/docs/web-platform/webgpu This is the entry point; the per-release "What's New in WebGPU (Chrome NNN)" posts are where feature-shipping, flags, origin trials, and raised limits are announced. The landing page links to them — if the answer needs a specific milestone, follow the link (or WebSearch
What's New in WebGPU Chrometo find the most recent post). Use this for: "is it shipping / in which Chrome / behind a flag / in an origin trial", and browser-compat reality.W3C WebGPU spec — authoritative API surface. (local cache, grep — not WebFetch) The spec is one 4.5 MB page; WebFetch'ing it per question is slow and lossy. Instead query a preprocessed local copy:
sh # Prints the cache path; (re)downloads + strips to text only when the cached # copy's date != today. Run it first, then grep the path it prints. python3 .claude/skills/webgpu-spec-lookup/update_spec.py grep -n -i "maxStorageBufferBindingSize" .claude/skills/webgpu-spec-lookup/webgpu-spec.txtThe text keeps each heading prefixed
[#anchor], so a grep hit traces back to a spec section (openhttps://www.w3.org/TR/webgpu/#<anchor>for the source). Use this for: exact feature names (theGPUFeatureNameenum — e.g.timestamp-query,shader-f16,float32-filterable,depth32float-stencil8, texture-compression families), default and required limit values (GPUSupportedLimits), and whether a capability exists in the spec at all versus being a proposal. Quote the exact identifier and value.
You usually need both: the spec says what the feature is called and what it guarantees; the Chrome docs say whether it's actually available and where. Cross-browser nuance (Safari/Firefox) isn't covered by either — if the question hinges on a non-Chrome browser, say what the spec defines and what Chrome ships, and flag that the other browsers' status isn't in these sources (MDN/caniuse would be needed, and the user didn't point there).
Show full SKILL.md (211 more words)Show less
Worked example: "are 64-bit atomics supported?"
Don't answer from memory. Fetch the spec to find the real feature name (64-bit
integer atomics are gated behind a WGSL/feature flag, not baseline), then the
Chrome "What's New" posts to see if/when it shipped or whether it's still
experimental / flagged. Report the exact GPUFeatureName, the Chrome status, and
that the user must feature-detect it (adapter.features.has(...)) — never assume
presence.
Tie back to OGPU
When the platform answer affects engine code, connect it: Renderer.initDevice
(src/core/Renderer.js) keeps a wantedFeatures wishlist and feature-detects
each entry against adapter.features before requesting the device, dropping
(and console.warn-ing) anything missing — so the engine boots anywhere but
optional features may be absent at runtime. Any code path depending on a feature
you just researched must guard on device.features.has(...) (precedent:
TimingHelper gating 'timestamp-query'). See the "Browser floor" section of
CLAUDE.md.
How to apply what you find
- Quote exact identifiers and values from the spec (feature names, limit defaults) rather than paraphrasing.
- State the Chrome version / flag / origin-trial status when support is the question, and cite which "What's New" post it came from.
- If the sources disagree with what you half-remember, trust the sources and say so. If a question can't be settled from these two (e.g. Safari timeline), say what's missing instead of guessing.
© 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 1 other file in .claude/skills/webgpu-spec-lookup of oframe/ogpu.
- SKILL.md
- update_spec.py
Open the folder on GitHubat commit 65e0a1a
Compare with similar skills
Webgpu Spec 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Webgpu Spec Lookup this skilloframe/ogpu | 151 | — | ~1.3k | Automated safety check: Pass | Unlicense | |
| Finishing a Development Branchobra/superpowers | 296k | 5 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Typescript Advanced Typesrolling-scopes/rsschool-app | 10k | 24 repos | ~4.2k | Automated safety check: Pass | MPL-2.0 | |
| PR Babysitteropeninterpreter/openinterpreter | 69k | 3 repos | ~4.2k | Automated safety check: Pass | Apache-2.0 | |
| Code Review ChecklistshareAI-lab/learn-claude-code | 78k | 5 repos | ~1.1k | Automated safety check: Pass | MIT | |
| Greplooponyx-dot-app/onyx | 32k | 4 repos | ~3.3k | Automated safety check: Pass | MIT |
Similar skills
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.
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.
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.
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.
Guidelines
akash-network/node
Behavioral guidelines to reduce common LLM coding mistakes. An agent skill from akash-network/node.
More from oframe/ogpu
Scaffold Shader
oframe/ogpu
Scaffold a new simple WGSL shader for the OGPU engine, wired for a RenderPipeline + Mesh.
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.
Webgpu Utils Lookup
oframe/ogpu
Ground any answer about the webgpu-utils library (greggman/webgpu-utils) in its actual API before responding.
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…
Pbr Shading
oframe/ogpu
Fold PBR/IBL shading into a RenderPipeline in the OGPU engine.
Shadow Mapping
oframe/ogpu
Fold real-time shadow mapping into an existing RenderPipeline/shader in the OGPU engine.
Related
Categories
Questions about Webgpu Spec Lookup
What does Webgpu Spec Lookup do?
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…. Webgpu Spec Lookup is an agent skill from 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 WebGPU docs and the W3C spec before responding, instead of answering from memory.
When should I use Webgpu Spec Lookup?
Webgpu Spec Lookup fits situations like: A question is about WebGPU as a platform rather than OGPUs own code: is X supported in Chrome/Safari/Firefox; are 64-bit atomics available; whats the default maxStorageBufferBindingSize; does WebGPU have feature Y yet.
How do I install Webgpu Spec Lookup in Claude Code?
Run `npx skills add oframe/ogpu --skill webgpu-spec-lookup -a claude-code`. Or copy the skill folder (.claude/skills/webgpu-spec-lookup in oframe/ogpu) into .claude/skills/webgpu-spec-lookup in your project. Claude Code loads it when a task matches its description.
How do I install Webgpu Spec Lookup in Codex?
Run `npx skills add oframe/ogpu --skill webgpu-spec-lookup -a codex`. Or copy the skill folder (.claude/skills/webgpu-spec-lookup in oframe/ogpu) into .agents/skills/webgpu-spec-lookup in your project. Codex loads it when a task matches its description.
Can I use Webgpu Spec 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-spec-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-spec-lookup, .gemini/skills/webgpu-spec-lookup, .github/skills/webgpu-spec-lookup and .opencode/skills/webgpu-spec-lookup in your project.
What does Webgpu Spec Lookup need to run?
Going by SKILL.md and its folder, Webgpu Spec Lookup needs Python for the scripts in its folder. Our summary lists: Python 3.
Does Webgpu Spec Lookup access the network?
SKILL.md names 2 domains. In commands or code: w3.org; the agent is likely to contact it when it follows the instructions. As links in the text: developer.chrome.com. This is read from the text; nothing was executed.
Is Webgpu Spec 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 Spec Lookup use?
Webgpu Spec 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 Spec Lookup use?
About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Webgpu Spec Lookup?
Skills that share tags, products or a category with Webgpu Spec 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 Spec 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.