DEDUPED Hot AI repos, turned into use cases Get the Monday 5

How to check a LIBERO evaluation manifest before spending compute with Open ETA

Confirm a parallel-evaluation manifest is well formed without calling a model or MCP service.

  • Top pick
  • Research
  • Intermediate
  • 15 minutes
  • From the README
  • Any agent

Who it is forA robotics researcher preparing a LIBERO benchmark run who wants to catch manifest errors before any model calls or simulator time.

The problemA bad manifest can waste a long parallel run, and it is hard to tell whether the file is valid without starting the agent stack.

The outcomeThe manifest passes validation, so the researcher knows the episode list is usable before connecting a Planner.

What you need first

  • Python 3.10 or newer and uv installed
  • An OpenAI-compatible Planner LLM or VLM endpoint for any run that reasons over a task
  • One simulator backend installed through scripts/setup_envs.sh, such as libero

Steps

  1. Run uv sync --extra dev in the Open ETA repository folder.
  2. Run uv run openeta-batch --manifest examples/parallel_libero_eval.json --validate-only. (inferred, check the README)
  3. Read the validation output and fix any reported manifest problem before the next step.

Prompt for your agent

Use the OpenETA repo to validate the manifest at <manifest path> with `uv run openeta-batch --manifest <manifest path> --validate-only`. Report whether validation passed and list any errors, without connecting to a model or MCP service.

Caveat. The README says validation runs without a model or MCP service, so it confirms the manifest only and does not show that any task succeeds.

Use this in your AI agent

Ask your agent

Using the Deduped MCP, get the setup steps for OpenMOSS/OpenETA and "Check a LIBERO evaluation manifest before spending compute"

Add Deduped to Claude Code once

claude mcp add --transport http deduped https://dedupedai.com/mcp

Cursor, ChatGPT, others

Share: X LinkedIn Hacker News Email Copy link

Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer