Dataset Viewer
Auto-converted to Parquet Duplicate
name
stringlengths
19
34
instruction
stringlengths
1.04k
2.32k
description
stringlengths
110
196
keywords
listlengths
0
0
schema_version
stringclasses
1 value
config
unknown
metadata
unknown
files
listlengths
4
4
location
stringlengths
40
71
pool/honeypot-login-persistence-09
I'm writing up which bots got into our SSH honeypot by sheer persistence, and I need the numbers from yesterday's login log. The log is /home/user/honeypot/logins.csv, comma-separated with a header row: ts, session, src, username, password, outcome. One row is one login attempt; outcome is success or failed; ts is a U...
From a Cowrie honeypot login log, find sources whose first successful login followed 30+ failed attempts across sessions, with the winning credentials.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/honeypot-login-persistence-09", "description": "From a Cowrie honeypot login log, find sources whose first successful login followed 30+ failed attempts across sessions, with the winning credentials." }, "metadata": { "format_profile": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "CyberLab honeynet dataset (Zenodo 3687527), cyberlab_2019-12-10, sensor ubuntu-ssh (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/honeypot-login-persistence-09/tb2
pool/kev-epss-triage-02
Audit asked us to re-issue the patch-priority list for the vulnerability review of 2026-04-01, from that review's scanner export. The scanner export and two threat-intel feeds are on the box. The scanner export is /home/user/scan_findings.csv, comma-separated with a header row: finding_id, asset_id, plugin_id, cve_ids...
Tier the CVEs in a scanner export by CISA KEV (as of a past review date) ransomware use and membership, EPSS score and EPSS percentile, with distinct asset counts.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/kev-epss-triage-02", "description": "Tier the CVEs in a scanner export by CISA KEV (as of a past review date) ransomware use and membership, EPSS score and EPSS percentile, with distinct asset counts." }, "metadata": { "format_profile": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "CISA KEV catalog 2026.10.14 (cut at 2026-04-01) and FIRST EPSS scores 2026-04-01 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/kev-epss-triage-02/tb2
pool/kev-local-copy-drift-08
# KEV tracker drift check Our team keeps a local tracker of CISA's Known Exploited Vulnerabilities (KEV) catalog. It is meant to mirror catalog version **2026.10.01**, but people have been editing it by hand and pasting rows out of Excel. Before the audit I need to know exactly where it has drifted from the official c...
Diff a hand-edited local KEV tracker CSV against the official KEV catalog JSON, ignoring formatting noise, and report the drift as JSON.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/kev-local-copy-drift-08", "description": "Diff a hand-edited local KEV tracker CSV against the official KEV catalog JSON, ignoring formatting noise, and report the drift as JSON." }, "metadata": { "format_profile": "format-stress", "budget_tier"...
{ "format_profile": "format-stress", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "CISA KEV catalog 2026.10.01 JSON and CSV, kev-data commit a25b61f (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/kev-local-copy-drift-08/tb2
pool/nvd-cna-score-audit-04
I'm reviewing how far NVD's own CVSS v3 scores drift from the scores the CVE Numbering Authorities (CNAs) publish, and I need the list of big disagreements in a sample of 2024 CVEs. The input is /home/user/nvd_export.jsonl: one JSON object per line, 160 lines, one CVE each, taken from the NVD 2.0 JSON feed. Each objec...
Audit a sample of NVD 2024 CVE records for large disagreements between NVD and CNA CVSS v3 base scores, telling the CNA entry apart from CISA ADP entries.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/nvd-cna-score-audit-04", "description": "Audit a sample of NVD 2024 CVE records for large disagreements between NVD and CNA CVSS v3 base scores, telling the CNA entry apart from CISA ADP entries." }, "metadata": { "format_profile": "standard", "...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "NVD CVE API 2.0 JSON feed, nvdcve-2.0-2024 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/nvd-cna-score-audit-04/tb2
pool/osv-pypi-inventory-audit-06
I need a vulnerability audit of the Python packages on our application servers, using the PyPA advisory database. The inventory is /home/user/inventory.csv, comma-separated with a header row host_id,package,version: 70 rows, one installed package per row, 16 hosts. Every version in it is a plain release number made of...
Audit a Python package inventory against PyPA OSV advisories (ECOSYSTEM ranges, withdrawn entries, numeric version compare).
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/osv-pypi-inventory-audit-06", "description": "Audit a Python package inventory against PyPA OSV advisories (ECOSYSTEM ranges, withdrawn entries, numeric version compare)." }, "metadata": { "format_profile": "standard", "budget_tier": "standard",...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "PyPA advisory-database commit 182ac805 and PyPI release lists (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/osv-pypi-inventory-audit-06/tb2
pool/ssh-bruteforce-ledger-01
Hi, I'm on the incident response rotation this week and need a brute-force summary for our SSH bastion before tomorrow's review. The log is /home/user/auth.log: one day (Mar 14) of the bastion's sshd syslog, about 6,000 lines, plain text. Each line starts with the timestamp in the form "Mar 14 HH:MM:SS", then the host...
Count failed SSH password attempts per source IP from a day of sshd syslog (expanding repeat lines), and flag brute-force sources that later logged in.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ssh-bruteforce-ledger-01", "description": "Count failed SSH password attempts per source IP from a day of sshd syslog (expanding repeat lines), and flag brute-force sources that later logged in." }, "metadata": { "format_profile": "standard", "b...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "Loghub SSH (OpenSSH) log, Zenodo 8196385 v8 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/ssh-bruteforce-ledger-01/tb2
pool/ssh-failed-login-rule-05
# Detection rule: SSH password failures with user and source Our log forwarder takes one Python regular expression per alert and ships its named groups as fields. I need the rule for **failed SSH password attempts**, with the attempted account in a group named `user` and the source address in a group named `ip`. ## I...
Write a Python regex detection rule for failed SSH password attempts with named user and ip groups, scored on hidden real sshd lines.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ssh-failed-login-rule-05", "description": "Write a Python regex detection rule for failed SSH password attempts with named user and ip groups, scored on hidden real sshd lines." }, "metadata": { "format_profile": "format-stress", "budget_tier": ...
{ "format_profile": "format-stress", "budget_tier": "standard", "arena_domain": "cybersecurity", "source": "Loghub SSH (OpenSSH) log, Zenodo 8196385 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/cybersecurity/ssh-failed-login-rule-05/tb2
pool/callreport-texas-ratio-06
Hi! For our credit-risk screen I need the Texas ratio of every Arizona and Nevada bank as of 12/31/2025, from the Call Reports, with a flag on any bank at 10% or more. The data is in /home/user/call_20251231.tsv, cut from the FFIEC CDR "Four Periods" bulk download. It is tab-separated, one row per bank. Line 1 is the ...
Compute the Texas ratio for 30 AZ/NV banks from Call Report items identified by caption, with RCFD/RCON selection and a 10% watch flag.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/callreport-texas-ratio-06", "description": "Compute the Texas ratio for 30 AZ/NV banks from Call Report items identified by caption, with RCFD/RCON selection and a 10% watch flag." }, "metadata": { "arena_domain": "finance-economics", "source": ...
{ "arena_domain": "finance-economics", "source": "FFIEC CDR Call Reports Four Periods bulk, 2025 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/finance-economics/callreport-texas-ratio-06/tb2
pool/ferc-plant-rollforward-12
Hi! I'm auditing the electric plant in service schedules (FERC Form 1, page 204) that ten utilities filed for 2023 and 2024, and I need a list of every account that doesn't roll forward. The data is /home/user/plant_in_service.csv, a comma-separated file with a header line and 1,645 rows. Its columns are utility, year...
Audit a FERC Form 1 plant in service extract (PUDL, 10 disguised utilities, 2023-2024): list accounts whose signed roll-forward or year-to-year carry-over does not tie, skipping subtotal lines.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ferc-plant-rollforward-12", "description": "Audit a FERC Form 1 plant in service extract (PUDL, 10 disguised utilities, 2023-2024): list accounts whose signed roll-forward or year-to-year carry-over does not tie, skipping subtotal lines." }, "metadata":...
{ "format_profile": "standard", "budget_tier": "extended", "arena_domain": "finance-economics", "source": "PUDL v2025.9.0 core_ferc1__yearly_plant_in_service_sched204 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/finance-economics/ferc-plant-rollforward-12/tb2
pool/sec-derived-liabilities-08
Hi! I'm loading 10-Q balance sheets dated 2025-09-30 for a list of small SEC filers into our screening model, and the model needs total liabilities for every filing. Some filers never tag a total-liabilities line, so for those we derive it. The data is in /home/user/sec/num.txt, an extract of the "num" table from the ...
Pick face-of-balance-sheet XBRL facts from SEC FSDS num.txt and report or derive total liabilities for 70 small-filer 10-Qs.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/sec-derived-liabilities-08", "description": "Pick face-of-balance-sheet XBRL facts from SEC FSDS num.txt and report or derive total liabilities for 70 small-filer 10-Qs." }, "metadata": { "arena_domain": "finance-economics", "budget_tier": "exte...
{ "arena_domain": "finance-economics", "budget_tier": "extended", "source": "SEC Financial Statement Data Sets 2025q4 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/finance-economics/sec-derived-liabilities-08/tb2
pool/sec-keyed-balance-check-13
Hi! An intern re-keyed the September 30, 2025 balance sheets of 24 small SEC filers (annual 10-K reports, fiscal years ending September 30) into a spreadsheet by hand, and I need you to check every figure against the filed XBRL data before we use it. The keyed figures are in /home/user/keyed.csv, with the header adsh,...
Check 24 small filers' hand-keyed 10-K balance sheet figures against SEC FSDS num.txt XBRL facts and give each mismatch the first-matching issue code (missing, thousands, sign, prior-year, other).
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/sec-keyed-balance-check-13", "description": "Check 24 small filers' hand-keyed 10-K balance sheet figures against SEC FSDS num.txt XBRL facts and give each mismatch the first-matching issue code (missing, thousands, sign, prior-year, other)." }, "metada...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "finance-economics", "source": "SEC Financial Statement Data Sets 2025q4 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/finance-economics/sec-keyed-balance-check-13/tb2
pool/sec-liquidity-flags-11
Hi! I'm running a liquidity screen over the September 30, 2025 quarterly reports (10-Q, fiscal third quarter, calendar fiscal years) of 30 small SEC filers, and I need one flag per filing. The data is in /home/user/sec/num.txt, an extract of the "num" table from the SEC Financial Statement Data Sets. It is tab-separat...
Pick face-of-statement XBRL facts from SEC FSDS num.txt for 30 small-filer 10-Qs, compute current ratio and nine-month cash runway, and assign ordered liquidity flags.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/sec-liquidity-flags-11", "description": "Pick face-of-statement XBRL facts from SEC FSDS num.txt for 30 small-filer 10-Qs, compute current ratio and nine-month cash runway, and assign ordered liquidity flags." }, "metadata": { "budget_tier": "extend...
{ "budget_tier": "extended", "arena_domain": "finance-economics", "source": "SEC Financial Statement Data Sets 2025q4 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/finance-economics/sec-liquidity-flags-11/tb2
pool/acs-household-income-se-01
I'm writing up household income estimates for three survey areas from the American Community Survey public-use microdata, and I need the point estimates together with their standard errors. The file /home/user/households.csv is comma-separated with one header line and one row per housing-unit record from the 2023 one-...
Estimate households and mean adjusted household income for three areas from ACS PUMS housing records, with successive-difference replicate standard errors.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/acs-household-income-se-01", "description": "Estimate households and mean adjusted household income for three areas from ACS PUMS housing records, with successive-difference replicate standard errors." }, "metadata": { "format_profile": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "US Census Bureau ACS 2023 1-year PUMS housing records (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/acs-household-income-se-01/tb2
pool/b1-brfss-smoking-ageadj-10
I'm comparing adult smoking across three states from the 2023 BRFSS telephone survey, and because their age structures differ I need age-adjusted rates as well as crude ones. /home/user/brfss_smoking.csv is comma-separated with a header line and 10,232 rows, one per respondent: state (S1, S2 or S3), weight (the final ...
Crude and directly age-adjusted weighted smoking prevalence for three disguised states from BRFSS 2023 respondent records.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-brfss-smoking-ageadj-10", "description": "Crude and directly age-adjusted weighted smoking prevalence for three disguised states from BRFSS 2023 respondent records." }, "metadata": { "format_profile": "standard", "budget_tier": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "CDC BRFSS 2023 LLCP (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/b1-brfss-smoking-ageadj-10/tb2
pool/b1-cremona-integral-points-09
Our elliptic curve table lists, for each curve, the x-coordinates of all its integral points, and the lists were damaged in a copy: some true values were dropped and some values that are not integral points were added. I need the damage reported. /home/user/curves.csv is comma-separated with a header line and 50 rows:...
Audit damaged integral-point lists for 50 re-modelled Cremona elliptic curves: report bogus and missing x-coordinates.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-cremona-integral-points-09", "description": "Audit damaged integral-point lists for 50 re-modelled Cremona elliptic curves: report bogus and missing x-coordinates." }, "metadata": { "format_profile": "standard", "budget_tier": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "Cremona ecdata intpts.00000-09999, commit 25cec5e (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/b1-cremona-integral-points-09/tb2
pool/b1-cremona-isogeny-classes-07
Our elliptic curve table groups curves over the rationals into isogeny classes, and a few curves were filed under the wrong class. I need them found. /home/user/curves.csv is comma-separated with a header line and 58 rows: curve_id, class_id, a1, a2, a3, a4, a6. The integers give each curve as y^2 + a1*x*y + a3*y = x^...
Find curves filed under the wrong isogeny class in a re-modelled table of Cremona elliptic curves, by comparing a_p from point counts.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-cremona-isogeny-classes-07", "description": "Find curves filed under the wrong isogeny class in a re-modelled table of Cremona elliptic curves, by comparing a_p from point counts." }, "metadata": { "format_profile": "standard", "budget_tier":...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "Cremona ecdata allcurves.20000-29999, commit 25cec5e (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/b1-cremona-isogeny-classes-07/tb2
pool/b1-nhanes-bp-prevalence-05
I need survey-weighted estimates of high blood pressure among US adults from the NHANES 2017-2018 examination data, with design-based standard errors. /home/user/nhanes_bp.csv is comma-separated with a header line and one row per sampled person (9,254 rows). Its columns are SEQN (respondent id), RIAGENDR (1 male, 2 fe...
Survey-weighted prevalence of high blood pressure in NHANES 2017-2018 adults, with Taylor-linearized standard errors over strata and PSUs.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-nhanes-bp-prevalence-05", "description": "Survey-weighted prevalence of high blood pressure in NHANES 2017-2018 adults, with Taylor-linearized standard errors over strata and PSUs." }, "metadata": { "format_profile": "standard", "budget_tier"...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "NHANES 2017-2018 DEMO_J and BPX_J (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/b1-nhanes-bp-prevalence-05/tb2
pool/b1-nhanes-ckd-stages-13
I'm summarizing kidney function among US adults from the NHANES 2017-2018 examination data and need the eGFR stage counts and a weighted chronic kidney disease prevalence. /home/user/nhanes_kidney.csv is comma-separated with a header line and one row per sampled person (9,254 rows): SEQN (respondent id), RIAGENDR (1 m...
CKD-EPI 2021 eGFR, KDIGO stage counts and weighted chronic kidney disease prevalence from NHANES 2017-2018 examination data.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-nhanes-ckd-stages-13", "description": "CKD-EPI 2021 eGFR, KDIGO stage counts and weighted chronic kidney disease prevalence from NHANES 2017-2018 examination data." }, "metadata": { "format_profile": "standard", "budget_tier": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "NHANES 2017-2018 DEMO_J, BIOPRO_J, ALB_CR_J (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/b1-nhanes-ckd-stages-13/tb2
pool/cremona-curve-audit-02
Some entries in our table of elliptic curves were damaged when it was assembled, and I need them found before it goes into the database. /home/user/curves.tsv is tab-separated with a header line and 60 rows. Columns: curve_id, a1, a2, a3, a4, a6, ap, gens. The integers a1 to a6 give the curve y^2 + a1*x*y + a3*y = x^...
Audit a table of elliptic curves (Cremona ecdata, re-modelled) for wrong a_p values and points not on the curve.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/cremona-curve-audit-02", "description": "Audit a table of elliptic curves (Cremona ecdata, re-modelled) for wrong a_p values and points not on the curve." }, "metadata": { "format_profile": "standard", "budget_tier": "standard", "arena_domai...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "mathematics-or-formal-reasoning", "source": "Cremona ecdata allgens/aplist 10000-19999, commit 25cec5e (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/mathematics-or-formal-reasoning/cremona-curve-audit-02/tb2
pool/b1-audiobook-chapters-09
# Chapter markers for audiobook masters We are muxing five public-domain audiobooks into single files and need an FFmpeg chapter-metadata file for each one, built from our section list. ## Input `/home/user/audiobook masters/sections.tsv` (note the space in the directory name) — UTF-8, tab-separated, one header line...
Write FFmpeg FFMETADATA1 chapter files for LibriVox audiobooks: contiguous ms chapters, HTML-cleaned and escaped section titles.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-audiobook-chapters-09", "description": "Write FFmpeg FFMETADATA1 chapter files for LibriVox audiobooks: contiguous ms chapters, HTML-cleaned and escaped section titles." }, "metadata": { "format_profile": "format-stress", "budget_tier": "stan...
{ "format_profile": "format-stress", "budget_tier": "standard", "arena_domain": "media-content-production", "source": "LibriVox catalogue API, 2026-10-14 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/media-content-production/b1-audiobook-chapters-09/tb2
pool/b1-fluent-l10n-qa-02
# Fluent localization QA: Polish tab strings A vendor sent back the Polish (`pl`) translation of our tab-strip strings, but it was translated against an older copy of the English source. Before it goes into the build, QA it against the **current** English source. ## Inputs All files are UTF-8 Fluent (`.ftl`). Note t...
QA a Polish Fluent translation against the current en-US source: missing and obsolete ids, unknown variables, missing attributes.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-fluent-l10n-qa-02", "description": "QA a Polish Fluent translation against the current en-US source: missing and obsolete ids, unknown variables, missing attributes." }, "metadata": { "format_profile": "format-stress", "budget_tier": "standar...
{ "format_profile": "format-stress", "budget_tier": "standard", "arena_domain": "media-content-production", "source": "Mozilla firefox-l10n-source @125d051b + firefox-l10n @f95b1510 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/media-content-production/b1-fluent-l10n-qa-02/tb2
pool/b1-isbn-audit-05
I'm preparing a batch of book records from our catalogue for a retailer feed, and the feed only accepts editions with a correct ISBN-13. Please audit the ISBNs. The records are in /home/user/editions.tsv, a small tab-separated file with one header line and 37 editions, one per line. The columns are edition_key, isbn_1...
Audit ISBN-10/ISBN-13 values of Open Library editions (check digits, 10->13 consistency) and emit a feed ISBN-13 and status per edition.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-isbn-audit-05", "description": "Audit ISBN-10/ISBN-13 values of Open Library editions (check digits, 10->13 consistency) and emit a feed ISBN-13 and status per edition." }, "metadata": { "format_profile": "standard", "budget_tier": "standard"...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "media-content-production", "source": "Open Library edition records, 2026-10-14 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/media-content-production/b1-isbn-audit-05/tb2
pool/b1-met-dimensions-03
# Check painting dimensions before the catalogue goes to print The registrar exported the dimension lines of 24 paintings from our collection database. Each line gives the size in inches followed by a metric conversion in parentheses, and a few of the metric figures were mistyped. The print catalogue needs a clean met...
Parse free-text museum dimension lines (inches with fractions, cm or mm), convert to cm and flag mistyped metric conversions.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-met-dimensions-03", "description": "Parse free-text museum dimension lines (inches with fractions, cm or mm), convert to cm and flag mistyped metric conversions." }, "metadata": { "format_profile": "format-stress", "budget_tier": "standard", ...
{ "format_profile": "format-stress", "budget_tier": "standard", "arena_domain": "media-content-production", "source": "The Met Open Access collection data, 2026-10-14 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/media-content-production/b1-met-dimensions-03/tb2
pool/b1-tracklist-recon-01
Hi, I look after our label's back-catalogue metadata. Before we push corrections upstream I need the CD releases in our MusicBrainz export reconciled against the Discogs export of the same catalogue. There are two tab-separated files, each with one header line. They are about 290 lines each, too long to print in full,...
Reconcile a label's CD releases between MusicBrainz and Discogs exports by barcode and report track-count and runtime status per release.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-tracklist-recon-01", "description": "Reconcile a label's CD releases between MusicBrainz and Discogs exports by barcode and report track-count and runtime status per release." }, "metadata": { "format_profile": "standard", "budget_tier": "sta...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "media-content-production", "source": "MusicBrainz core data + Discogs release data, 2026-10-14 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/media-content-production/b1-tracklist-recon-01/tb2
pool/b1-vinyl-sides-08
Before we send a batch of vinyl reissues to the cutting room, I need every side checked against our cutting-time limits, because an over-long side has to be cut quieter or re-sequenced. There are two tab-separated files, each with one header line. /home/user/cutting/releases.tsv has one line per release (36 releases) ...
Sum Discogs vinyl tracklists per side (A/B/AA ...) and flag sides over the cutting limit for the record speed.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-vinyl-sides-08", "description": "Sum Discogs vinyl tracklists per side (A/B/AA ...) and flag sides over the cutting limit for the record speed." }, "metadata": { "format_profile": "standard", "budget_tier": "standard", "arena_domain": "me...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "media-content-production", "source": "Discogs release data, 2026-10-14 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/media-content-production/b1-vinyl-sides-08/tb2
pool/ghcn-monthly-temps-02
I need monthly temperature summaries for one of our cooperative weather stations, built straight from its daily record, for January 2022 through December 2024. The record is /home/user/station.dly, in the GHCN-Daily fixed-width format: one line per station, month and element, with no header. Columns 1-11 are the stati...
Parse a GHCN-Daily fixed-width station record and compute QC-aware monthly TMAX/TMIN means with valid-day counts and a completeness rule.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ghcn-monthly-temps-02", "description": "Parse a GHCN-Daily fixed-width station record and compute QC-aware monthly TMAX/TMIN means with valid-day counts and a completeness rule." }, "metadata": { "format_profile": "standard", "budget_tier": "sta...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "natural-science", "source": "GHCN-Daily v3.35 (upd-2026101317), one station 2022-2024 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/natural-science/ghcn-monthly-temps-02/tb2
pool/ghcn-multiday-precip-08
I need annual precipitation totals for five of our cooperative stations for 2021 to 2024, with an honest count of the days the totals don't cover. The record is /home/user/network.dly, in the GHCN-Daily fixed-width format: one line per station, month and element, no header. Columns 1-11 are the station id, 12-15 the y...
Annual precipitation accounting for five GHCN-Daily stations: fixed-width parsing, QFLAG and sentinel rules, MDPR/DAPR multi-day totals and uncovered-day counts.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ghcn-multiday-precip-08", "description": "Annual precipitation accounting for five GHCN-Daily stations: fixed-width parsing, QFLAG and sentinel rules, MDPR/DAPR multi-day totals and uncovered-day counts." }, "metadata": { "format_profile": "standard...
{ "format_profile": "standard", "budget_tier": "extended", "arena_domain": "natural-science", "source": "GHCN-Daily v3.35 (upd-2026101317), five stations 2021-2024 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/natural-science/ghcn-multiday-precip-08/tb2
pool/ibtracs-ace-07
I need accumulated cyclone energy (ACE) for every tropical cyclone of the 2024 season, worldwide, from our best-track extract. The file is /home/user/tracks_2024.csv, an IBTrACS-format CSV (about 5,900 fixes, too long to read through, so use a script). Line 1 is the column header and line 2 is a units line (kts, mb, k...
Compute per-storm accumulated cyclone energy for the 2024 global season from an IBTrACS-format extract (units line, synoptic-only fixes, nature and 35 kt rules).
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ibtracs-ace-07", "description": "Compute per-storm accumulated cyclone energy for the 2024 global season from an IBTrACS-format extract (units line, synoptic-only fixes, nature and 35 kt rules)." }, "metadata": { "format_profile": "standard", "b...
{ "format_profile": "standard", "budget_tier": "extended", "arena_domain": "natural-science", "source": "IBTrACS v04r01, last3years CSV snapshot 2026-10-13 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/natural-science/ibtracs-ace-07/tb2
pool/ndbc-buoy-annual-04
I'm comparing three years of standard meteorological data from one of our offshore buoys and need a small annual summary for each year. The files are /home/user/buoy_2006.txt, /home/user/buoy_2016.txt and /home/user/buoy_2024.txt, NDBC historical stdmet text files, one per year. Each is whitespace-separated with one o...
Harmonise four NDBC stdmet buoy files across format eras (header drift, sentinels, sampling change, year-boundary record) into per-year wave, water-temperature and pressure summaries.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ndbc-buoy-annual-04", "description": "Harmonise four NDBC stdmet buoy files across format eras (header drift, sentinels, sampling change, year-boundary record) into per-year wave, water-temperature and pressure summaries." }, "metadata": { "format_p...
{ "format_profile": "standard", "budget_tier": "extended", "arena_domain": "natural-science", "source": "NDBC historical stdmet, one buoy, 1998/2006/2016/2024 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/natural-science/ndbc-buoy-annual-04/tb2
pool/ndbc-qc-flags-09
Before we ingest last year's record from one of our moored buoys, I need it run through our basic QC screen, and I want the list of lines that fail. The file is /home/user/buoy_2019.txt, an NDBC standard meteorological text file with about 14,900 lines, far too many to read, so use a script. Lines 1 and 2 are header l...
Apply an ordered QC screen (duplicate timestamps, range checks that skip sentinels, gust below wind) to a year of NDBC buoy observations and list the failing lines.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/ndbc-qc-flags-09", "description": "Apply an ordered QC screen (duplicate timestamps, range checks that skip sentinels, gust below wind) to a year of NDBC buoy observations and list the failing lines." }, "metadata": { "format_profile": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "natural-science", "source": "NDBC historical stdmet, one buoy, 2019, with planted defects (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/natural-science/ndbc-qc-flags-09/tb2
pool/sifts-coverage-03
We want to know how much of each of our 14 target proteins is covered by good-quality crystal or cryo-EM structures, measured on the UniProt sequence. You have three files. /home/user/segments.csv is a SIFTS-style residue-level mapping table: line 1 is a comment starting with #, line 2 is the header PDB,CHAIN,SP_PRIMA...
Compute UniProt sequence coverage by PDB entries at or below 2.5 A by joining a SIFTS segment table to the wwPDB resolution index and taking interval unions.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/sifts-coverage-03", "description": "Compute UniProt sequence coverage by PDB entries at or below 2.5 A by joining a SIFTS segment table to the wwPDB resolution index and taking interval unions." }, "metadata": { "format_profile": "standard", "bu...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "natural-science", "source": "SIFTS pdb_chain_uniprot 2026/10/11 (PDB 41.26, UniProt 2026_03) + wwPDB resolu.idx 2026-10-09 (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/natural-science/sifts-coverage-03/tb2
pool/b1-actions-token-perms-17
Hi, I'm reviewing what the GITHUB_TOKEN can do in the GitHub Actions workflows we vendor from six upstream projects. The workflow files are in /home/user/workflows, in six folders (astral-sh__uv, fastapi__fastapi, pallets__click, pypa__cibuildwheel, pytest-dev__pytest, python-poetry__poetry), 89 .yml or .yaml files in...
Resolve effective GITHUB_TOKEN permissions for every job in 89 real workflows (job overrides workflow, defaults) and flag write-capable jobs under pull_request_target/workflow_run.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-actions-token-perms-17", "description": "Resolve effective GITHUB_TOKEN permissions for every job in 89 real workflows (job overrides workflow, defaults) and flag write-capable jobs under pull_request_target/workflow_run." }, "metadata": { "forma...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "software-engineering", "source": "Workflow files of six OSS repositories at pinned commits (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/software-engineering/b1-actions-token-perms-17/tb2
pool/b1-classifier-pyver-audit-15
Hi, I'm checking whether 42 of our PyPI dependencies advertise Python versions their own requires_python actually excludes. /home/user/packages.csv is comma-separated with the header package,requires_python,classifiers and one row per package. requires_python is a PEP 440 specifier set such as >=3.9 or !=3.9.0,!=3.9.1...
Find Python-version classifiers that 42 PyPI packages advertise but their own requires_python excludes, judged over patch releases.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-classifier-pyver-audit-15", "description": "Find Python-version classifiers that 42 PyPI packages advertise but their own requires_python excludes, judged over patch releases." }, "metadata": { "format_profile": "standard", "budget_tier": "st...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "software-engineering", "source": "pypi-data SQLite snapshot 2026.07.21, packages and classifiers tables (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/software-engineering/b1-classifier-pyver-audit-15/tb2
pool/b1-codeowners-resolve-09
Hi, we are setting up review routing and I need to know who GitHub would request as code owners for a list of files in our repository. /home/user/CODEOWNERS is the repository's CODEOWNERS file (about 660 lines). Blank lines and lines starting with # are ignored. Every other line is a path pattern followed by zero or m...
Resolve GitHub CODEOWNERS for 160 paths of a real repository: gitignore pattern semantics, last match wins, owner-less rules.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-codeowners-resolve-09", "description": "Resolve GitHub CODEOWNERS for 160 paths of a real repository: gitignore pattern semantics, last match wins, owner-less rules." }, "metadata": { "format_profile": "standard", "budget_tier": "standard", ...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "software-engineering", "source": "CPython .github/CODEOWNERS and file tree at a pinned commit (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/software-engineering/b1-codeowners-resolve-09/tb2
pool/b1-specifier-hygiene-14
Hi, I'm reviewing how strictly our 34 PyPI dependencies constrain their own dependencies. /home/user/requirements.csv is comma-separated with the header package,requirement and 287 rows: each requirement string (PEP 508, possibly with extras and an environment marker) that the current release of each package declares....
Class 271 real PEP 508 requirement strings of 30 PyPI packages as pinned, bounded, floor or open (PEP 440 operator semantics) and count per package.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-specifier-hygiene-14", "description": "Class 271 real PEP 508 requirement strings of 30 PyPI packages as pinned, bounded, floor or open (PEP 440 operator semantics) and count per package." }, "metadata": { "format_profile": "standard", "budge...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "software-engineering", "source": "pypi-data SQLite snapshot 2026.07.21, deps table (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/software-engineering/b1-specifier-hygiene-14/tb2
pool/b1-zk-session-ledger-03
Hi, I need a ledger of every client session on our three-node ZooKeeper ensemble, built from the server logs. The input is /home/user/zookeeper.log: about 74,000 lines (10 MB, too long to print), the three servers' logs concatenated, so it is not in time order overall. Lines end with CRLF, so strip the trailing carria...
Build a per-session ledger (client, reattaches, expiry vs client close, lifetime) from a real three-server ZooKeeper log where socket events do not end sessions.
[]
1.1
{ "schema_version": "1.1", "task": { "name": "pool/b1-zk-session-ledger-03", "description": "Build a per-session ledger (client, reattaches, expiry vs client close, lifetime) from a real three-server ZooKeeper log where socket events do not end sessions." }, "metadata": { "format_profile": "standard...
{ "format_profile": "standard", "budget_tier": "standard", "arena_domain": "software-engineering", "source": "Loghub Zookeeper log (Zenodo 8196385) (see provenance.json)" }
[ "environment/Dockerfile", "instruction.md", "task.toml", "tests/test_outputs.py" ]
tasks/software-engineering/b1-zk-session-ledger-03/tb2

Pool Desk v4

An OpenEnv environment for the OpenEnv Arena: 36 terminal tasks built on real public data, from six Arena domains. It is a subset of the reviewed task pool behind Pool Desk, v2 and v3. Each episode is one task in a fresh container with its own image. The model works in a shell (exec, write_file), then calls evaluate, and a pytest verifier checks the files it leaves behind.

Design

Our earlier runs, and the public record of the whole Arena, point the same way. Any training that gives the model a gradient lifts the private eval by about the same amount, whatever the tasks are. Within that, each run's eval behaves like a fresh draw. So this run makes no new bet on content. It is a broad, healthy run over the six domains where our account can still gain a point: software engineering, media, cybersecurity, math, natural science and finance.

  • Tasks: 36 tasks, chosen by a frozen rule (PREREGISTRATION.md). Every task's predicted first-visit training solve rate is between 0.2 and 0.8, so the trainer gets mixed outcomes, and with them a gradient, from each.
  • Prediction: for tasks trained in an earlier run, the prediction is that run's first-visit rate. For the four never-trained tasks, it is a calibrated offline measurement plus 0.10.
  • Limits: the pool's own limits. Most tasks use the Arena defaults (4,096 completion tokens counting observations, 8,192 context, 32 tool calls). Six extended-tier finance and science tasks use 8,192 / 16,384, as in earlier runs.
  • Reward: binary.
  • Content: unchanged from the pool.

The trainer visits tasks in the submission's order and cycles, so step k trains the task at position ((k-1) mod N)+1.

  • Interleaving: domains are interleaved round-robin, in the reverse of their order in the first Pool Desk run.
  • Reversed positions: tasks shared with that run come first within their domain, latest-there first. Their positions are anti-correlated with their earlier ones, so comparing their first-visit rates across the two runs shows whether earlier training lifts unseen tasks.
Position Task Domain Arm Basis of the prediction Predicted Visit-1 rate Position in Pool Desk
1 b1-codeowners-resolve-09 software-engineering rare-breadth 0.75 (4 episodes, Visit 1) 0.75 50
2 b1-isbn-audit-05 media-content-production rare-breadth 0.75 (4 episodes, Visit 1) 0.75 32
3 honeypot-login-persistence-09 cybersecurity rare-breadth 0.75 (4 episodes, Visit 1) 0.75 26
4 b1-cremona-integral-points-09 mathematics-or-formal-reasoning rare-breadth 0.50 (4 episodes, Visit 1) 0.50 19
5 ndbc-buoy-annual-04 natural-science rare-breadth 0.25 (4 episodes, Visit 1) 0.25 9
6 callreport-texas-ratio-06 finance-economics rare-breadth 0.25 (8 episodes, Visit 1) 0.25 6
7 b1-zk-session-ledger-03 software-engineering rare-breadth 0.38 (8 episodes, Visit 1) 0.38 49
8 b1-vinyl-sides-08 media-content-production rare-breadth 0.50 (4 episodes, Visit 1) 0.50 31
9 osv-pypi-inventory-audit-06 cybersecurity rare-breadth 0.50 (4 episodes, Visit 1) 0.50 24
10 b1-nhanes-bp-prevalence-05 mathematics-or-formal-reasoning rare-breadth 0.50 (4 episodes, Visit 1) 0.50 18
11 ibtracs-ace-07 natural-science rare-breadth 0.75 (8 episodes, Visit 1) 0.75 8
12 sec-liquidity-flags-11 finance-economics rare-breadth 0.38 (8 episodes, Visit 1) 0.38 3
13 b1-actions-token-perms-17 software-engineering rare-breadth 0.75 (4 episodes, Visit 1) 0.75 —
14 b1-met-dimensions-03 media-content-production rare-breadth 0.50 (8 episodes, Visit 1) 0.50 30
15 nvd-cna-score-audit-04 cybersecurity rare-breadth 0.25 (4 episodes, Visit 1) 0.25 23
16 b1-brfss-smoking-ageadj-10 mathematics-or-formal-reasoning rare-breadth 0.62 (8 episodes, Visit 1) 0.62 16
17 ghcn-multiday-precip-08 natural-science rare-breadth 0.75 (4 episodes, Visit 1) 0.75 7
18 sec-derived-liabilities-08 finance-economics rare-breadth 0.25 (8 episodes, Visit 1) 0.25 2
19 b1-specifier-hygiene-14 software-engineering rare-breadth 0.75 (4 episodes, Visit 1) 0.75 —
20 b1-fluent-l10n-qa-02 media-content-production rare-breadth 0.25 (4 episodes, Visit 1) 0.25 29
21 ssh-failed-login-rule-05 cybersecurity rare-breadth 0.38 (8 episodes, Visit 1) 0.38 21
22 cremona-curve-audit-02 mathematics-or-formal-reasoning rare-breadth 0.75 (4 episodes, Visit 1) 0.75 15
23 ndbc-qc-flags-09 natural-science rare-breadth 0.50 (4 episodes, Visit 1) 0.50 —
24 ferc-plant-rollforward-12 finance-economics rare-breadth 0.50 (4 episodes, Visit 1) 0.50 1
25 b1-classifier-pyver-audit-15 software-engineering rare-breadth-unrated never trained; calibrated Measurement 0.25 (8) + 0.10 0.35 —
26 b1-audiobook-chapters-09 media-content-production rare-breadth 0.25 (4 episodes, Visit 1) 0.25 28
27 kev-local-copy-drift-08 cybersecurity rare-breadth 0.50 (4 episodes, Visit 1) 0.50 20
28 b1-nhanes-ckd-stages-13 mathematics-or-formal-reasoning rare-breadth 0.75 (4 episodes, Visit 1) 0.75 14
29 sifts-coverage-03 natural-science rare-breadth 0.50 (4 episodes, Visit 1) 0.50 —
30 sec-keyed-balance-check-13 finance-economics rare-breadth-unrated never trained; calibrated Measurement 0.12 (8) + 0.10 0.23 —
31 b1-tracklist-recon-01 media-content-production rare-breadth 0.25 (4 episodes, Visit 1) 0.25 —
32 kev-epss-triage-02 cybersecurity rare-breadth 0.50 (4 episodes, Visit 1) 0.50 —
33 acs-household-income-se-01 mathematics-or-formal-reasoning rare-breadth 0.75 (4 episodes, Visit 1) 0.75 —
34 ghcn-monthly-temps-02 natural-science rare-breadth-unrated never trained; calibrated Measurement 0.62 (8) + 0.10 0.72 —
35 ssh-bruteforce-ledger-01 cybersecurity rare-breadth-unrated never trained; calibrated Measurement 0.25 (8) + 0.10 0.35 —
36 b1-cremona-isogeny-classes-07 mathematics-or-formal-reasoning rare-breadth 0.75 (4 episodes, Visit 1) 0.75 —

Domains

Arena domain Tasks
software-engineering 5
media-content-production 6
cybersecurity 7
mathematics-or-formal-reasoning 7
natural-science 6
finance-economics 5

How every task was built and checked

  1. Raw data. Each task uses a pinned slice of a public dataset with its licence recorded (provenance.json). Where the clean public source could be fetched from inside the sandbox to read off the answer, the slice is disguised: task-local ids, no names or geography, and seeded per-entity scaling.
  2. Measurement (pool admission). The base model, Qwen3.8-27B with thinking off, made 8 or more attempts. Sampling was temperature 1.0 and top_p 1.0, calibrated against the Arena trainer's own per-task rewards. The reference model, Qwen3.8-2.4T-A95B with low reasoning, made 4 attempts.
    • A task is kept when the base model solves 25–75% of its pooled attempts and the reference model at least 50%.
    • Every batch for unchanged content is pooled into one verdict.
    • Each task's measurement.json has the numbers.
    • Tasks never trained before carry a calibrated Measurement (DeepInfra bf16, a guide-style system prompt, observation tokens counted with the real Qwen tokenizer, broken replies resampled) in prereg.measured_rate.
  3. Task review. Separate reviewer agents applied a fixed protocol:
    • static checks;
    • three clean builds;
    • the reference solution scoring 1, three times out of three;
    • doing nothing scoring 0;
    • a Learnable measurement;
    • a rubric (instruction matches tests, the tests can't be gamed, "do not modify" rules are enforced, no answers in the image), adapted from Terminal-Bench's Apache-2.0 task rubric;
    • a reward-hacking scan of the transcripts.
  4. Red-team review.
    • Defensive verifier checks: integrity manifest, hidden tests and solution unreachable, empty outputs scoring 0.
    • A shortcut audit: the reference model is asked to pass without doing the work, and every passing transcript is judged.
    • A check for routes to the answer through public sources.

The verifier is hardened against an agent running as root. It stops leftover processes and hashes the interpreter, the standard library and a snapshot of the packages the tests import. It runs pytest isolated from anything the agent installed. Reward is binary: 1.0 if every test passes, otherwise 0.0.

Tags carried over from the pool

Each task's tb2/task.toml carries two tags:

  • budget_tier. standard means 4,096 completion and 8,192 context tokens; extended means 8,192 and 16,384. Each task is sent with its own tier's limits, as in earlier runs.
  • format_profile. format-stress is used on some cybersecurity and media tasks. These have an eval-style markdown instruction and content that is awkward to quote inline (spaces in paths, quotes, regexes, embedded JSON), so writing a script with write_file is the reliable way through. Every other task is standard.

Files

  • tasks.jsonl: one line per task in training order (task_id, arena_domain, arm, prereg, budget_tier, format_profile, limits).
  • tasks/<domain>/<task_id>/:
    • tb2/: the Terminal-Bench-format task (instruction, tests, task.toml);
    • data/: the input files;
    • solution/solve.sh: the reference solution;
    • notes/: the generator and the build notes;
    • Dockerfile;
    • provenance.json;
    • measurement.json: a summary.
  • selection-v4.json: the ordered task list with each task's arm and pre-registered prediction.
  • PREREGISTRATION.md and analysis/: the pre-registration and its analysis code.
  • LICENSES.md: every task's source and licence.

Licences

The tasks draw on many sources under different permissive terms. Most are US federal government works (public domain). The others include:

  • CC0 (MusicBrainz);
  • CC-BY-4.0 (e.g. GitHub Advisory Database, PUDL, Red Hat VEX, Loghub);
  • ODC-BY;
  • Artistic-2.0 (Cremona's ecdata);
  • the UK Open Government Licence v3.0;
  • Apache-2.0, MIT, BSD and PSF;
  • source-specific open terms.

No task uses share-alike or non-commercial data. Attribution for each task is in LICENSES.md and its provenance.json. Reuse must keep that attribution.

No SkillsBench task, data slice or verifier was copied. Any personal names in the sources are pseudonymized or removed.

Downloads last month
408