AI Skills became a standard. Memory moved onto files. Every called the promotion. A new paper explains why reliability feels hard.
 ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏ ‌​‍‎‏
Learned Context iconLearned Context
The Curation
Editorial illustration
Saturday Curation

Same file. Claude, ChatGPT, Cursor, GitHub.

Sun 19 Apr 2026 · 5 items

AI Skills became a shared standard, memory moved onto your files, and the job got renamed.


01tool

Agent Skills become an open standard

Anthropic published Agent Skills as an open standard this fortnight. Microsoft, OpenAI, Atlassian, Figma, Cursor, and GitHub all agreed to use the same file format. The practical effect: the skill you write once to capture your voice or your reasoning now runs on Claude, ChatGPT, Cursor, Copilot, and the others. The AI tool you pick stops being a lock-in.

Anthropic
02tool

Claude Opus 4.7 quietly moves memory onto your files

Anthropic released Claude Opus 4.7 on 16 April. The headline features got the coverage. The quieter line is doing more work: Claude is now measurably better at writing notes to files and reading them back later. Anthropic also removed several controls that used to live inside the model. Direction of travel: fewer knobs on the AI, more weight on the files around it.

Anthropic
03read

You're the manager now

Laura Entis for Every this week: 'As you climb the frame hierarchy, your role is less about communicating the mechanics of a problem and more about defining what the most important problem even is.' She is writing for developers. The argument generalises. Most professionals have quietly been promoted to managing AI, not using it. The job is briefs, reviews, holding standards. The promotion came with no training manual.

Every.to
04read

AI picks the wrong skill about half the time

Researchers benchmarked 34,000 AI skills running in real conditions on Claude, Cursor, and Codex. Two numbers to sit with. Pass rates dropped from 55% to 38% once the AI had to pick the right skill from a large library. Even when the right skill was available, the AI loaded it only 49% of the time. Reliability is a selection problem. More skills is not the answer.

arxiv, 34,000-skill benchmark
05observation

The discipline is getting named: context engineering

Two production AI teams published post-mortems this fortnight. Manus, on running agents at scale, and Microsoft's Azure site reliability team. Both arrived at the same sentence, almost verbatim: 'we realised we were building a context engineering system that happens to do X.' The pattern is now named. The practitioners calling it this are not selling it to you. They are reporting what actually produced the result.

Manus + Microsoft Azure

Missed this week's essay? I Built a Paul Graham AI Profile

Want to build a system where your AI actually knows how you work?

Take the audit

Learned Context

Context engineering for professionals

Website·LinkedIn·X·Forward to a colleague

Unsubscribe