AntFleet

Disagreement · 3c2fcd11-anthropic-1

Install one-liner `./aeon` is not a documented entry point for aeon-bench

solo Opus
repo 6f7fc663·PR #9·reviewed 1 week ago

Opus finding

Install one-liner `./aeon` is not a documented entry point for aeon-bench

mediumdocs-gapmedium
  • skills/show-hn-draft/SKILL.md:84-85
  • skills/show-hn-draft/SKILL.md:141
The skill tells the operator to paste a public install command `./aeon` that assumes a top-level executable script named `aeon`. The repo under review (aeon-bench) ships an `aeon.yml` config but there is no evidence of an `./aeon` launcher or `./scripts/skill-runs` script in the inspected files. If those scripts do not exist in this fork, the launch post will instruct readers to run a non-existent command, and the operator launch checklist references a non-existent script. This is a deceptive doc/instruction that will produce a broken public-facing post.

Recommendation

Either confirm `./aeon` and `./scripts/skill-runs` exist in this repo (and adjust the path if not), or replace the install one-liner with a verified setup command for aeon-bench (e.g., the actual onboarding instructions in README), and update the checklist to reference a script that exists.

Other reviewer

The other reviewer flagged nothing in this file/line range.

Why this didn't post

This finding didn't meet AntFleet's unanimous agreement threshold. Both frontier models review every PR independently; only findings they both flag with the same severity and category are posted to the PR. This one fell through.

read the methodology →

From the same review

These findings passed the unanimous gate on the same PR review. The disagreement above was filtered out; the findings below were posted.