A Skill Is Only Real When You Need It

Latest

Accept All is a magazine, a radar and a diary about artificial intelligence and the craft of code — read from Tokyo, for people who build.

The name is the button. Code is written by agents now and reviewed by a human thumb that hovers over Accept all a hundred times a day; the whole question of this decade is what, exactly, you just accepted. So we read the diff. A magazine, because every week one model, one tool or one idea is worth reading about slowly. A radar, because we count what the labs, the Valley, GitHub and the chip makers are talking about — releases, agents, open weights, compute, funding, rules — and show it as it moves. A diary, because a seal is set each day in that day's colour, and the days add up.

We read the research labs' own posts, the American and European tech press, the Japanese and Chinese developer sites and the newsletters people actually forward, and bring it together in English and Japanese. Everything here links back to the people who wrote it; the images belong to their authors.

Accept All will keep changing. New sources, new signals, new ways of looking — a little better each week, never finished. If something here made you open a terminal, that is enough.

Thank you for reading. ありがとうございます。

A Skill Is Only Real When You Need It

September 7, 2026Yuki Halvorsen

At 1:14 a.m. the terminal in Nakameguro is the only light on, and the agent I'm running has just asked me, politely, to explain three separate deployment procedures it does not need tonight — because I put all three in its system prompt, the way you'd hand someone the entire manual before they've touched the machine.

The fix is a file, nothing more: a folder called skills, one markdown document inside it with a short description at the top and the actual instructions below. The agent reads only the descriptions until one of them matches what it's doing — deploy, migrate, review — and only then does it open the file and load the rest. It is the oldest idea in computing, lazy evaluation, wearing a new coat, and it means a context window that used to fill up with instructions for jobs I wasn't doing now stays empty until I ask for the job I am.

Google shipped roughly the same mechanism into Genkit's Go agents this week, calling it progressive disclosure, which is a better name than mine. The interesting part isn't the loading — any cache can do that — it's the writing. A skill only fires if its one-line description is honest about what it actually does; write it too broad and it loads for everything, too narrow and it never loads at all. I spent longer on that single sentence for my deploy skill than on the deployment script itself.

This is the part of the job nobody puts in the demo: not the model, not the framework, just deciding what deserves to be in the room before it's asked for. Stockholm taught me that every dependency you add is a promise you have to keep at 3 a.m.; Tokyo is teaching me that every instruction you load unasked is a tax someone else pays without knowing it.

By 1:40 the deploy finishes clean, the skill file closes itself back to a single line on disk, and the terminal goes back to being mostly cursor, blinking over nothing, waiting to be told what it doesn't know yet.

Yuki Halvorsen was born in Sapporo to a Norwegian father and a Japanese mother, wrote her first program on a school computer that took ten seconds to draw a circle, and spent eight years as an engineer in Stockholm before Tokyo pulled her back. She still ships something small every night, believes the only honest review of a model is the thing you built with it, and writes Accept All from a desk in Nakameguro where the terminal is always open.