The name is the button.

An agent writes the code now, and a human thumb hovers over Accept all a hundred times a day. The honest question of this decade is what, exactly, you just accepted. So I read the diff.

Eight years as a backend engineer in Stockholm, back in Tokyo since 2023, and I still ship something small most nights, usually badly. My one rule: the only real review of a model is the thing you built with it. That is why there is no leaderboard on this site.

Around two hundred sources come through — the labs' own posts, the papers, the tools, the runtimes and languages nobody is watching yet, the chip under the demo, and the newsletters people actually forward. What is moving gets counted so the week reads at a glance, and every few days I explain one mechanism in plain words.

A story here is a headline, a short excerpt, one image and the link to whoever wrote it. We never reproduce the post; the images belong to their authors. A post written in Japanese appears in Japanese, exactly as it was published, and the link goes to the original.

— Yuki Halvorsen, Tokyo

← Accept All Archive

Phil SchmidVoices

8 Tips for Writing Agent Skills

04.13

8 Tips for Writing Agent Skills. Know What a Skill Is, Nail the Description, Write Instructions, Keep It Lean, Set the Right Level of Freedom, Don't Skip Negative Cases, Test It Before You Ship It…

Agents & vibe coding MCP, skills & tools

Read at Phil Schmid ↗

One letter a week, starting soon.

Latest

8 Tips for Writing Agent Skills

Related

VoicesPractical Guide to Evaluating and Testing Agent Skills Phil Schmid

VoicesEvals Skills for Coding Agents Hamel Husain

VoicesHow to use Gemma 4 with the Gemini API and Google AI Studio Phil Schmid

VoicesHow Kimi, Cursor, and Chroma Train Agentic Models with RL Phil Schmid

VoicesCombine Built-in Tools and Function Calling in the Gemini Interactions API Phil Schmid

VoicesDeveloper Guide: Nano Banana 2 with the Gemini Interactions API Phil Schmid