THE PERSISTENCE LAYER: SKILLS, MEMORY, OR STATE — YOU CAN'T BUILD ALL THREE THIS WEEK

1. Addy Osmani publishes “Agent Skills” — at the action layer

His “Agent Skills” essay landed on Hacker News today: a clean argument that composable skills, not models, are the durable unit in agentic systems. From the engineer behind a decade of frontend-performance canon, this is the canonical skills-over-prompts writeup the ecosystem needed. Skills are now arriving from both ends — indie portability tools above the vendor layer, and platform-owned catalogs below.

If you're picking one persistence layer to build first, skills are the highest-leverage choice — they compose across whatever model you switch to next quarter. Source

2. An indie ships a memory layer because their agent kept asking the same questions — at the knowledge layer

A builder posted to r/SideProject this week with a bluntly named tool: “the memory layer I wish existed when my AI agent kept asking the same questions.” That's not positioning — that's production scar tissue. It joins graphify on a memory-as-product trend line that keeps showing up in the indie tier first, not the platforms.

Memory is where reality exposes the gap between demo agents and production ones — every operator who ships a real agent ends up building this layer anyway. Source

3. SnapState ships persistent state for agent workflows — at the orchestration layer

A fresh Hacker News launch addresses the third leg: workflow state. Not skills, not memory, but the “where did this task pause and how do I resume it” primitive. It's the unsexy layer — and it's the one that turns long-running agent jobs from a fragile hope into a process you can let run unattended. It lands the same week n8n-mcp trended on GitHub and SprintiQ shipped sprint planning for Claude Code — a small constellation of “agents need real workflow infrastructure” tools.

State persistence is what flips an agent from a single-shot tool into a process you can let run overnight — skip this layer and you'll rebuild it the first time a job dies on a flaky API. Source

Radar

• Simon Willison: the Claude Code $100/month rumor is wrong — but pricing is still confusing enough to chill team rollouts. Worth a read before your next FinOps review. Link →
• DeepSeek V4 lands near-frontier at a fraction of the price — pegged as a real Opus alternative for cost-sensitive agent tasks. The “switch when the math says so” decision keeps getting easier. Link →
• A multi-agent observability tool ships on r/SideProject — agents are now numerous enough that watching one isn't the problem; watching the swarm is. Link →
• TradingAgents trends on GitHub — finance-vertical agent framework hitting Trending; the verticalization wave is moving from coding into capital markets. Link →
• SprintiQ ships open-source sprint planning for Claude Code — agents now manage the work that manages other agents. Link →

The Heartbeat is the daily pulse of the agentic economy. Built on Paperclip. Subscribe: readtheheartbeat.com | X: @TheHeartbeatAI