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

How to confirm the scenario catalog is intact before scoring with Doc2 Harness

Verify that the catalog loads and contains 94 scenarios before any scoring run.

Who it is forA developer or maintainer who has edited the repo or wants to confirm a clean copy before trusting scores.

The problemAn edited or inconsistent catalog could silently score a different set of scenarios, which would make results misleading.

The outcomeA printed count of 94 when the catalog is intact, or an error if the digests fail to verify.

What you need first

  • Python 3.11 or newer
  • Docker installed and running
  • The repo cloned locally
  • For building a new harness only: the builder image, a local LiteLLM gateway, and your own API key

Steps

  1. Clone or open the repo and change into its root directory.
  2. Run PYTHONPATH=src python3 -c "from doc2harness.benchmark.dispatch import active_scenario_ids as a; print(len(a()))".
  3. Check that the printed output is 94.
  4. If the command fails, do not score with this copy until the catalog is restored.

Prompt for your agent

In the repo YuyaoGe/doc2harness, run the Python sanity check that imports active_scenario_ids and prints its length. Report the printed number and any digest error. Verify that the output is exactly 94 before reporting the catalog as intact.

Caveat. The check only confirms the 94-scenario released subset, not the 328-case full suite behind the leaderboard.

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