agentreadme

Report · marked 26 Aug 2026

calcom/cal.diy

Solid foundations, held back in a few specific places.

TypeScript · 47,926 stars · 7,702 files · branch main

Fix these first

01
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.
02
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.
03
Static type checking
A type checker gives an agent an error message instead of a runtime surprise. It's the second-fastest feedback loop after the compiler.

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.
9,222 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 18/20 A

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

Deterministic install 6/6
yarn.lock pins the dependency tree.
Found yarn.lock
Discoverable commands 6/6
Commands are declared where an agent will look for them.
package.json scripts (app-store-cli, app-store:build, app-store:watch, app-store, create-app, edit-app…)
scripts/ directory
Environment config 4/4
.env.example documents what the app needs to 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 20/25 A-

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

Tests exist 6/8
576 test files against 5067 source files.
e.g. __checks__/csp-login.spec.ts, apps/api/v2/src/app.e2e-spec.ts, apps/api/v2/src/lib/inputs/capitalize-timezone.spec.ts
Test command is discoverable 7/7
An agent can find and run `npm run test`.
Continuous integration 4/4
50 GitHub Actions workflows define what "passing" means.
Lint and format rules 3/3
biome.json encodes the house style.
Static type checking 0/3
No static type checking.
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 9/20 C

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 70 patterns.
File sizes fit in context 0/6
6 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.
.yarn/releases/yarn-4.12.0.cjs — 2923KB
packages/features/bookings/lib/handleNewBooking/test/reschedule.test.ts — 124KB
apps/api/v2/src/platform/event-types/event-types_2024_06_14/controllers/event-types.controller.e2e-spec.ts — 123KB
Repository weight 0/5
About 1147MB 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 calcom/cal.diy
# AGENTS.md

Scheduling infrastructure for absolutely everyone.

## Setup

```
yarn install
```

## Commands

```
yarn dev               # run locally
yarn start             # run the app
yarn build             # produce a build
yarn test              # run the test suite, must pass before any commit
yarn lint              # lint
yarn format            # format
yarn app-store-cli
yarn app-store:build
```

## Layout

- `packages/`     3404 source files
- `apps/`         1624 source files
- `scripts/`      20 source files
- `example-apps/` 7 source files
- `__checks__/`   3 source files
- `deploy/`       2 source files

## Conventions

- Tests live alongside the code they cover, following `__checks__/csp-login.spec.ts`.
- CI defines what passing means. See `.github/workflows/all-checks.yml`, and keep it green.
- TODO: add the two or three conventions a newcomer always gets wrong here.

## Gotchas

- `.yarn/releases/yarn-4.12.0.cjs` is 2923KB. It will not fit comfortably in context, so read it in parts.
- Copy `.env.example` before running anything that needs configuration.

---

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/calcom/cal.diy.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 80 out of 100

[![agent ready](https://agentreadme.com/badge/calcom/cal.diy.svg)](https://agentreadme.com/calcom/cal.diy)

Other TypeScript repositories, marked

freeCodeCamp/freeCodeCamp 69 B openclaw/openclaw 68 B nilbuild/developer-roadmap 45 C vuejs/vue 67 B n8n-io/n8n 87 A anomalyco/opencode 80 A-

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