Test262 Pass Rates
Show current test262 pass rates for both the js-host (gc) and standalone targets side by side, from committed baseline summaries — no network fetch, no compile. Use for a quick conformance status check.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Test262 Pass Rates when an AI agent needs a reusable SKILL.md workflow for this job: Show current test262 pass rates for both the js-host (gc) and standalone targets side by side, from committed baseline summaries — no network fetch, no compile. Use for a quick conformance status check.
When not to use it
Skip Test262 Pass Rates when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/test262-pass-rates # Save SKILL.md to ~/.claude/skills/test262-pass-rates/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/test262-pass-rates/SKILL.md. For a shared project, commit the folder at .claude/skills/test262-pass-rates/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Test262 Pass Rates skill for this task: Use Test262 Pass Rates when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 58/100
- Source signals
- 72/100
Model compatibility evidence
- claudeinferred
The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Test262 Pass Rates (js-host vs standalone)
Prints the current committed test262 conformance numbers for both compile targets side by side. Reads two committed, CI-refreshed summary files directly — no test run, no network fetch, near-instant.
## Data sources
- **js-host (gc target)**: `benchmarks/results/test262-current.json` — refreshed by the `promote-baseline` job in `test262-sharded.yml` on every push to main. Use `.summary` (or `.official_summary` if present) for `pass`/`total`, and `.summary.host_free_pass` for the narrower "passes with zero host imports" count (not the same as a standalone-target run — see below). - **standalone target**: `benchmarks/results/test262-standalone-highwater.json` — refreshed alongside the js-host baseline (same `sha`/`generated_at`). Use `.official_pass` / `.official_total` for the genuine standalone-target compile+run pass rate.
Both files are committed to the repo (small, ~KB-scale) and always reflect the last successful push-to-main run — check `.timestamp`/`.generated_at` and `.sha` against `git -C /workspace log -1 --format=%H` to confirm freshness; if the sha doesn't match current main, note that the numbers are as-of the last CI run, not live.
## Steps
1. Read both files:
```bash node -e " const host = require('/workspace/benchmarks/results/test262-current.json'); const sa = require('/workspace/benchmarks/results/test262-standalone-highwater.json'); const h = host.official_summary ?? host.summary; const hostPct = (100 * h.pass / h.total).toFixed(1); const saPct = (100 * sa.official_pass / sa.official_total).toFixed(1); const gap = h.pass - sa.official_pass; console.log('js-host (gc): ' + h.pass + ' / ' + h.total + ' (' + hostPct + '%)'); console.log('standalone: ' + sa.official_pass + ' / ' + sa.official_total + ' (' + saPct + '%)'); console.log('honest gap: ' + gap + ' tests pass under js-host but not standalone'); console.log('baseline sha: ' + host.baseline_sha); console.log('generated at: ' + host.timestamp); " ```
2. Report the three lines (js-host, standalone, gap) plus the baseline sha/timestamp so the user knows how fresh the numbers are. 3. If the user wants a live/fresh recompute instead of the committed baseline (e.g. mid-session after several merges), note that `pnpm run test:262` produces a new `test262-current.json` locally, and the standalone-highwater file is only refreshed by CI's `promote-baseline` job — a local standalone re-run needs `--target standalone`/`--target wasi` on the relevant runner, which is a much heavier operation than this quick check.
## Output format
``` js-host (gc): 31874 / 43106 (73.9%) standalone: 18415 / 43106 (42.7%) honest gap: 13459 tests pass under js-host but not standalone baseline sha: b71bea94d97021c21cb61ef2e0b553ad78916da9 generated at: 2026-07-03T07:31:22.294Z ```
Intended uses
- Use Test262 Pass Rates when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.