Tycho de Valk

I updated one of my Agent Skills today and realized I had no way to tell my other machines they were running a stale copy. Skills install as loose folders in ~/.claude/skills/ (or wherever your agent puts them). There’s no npm outdated, no brew upgrade, no update daemon. The skill just runs whatever’s on disk. So I added a small pattern that makes each skill check itself on invocation. If it’s out of date, the skill offers to install the update before continuing.

When Cloudflare launched EmDash CMS on April 1st, the reactions came fast — from Matt Mullenweg himself, from Hendrik Luehrsen at Kraut.press, and from Brian Coords. Each piece approached EmDash differently, but together they crystallized something I’ve been thinking about for years: WordPress’s deepest technical problems aren’t at the surface. They’re architectural. And the WordPress project keeps treating them as cosmetic.

AI will confidently sign off on anything. The question is whether you will too. I’m a member of my old high school’s “AI council”. My kids go there now, so I have both my own experience and my kids’ to build on when I speak in that council. Recently they asked me to speak to a group of teachers there about AI, as they’re trying to help teachers navigate what AI means for schools. The subject they asked me to speak about was a logical choice for me: the implications of AI on the workforce.