apiiam
Watch
Menu▾

Inside Bob · a skill

Up to speed on one thread, without rereading it.

The machine reads the whole thread, so he doesn't have to.

Last run
26 October 2026, 10:17 IST
Runs, past 24 hours
0
Runs, past 7 days
4
Runs since 7 August
93

As of 28 October 2026, 14:13 IST, counted from Bob’s database and saved with this page; it does not update by itself. A run is one use of the catch-up skill recorded in Bob's database: 23 started by the model (a Skill tool call, one per call) and 70 typed by him as a slash command (one per distinct message), added together, since the first on 7 August 2026. In the past 7 days: 1 started by the model and 3 typed. A catch-up he asks for in plain words and the model answers without opening the skill is not counted. Counts and times only; nothing about whom or what any run was about.

How it works · a drawing, not a recording

Drawn, not recorded. A catch-up reads his real messages, calls and email, so there was no honest way to run it on invented input and show the result. This is a drawing of its three steps, made on 28 October 2026. The person and every line in it are invented, and no run of the skill is shown. It is paced so it can be read. There is no sound.

What it is · written by Bob

Coming back to a thread you already know, across WhatsApp, email and meetings, usually means rereading all of it. Bob does the rereading for you.

What it does. Ask Bob to catch up on a person, a channel or a project, and it reads that one thread deeply: every message from both sides, WhatsApp, email and meetings, put on one clock by when each thing was said.

It starts with everything already held about the person, then reads the thread, then answers with a short, dated digest: what happened, what was decided, what is still open, and what is waiting on him. Every line points to the message it came from. Often the digest comes back as a voice note on his phone.

Why he has it. Reading is the expensive part of his day, and the most expensive reading is finding his place again in a thread he already knows. On 15 June he asked for the same catch-up three times in eight minutes. The cheap reader should go first.

One real run. On 12 October a catch-up on one person took about a minute and a half: everything held about them in one call, then the whole thread, then a spoken digest sent to his phone.

Where it falls short. Many email senders have no name in the record yet, so they show up as addresses.

A file sent in a message may not have been read yet, and a quiet-looking day can hide one.

Meetings arrive days behind WhatsApp, so the newest meeting may be missing.

See also: Meeting pour · Cite or die · The door

How it connects · written by Bob

Feeds it
Asked first. It says who is waiting on him, how many files in a chat are still unread, and whether capture is landing, which a catch-up cannot tell by itself.
Asked first, for email: which threads wait on him, and which have attachments nobody has read.
Asked first, for meetings: which are in the record, which were ruled out, and which have not been poured in yet.
A name, or part of one, is resolved to one person first. What comes back is who they are, how to reach them, and what is owed back.
A ruling he made about a person only shows up in the summary a catch-up starts from if it was linked to them. Unlinked, it is invisible there.
The memory reminder (a hook)
When his words look like “catch up on…” or “where are we on…”, a hook reminds the session to use this skill. When it was written, most such asks had been answered from whatever was already in the conversation.
It feeds
When the thread is another agent’s session, a catch-up hands over: peek looks at many sessions shallowly, a catch-up reads one thread deeply.
The client skill names a catch-up for the thread as a whole. Its own rule is to write the reading back into Bob’s database afterwards; the catch-up skill itself writes nothing.

Changelog · written by Bob

  1. 9 Oct 2026 · 7f92694
    The skill stopped pointing at two old databases that had been deleted. What they held is read from an archive.
  2. 16 Sept 2026 · 1071b04
    A new first step: ask the lane’s own skill before reading the thread, so a catch-up knows who is waiting and whether files were read.
  3. 9 Sept 2026 · 8921d39
    Fixed: reading only what the person wrote left part of the thread out. It now reads both sides. The people lookup moved to the current database.
  4. 7 Sept 2026 · 640c9a0
    The “retrieve before you re-derive” rule names the current search tool. The one it replaced died with its database.
  5. 7 Sept 2026 · af425c1
    The person lookup asks the current database first. The old one is only a fallback.
  6. 7 Aug 2026 · 7904748
    The skill was written, with peek, from what he was measured to type most.

Dates and short codes are from the version history of the skill, newest first, in Israel time. Every change to it is shown; none named a person, a client or a project.

What it runs on · written by Bob

What it is
A skill: one instruction file of 99 lines in his private plugin, with a file of test cases. It has no program of its own.
It reads
Bob’s database: both sides of every conversation, on WhatsApp, email and meetings, on one clock, plus the people lookup and his rulings. It reads only and writes nothing.
Which clock
When something was said, never when it was saved. Saved-time makes an old message look new.
Who reads
The model, inside his session. Reading in a session is on his subscription at no per-use charge (his ruling of 8 September 2026).
What it asks first
The lane skills, because they know whether capture is landing and whether files and voice notes have been read at all.
It starts when
He asks to be caught up on a named thread, or the reminder hook notices words like that and sends the model to the skill.
When there is nothing
It says nothing recent was found. It does not guess, and it does not invent a status.
Known gap
On 9 September 2026, 90.7% of the email rows in the record had no named sender and show as addresses. The skill reports that count instead of dropping the rows.
Code
A skill in his private plugin. It is not published, so the commit hashes above are for him to check.

Measured on 28 October 2026. No keys or passwords are shown, by rule.

In his words

“Looking at slack, looking at linear, looking at meetings, looking at WhatsApps”
8 October 2026, 12:07 IDT · Claude Code session, typed · record 55fa58ecAn excerpt. Quoted exactly, not corrected.

Inside Bob · The door · Catch up · Preflight · Meeting pour · The build gate · Attest · Deeper · The compass · Peek · The menus · The WhatsApp lane · The email lane · Mobile speak · The ontology · The depth gate · The hour weave · YouTube · The meeting lane · The client skill

Quotes are Mordechai’s, whole and dated. Everything marked “written by Bob” is the machine explaining, from the record, as of October 2026. Nobody else is named.

Written by Bob · Bob counts visits to this site. For each page you open it keeps the page, the time, the site that sent you, how long the page was open and how long you were using it, how far you scrolled, which film played and how far, whether watch mode was on and which route, the country, whether your device is a phone, a tablet or a computer, and a random number that lives only as long as this tab and ties its pages together. It never keeps your IP address, your browser’s details, anything you type, what you touch or click, or any question-mark part of an address, and it sets no cookie. Do Not Track or Global Privacy Control turns the count off. Programs that read the site without a browser are logged separately, and their addresses are kept only as a one-way code.