Claude Skills for Research
Discover packages, clarify the question, and—only when needed—drive a browser. A research-oriented cut of the easyskills ranking.
Research intent
On easyskills, research means three practical jobs: find the right Agent Skill for a task, sharpen a fuzzy question before you burn tokens, and—only when necessary—inspect a live page with browser control. It is not an academic citation product and it is not a second copy of the full best Claude skills ranking.
Scores match the home ranking as of Nov 21, 2026. We keep risk labels honest: discovery and clarification are low drama; browser control is not. Public install counts appear as context on skill pages; they are never a free pass to skip reading SKILL.md.
Most people who land here are mid-decision: they know the job in English (“Excel formulas,” “clarify this ticket,” “check the staging checkout”) but do not know which package to trust. This hub is the short path for that intent.
How to choose
- Unknown package → find-skills.
- Fuzzy brief → grill-me.
- Must see the live UI → agent-browser with eyes open.
- Prefer pins; remove skills you have not triggered in a month so they stop competing for context.
- Run the safety checklist before every new install—especially anything discovery suggests.
Common research mistakes
- Accepting the first name match from find-skills without opening the repo.
- Treating grilling as optional theater, then wondering why the session wanders.
- Installing agent-browser on a daily-driver browser profile logged into production.
- Loading discovery + browser + three task skills “for later” and wondering why Claude’s advice conflicts.
find-skills — 88/100
Describe the job; Claude helps locate and install a matching skill when you do not know the package name. Huge public install counts (~4.4M reads around our ranking date) show reach, not trust.
Install when you are new to the ecosystem or you evaluate skills often. Skip when you already standardized on a short allowlist and want a quieter context window.
Safe pattern: ask for candidate owner/repo + why, open the source, then install. Unsafe pattern: “just install whatever you found.”
npx skills add vercel-labs/skills --skill find-skills
find-skills review. Open every proposed repository. Name collisions are common. Authors also use discovery from the authoring hub to study examples.
grill-me — 90/100
Clarify fuzzy research or product questions before you spend a session wandering. Rank #4 on the shortlist for a reason: small skill, high leverage on vague briefs.
Install when tickets start as Slack one-liners. Skip when acceptance criteria and non-goals are already written.
Time-box the interview. Lock decisions. Then research or build—do not grill forever.
npx skills add mattpocock/skills --skill grill-me
grill-me review. Also listed on the coding hub because clarifying a ticket is coding hygiene.
agent-browser — 82/100 (high-risk)
Drive Chrome from the terminal for clicks, forms, and screenshots. Powerful for live verification; high blast radius if pointed at the wrong profile or authenticated session.
Install when a live staging check is required and policy allows it. Skip when you only needed discovery or clarification—or when your only profile is production admin.
npx skills add vercel-labs/agent-browser --skill agent-browser
agent-browser review. Kept out of our top three by policy. Use a disposable browser profile and a non-production account for first runs.
What this hub is not
Document file jobs belong on documents. Screen taste and components belong on design. Writing new skills belongs on authoring. The full ranking remains the score source of truth.
Related
Install mechanics: How to install Claude skills. Terminal habits: Claude Code skills. Safety: skill-safety-check.
Back to the full ranking.
FAQ
What Claude skills help with research?
find-skills to discover packages, grill-me to clarify the research question, and agent-browser for live page checks when you accept the risk.
Is agent-browser required for research?
No. Start with find-skills and grill-me. Add agent-browser only for live UI or site verification.
Are install counts a trust signal?
No. Treat them as reach. Always open the proposed repository and read SKILL.md before you install.
What is a safe first research stack?
find-skills plus grill-me, with the safety checklist on every new package. Leave browser control off until you need a live check.