Automation vs Frontend · both proven

triage vs vercel-react-best-practices

Both skills were run through Claude twice: once on a fixed brief without the skill, once with it. The briefs differ because each is written for the job the skill claims to do, so compare each skill against its own baseline, then decide which difference matters for your work. They are in different categories, so this is a choice of job, not a head-to-head on the same job.

triage

Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

Category: Automation
Source: mattpocock/skills
License: MIT
Proof model: claude-opus-5-5
Brief: “You are triaging three new issues on an open-source Markdown editor. #412 "App crashes" by @kmorr: "It crashes when I paste stuff. Please fix asap." #413 "Export to PDF loses images" by @dlee: "On v2.3.1 (macOS 15), exporting a note with two PNG images to PDF produces a PDF with blank boxes where the images were. Steps: create note, drag in two PNGs, File > Export > PDF. Expected images in the PDF. Worked in v2.2.0." #414 "Add vim keybindings" by @tpz: "Would love vim mode. Lots of editors have it." Present the triage as a single HTML page: for each issue, the category, the state you would move it to and why, the comment you would post, and for any issue ready for an agent to implement, the agent brief.”
Skill commit: 5beb35b

Without the skillWith triage

⇆

Without, runWith triage, run3 independent runs per side, none selected by hand.

Download the with-skill page

vercel-react-best-practices

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Category: Frontend
Source: vercel-labs/agent-skills
License: Not stated
Proof model: claude-opus-5-5
Brief: “Here is a slow Next.js product list page. It fetches products, reviews and inventory one after another in a client component with useEffect, renders 500 product cards at once, imports the full lodash library, and re-sorts the list on every render. Rewrite it following current React and Next.js performance practice, and present the result as a single HTML page that shows the new code, explains each change, and estimates the impact of each.”
Skill commit: 063bee9

Without the skillWith vercel-react-best-practices

⇆

Without, runWith vercel-react-best-practices, run3 independent runs per side, none selected by hand.

Download the with-skill page

We don’t pick a winner for you: the pages are the evidence. Both proofs can be repeated with the brief, model and commit shown above. See alternatives to triage or alternatives to vercel-react-best-practices.