01
Clear job
The trigger and promised output are specific enough to evaluate.
Seven Claude Code skills / 2026
Sources checked 03 Oct 2026
Best Claude Code skills, by task.
Seven top Claude skills for design, feature discovery, documents, React performance, skill creation, and browser work. Compare why each made the list and what it needs before you install.
Selected by Anton Shumeiko · Free catalogue and licence questions
02
Visible source
SKILL.md and supporting files can be inspected before installation.
03
Repeatable method
The package defines an ordered workflow and an observable result.
04
Known access
Tools, scripts, permissions, source, and license can be reviewed.
Seven examples
Seven skills for seven jobs.
Selection is based on the task covered, package structure, and source review. Repository stars appear as metadata and do not decide the list.
01
skill-creator
anthropics/skills
Create, improve, evaluate, and benchmark reusable Agent Skills with a structured workflow.
- Content language
- English
- Repository license
- Apache-2.0
Source updated
Best for: create your own skill
Turn a repeated workflow into a SKILL.md package, then compare its results across test prompts and improve its trigger.
Before you start: Prepare examples of the task and an observable result to evaluate.
02
frontend-design
anthropics/skills
Distinctive visual direction, typography, and interface design guidance for production web experiences.
- Content language
- English
- Repository license
- Apache-2.0
Source updated
Best for: design a web interface
Choose a visual direction, typography, and layout before building a landing page or application interface.
Before you start: Give it your audience, brand constraints, and the real content the interface must show.
03
brainstorming
obra/superpowers
A disciplined discovery workflow for exploring intent, constraints, requirements, and design before implementation.
- Content language
- English
- Repository license
- MIT
Source updated
Best for: clarify a feature before coding
Explore requirements and alternatives before committing to an implementation. Useful when the request is still ambiguous.
Before you start: Allow time for discovery questions and review the proposed design before implementation.
04
pdf
anthropics/skills
Read, create, inspect, render, and verify PDFs where content and visual layout both matter.
- Content language
- English
- Repository license
- Custom license
Source updated
Best for: work with pdf documents
Choose a document-specific workflow for extracting text, working with PDF files, and checking the resulting artifact.
Before you start: Check its file-level Anthropic terms. Public source access does not grant a general copying licence.
05
docx
anthropics/skills
Create, edit, inspect, and verify professional Word documents with layout-aware workflows.
- Content language
- English
- Repository license
- Custom license
Source updated
Best for: create or edit word documents
Use a workflow that understands Word structure, document edits, and verification of the final file.
Before you start: Check its file-level Anthropic terms and verify the output in a document viewer.
06
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance guidance from Vercel Engineering, covering rendering, data fetching, and bundle efficiency.
- Content language
- English
- Repository license
- MIT
Source updated
Best for: improve react and next.js performance
Review data fetching, rendering, and bundle decisions using Vercel’s prioritised performance guidance.
Before you start: Measure the bottleneck first and verify that the proposed change improves your application.
07
browser-use
browser-use/browser-use
Control a browser for automation, scraping, testing, screenshots, and repeatable web workflows.
- Content language
- English
- Repository license
- MIT
Source updated
Best for: verify work in a real browser
Navigate pages, interact with an interface, and inspect browser behaviour when a plain HTTP request cannot verify the task.
Before you start: Requires the browser-use CLI and browser connection setup described in the source package.
01
Choose the task first.
Use brainstorming for unclear requirements, frontend-design for visual direction, React best practices for implementation constraints, document skills for artifact-heavy work, and browser automation when verification requires a real web session.
02
Install fewer skills, with less overlap.
A large library can create ambiguous triggers and unnecessary context. Add one workflow, test whether it activates at the right time, then compare its output against the same task without the skill.
03
Re-review after updates.
Skills are executable instructions. A safe revision today does not automatically approve future script or dependency changes. Pin a reviewed commit for controlled environments and inspect meaningful updates before adopting them.