DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to submit a new case or skill to the benchmark with Harness Eval W

Draft a new world, action, or probe case, or a new evaluation skill, in the existing benchmark format for submission.

  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forA researcher who has found a physics or causality failure the public set does not test and wants to contribute it.

The problemExisting cases may not cover a useful kind of world model failure, and there is no shared place to propose one.

The outcomeA submission draft in the existing benchmark format, sent through the contribution page.

What you need first

  • Git and conda installed
  • Ability to create three conda environments from the files in docs/installation
  • Credentials and paths filled into harnesseval.env, copied from config/example.env
  • Generated results in the layout used by runs/example/results_example, or use the bundled demo

Steps

  1. Open the [Contribute page](https://mirros-lab.github.io/HarnessEval-W/contribute.html).
  2. Decide whether you are submitting a new case (new world, action, or probe family) or a new skill (a new kind of evaluation).
  3. Read the bundled benchmark files in the repo and match your submission to the existing format.
  4. Write down the world, action, or probe intent and the evidence each sub-question needs.
  5. Submit through the contribute page.

Prompt for your agent

Read the HarnessEval-W repo and its public benchmark format, then draft a new <case or skill> for <the failure you want to test>. Expect a written draft with the world, action, probe intent, and sub-questions in the existing format. Check that the draft matches the format of the bundled examples before submitting it on the contribute page.

Caveat. The README does not describe the exact submission template, so you need to read the bundled files to match the format.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page