Report · marked 25 Aug 2026

Graphify-Labs/graphify

Solid foundations, held back in a few specific places.

Python · 110,450 stars · 838 files · branch v8

83 /100 A-

Instructions 21/27Whether the repo tells an agent how to behave before it starts guessing. Losing marks on instruction quality.Setup 16/20Whether an agent can install the project and get it running without a human. Losing marks on environment config and pinned runtime version.Verification loop 24/25Whether an agent can check its own work. This is the category that most decides whether agent output is trustworthy. Losing marks on static type checking.Context economy 14/20Whether the repo fits in a context window, or fights it. Losing marks on file sizes fit in context.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.

Instruction quality

Worth fixing: it never states a build, test, or run command; has no code blocks.

Environment config

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.

The full marking

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

Instructions 21/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.

✗Instruction quality 6/12

Real instructions, with gaps.

Worth fixing: it never states a build, test, or run command; has no code blocks.

410 characters, a workable length

uses headings, so an agent can skim it

✓README as an entry point 3/3

README has a clear getting-started section.

Setup 16/20 A-

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

✓Deterministic install 6/6

uv.lock pins the dependency tree.

Found uv.lock

✓Discoverable commands 6/6

Commands are declared where an agent will look for them.

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 2/2

dockerfile gives a known-good environment.

Verification loop 24/25 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

376 test files against 400 source files.

e.g. docs/superpowers/specs/2026-05-04-incremental-updates-dedup-design.md, graphify/skills/agents/references/extraction-spec.md, graphify/skills/amp/references/extraction-spec.md

✓Test command is discoverable 7/7

An agent can find and run `pytest`.

✓Continuous integration 4/4

3 GitHub Actions workflows define what "passing" means.

✓Lint and format rules 3/3

pyproject.toml encodes the house style.

✗Static type checking 2/3

Type checking is configured, but not in strict mode.

A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

Context economy 14/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 34 patterns.

✗File sizes fit in context 0/6

12 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.

graphify/extract.py — 326KB

graphify/extractors/engine.py — 311KB

graphify/cli.py — 215KB

✓Repository weight 5/5

About 11.3MB checked out, which is comfortable.

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 Graphify-Labs/graphify

# AGENTS.md

Turn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.

## Setup

```
uv sync
```

## Commands

```
pytest         # run the test suite
ruff check .   # lint
```

## Layout

- `tests/`    297 source files
- `graphify/` 84 source files
- `worked/`   14 source files
- `tools/`    4 source files
- `scripts/`  1 source file

## Conventions

- Tests live alongside the code they cover, following `docs/superpowers/specs/2026-05-04-incremental-updates-dedup-design.md`.
- CI defines what passing means. See `.github/workflows/ci.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `graphify/extract.py` is 326KB. It will not fit comfortably in context, so read it in parts.

---

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/Graphify-Labs/graphify.md

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/Graphify-Labs/graphify.svg)](https://agentreadme.com/Graphify-Labs/graphify)

Other Python repositories, marked

vinta/awesome-python 81 A- NousResearch/hermes-agent 84 A- TheAlgorithms/Python 66 B yt-dlp/yt-dlp 54 C+ Significant-Gravitas/AutoGPT 63 B microsoft/markitdown 46 C

All Python 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