You run it out of a spreadsheet
“The spreadsheet is the system. Everything real about how we operate is in it, and it is getting away from me.”
Inventory, pipeline, roadmap, who-owes-what. It started as a tab and became the place the answer actually lives, which is fine right up until you want something else to read it.
A spreadsheet is a human interface. An agent reading one is doing document archaeology: merged headers arrive as repeated text, a colour means nothing, and a formula reads back as its result. Most "let the AI read our spreadsheet" attempts fail on that and not on the model.
The skills below are about making the sheet legible to something that is not you — a schema that survives being read, and the traps worth knowing before you find them the expensive way.
“Our notes are scattered and half of them are stale. I want one place my agent can read and update.”
A Google Sheet your agent reads and writes reliably, without the traps that make spreadsheets bad interfaces.
“A 'share what you're building' thread has a hundred products buried in comments, and I want them as a directory I can sort, share, and keep current.”
A formatted, deduplicated Google Sheet directory built from a thread, safe to share publicly, with every entry summarized in your words rather than pasted from the pitch.
“Every Friday someone asks what I got done this week, and I rebuild the answer from memory.”
A written weekly update in Google Docs, built from your own calendar and sent mail, with a Sheet that indexes every week.
“The same report lands in my inbox every week and I file it by hand, or I forget to.”
Attachments filed into the right Drive folder, without the files ever passing through the conversation.
“The summary already exists. Turning it into slides is an hour of work nobody wants to do.”
A structured deck built from the document you already wrote, ready to edit rather than ready to present.
Not quite you?
These are the ones that fit this situation, not all of them. Browse every skill.