Report · marked 8 Oct 2026

ruvnet/RuView

Solid foundations, held back in a few specific places.

Rust · 96,927 stars · 3,635 files · branch main

82 /100 A-

Instructions 27/27Whether the repo tells an agent how to behave before it starts guessing. Full marks.Setup 11/20Whether an agent can install the project and get it running without a human. Losing marks on deterministic install and environment config.Verification loop 22/22Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Full marks.Context economy 11/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context and repository weight.Navigability 10/10How quickly anything new can orient itself. Full marks.

Higher is better. Accent marks what is costing you most.

Fix these first

File sizes fit in context

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

Deterministic install

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

Repository weight

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

The full marking

Every deduction below names the file or setting it came from.

Instructions 27/27 A+

Whether the repo tells an agent how to behave before it starts guessing.

✓Agent instruction file 12/12

AGENTS.md is present, which is the format the most tools read.

Also found: CLAUDE.md

✓Instruction quality 12/12

Specific enough that an agent can act on it.

7,928 characters, a workable length

names the actual commands to run

uses headings, so an agent can skim it

includes copyable code blocks

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 11/20 B-

Whether an agent can install the project and get it running without a human.

✗Deterministic install 3/6

Only requirements.txt, which pins loosely at best.

Commit the lockfile your package manager generates. Without it, an agent's install and your install are different builds, and 'works on my machine' becomes unfalsifiable.

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

Makefile

pyproject.toml scripts

scripts/ directory

✗Environment config 2/4

Env vars are mentioned in the README but there's no example file to copy.

Add a .env.example listing every variable with a safe placeholder value. It's the cheapest possible fix and it unblocks the whole first run.

✗Pinned runtime version 0/2

No pinned runtime version.

Add a .nvmrc, .python-version, or equivalent so the agent's toolchain matches yours.

✗Reproducible environment 0/2

No container or devcontainer definition.

A Dockerfile or devcontainer removes an entire class of 'it won't install' failures.

Verification loop 22/22 A+

Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy.

✓Tests exist 8/8

401 test files against 1998 source files.

e.g. aether-arena/calibration/test_calibration.py, aether-arena/calibration/test_cog_calibration.py, archive/v1/scripts/test_api_endpoints.py

✓Test command is discoverable 7/7

An agent can find and run `make test`.

✓Continuous integration 4/4

36 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

pyproject.toml encodes the house style.

–Static type checking n/a

Not applicable — the Rust compiler type checks every build.

Context economy 11/20 B-

Whether the repo fits in a context window, or fights it.

✓No committed build output 6/6

No generated directories committed.

✓.gitignore hygiene 3/3

.gitignore covers 156 patterns.

✗File sizes fit in context 0/6

3 source files are over 100KB.

A single file that fills the context window forces an agent to work from fragments, and it will confidently edit code it never saw. Splitting the worst offenders pays for itself immediately.

v2/crates/wifi-densepose-desktop/ui/.vite/deps/react-dom_client.js — 911KB

v2/crates/wifi-densepose-sensing-server/src/main.rs — 702KB

v2/crates/wifi-densepose-desktop/ui/src/pages/EdgeModules.tsx — 101KB

✗Repository weight 2/5

About 422MB checked out. Large enough that cloning and searching are both slow.

Large binaries and vendored trees slow every operation an agent performs. Git LFS or a separate assets repo keeps the working tree navigable.

Here is your AGENTS.md

Drafted from what is actually in this repository: the install command from your lockfile, the commands you already declare, your real directory layout. Anything marked TODO needs a person. Save it at the root as AGENTS.md.

AGENTS.md — drafted for ruvnet/RuView

# AGENTS.md

π RuView turns commodity WiFi signals into real-time spatial intelligence, vital sign monitoring, and presence detection — all without a single pixel of video.

## Setup

```
pip install -r requirements.txt
```

## Commands

```
make install
make install-verify
make install-python
make install-rust
make install-browser
make install-docker
```

## Layout

- `v2/`       992 source files
- `ui/`       195 source files
- `harness/`  131 source files
- `archive/`  119 source files
- `firmware/` 118 source files
- `scripts/`  112 source files

## Conventions

- Tests live alongside the code they cover, following `aether-arena/calibration/test_calibration.py`.
- CI defines what passing means. See `.github/workflows/aether-arena-harness.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `v2/crates/wifi-densepose-desktop/ui/.vite/deps/react-dom_client.js` is 911KB. It will not fit comfortably in context, so read it in parts.
- No lockfile is committed, so an install here may not match what CI produced.

---

Drafted by agentreadme.com from what is in this repository. Everything marked TODO
needs a human. Check it in as AGENTS.md at the root.

Open the raw markdown or curl -o AGENTS.md agentreadme.com/draft/ruvnet/RuView.md

A draft gets the commands right and stops at the things only a maintainer knows. What a good Rust AGENTS.md looks like covers what to add by hand, and what AGENTS.md is explains the format itself.

Show the mark

The badge re-checks daily, so it keeps up as the repository changes. Use mark again to force it now.

[![agent ready](https://agentreadme.com/badge/ruvnet/RuView.svg)](https://agentreadme.com/ruvnet/RuView)

Other Rust repositories, marked

ultraworkers/claw-code 71 B+ clash-verge-rev/clash-verge-rev 91 A farion1231/cc-switch 63 B openai/codex 61 B- rustdesk/rustdesk 72 B+ rust-lang/rust 65 B

All Rust repositories

Think this mark is wrong?

Every deduction above names the file it came from, so this can be settled by looking. If a check missed something, that is a rule worth fixing.

Open an issue, already filled in