Vercel Didn't Write a Blog Post. They Wrote a Skill. The Difference Matters.

Vercel has written some of the most widely-read React performance content on the internet. Guides, blog posts, conference talks — there's no shortage of material documenting what good React looks like.

So when they shipped react-best-practices as a skill with 358,800 installs, the interesting question isn't what's in it. It's why they packaged it this way instead of the way they've always packaged knowledge.

The Shelf Life Problem

A blog post is written once. It's accurate on the day it's published. It decays.

React has changed significantly over the last three years. Concurrent features. The compiler. Server Components. use client and use server boundaries. Patterns that were best practice in 2022 are actively harmful in 2024 — not because they stopped working, but because the architecture they assumed no longer describes most applications.

Documentation ages in a particular way that's worse than being obviously wrong. It stays indexed. It still gets found. It continues to be followed by people who don't know the date it was written matters.

A skill can be updated. When the agent installs it, it gets the current version. The knowledge stays synchronized with what's actually true.

That's not a trivial difference. That's the core reason skills exist as a format.

40 Rules as a Single Context Load

The react-best-practices skill from vercel-labs/agent-skills ships 40 performance rules as agent instructions. Rules like: avoid inline object creation in render, memoize expensive computations, use key props correctly, understand when useCallback actually helps versus when it adds overhead without benefit.

The rules themselves are knowable. A senior React developer carries most of them in their head already. What changes when they're in a skill is when and how they get applied.

Without the skill, the agent applies whatever React knowledge it was trained on — which may be outdated, incomplete, or inconsistently weighted. With the skill loaded, all 40 rules are active in the context for every component it touches. The agent doesn't have to retrieve them. They're just there.

That's a meaningful difference in outcomes. Not because the agent didn't know React — it did. Because the rules are now consulted systematically rather than recalled when they happen to be relevant.

The Curation Problem Skills Solve

The second thing Vercel's choice reveals is something about curation. There's no shortage of React advice. There's actually too much of it — Stack Overflow answers, GitHub issues, blog posts, Twitter threads, each giving confidently different guidance for different versions and different contexts.

An agent trained on all of that content has absorbed a lot of conflicting information and has to make judgment calls about which guidance to apply. More training data doesn't solve this problem — it can make it worse by including more outdated or context-specific material alongside the current best practice.

A skill bypasses that problem. The 40 rules aren't filtered from everything the internet has ever said about React. They're the specific rules that Vercel's engineering team has determined are currently correct for the kinds of applications they're seeing in production.

Curation is the value. The format — skill rather than blog post — is what makes the curation available to the agent at the moment it needs it, rather than buried in training data where its signal gets averaged down.

What This Changes About Documentation

The implication extends beyond React. Every domain that has a set of known-good practices, a set of known-bad patterns, and a pattern of knowledge decay has the same problem Vercel solved with this skill.

Database query patterns. Security review checklists. API design conventions. Accessibility guidelines. The knowledge exists. It gets written down. It stops being consulted when it should be, or it gets consulted after it's expired.

Skills are a distribution format for perishable knowledge. That's new. It's worth thinking about what you're publishing as a blog post that should probably be a skill instead.

---

Part of the AI Skill Daily series — skills worth understanding, one at a time.