agent-browser
Browser automation built for repeatable agent workflows.
- Agent fit
- Native
- Main limitation
- The checked-in SKILL.md is a discovery stub; full instructions come from the installed CLI version.
- First risk
- Browser-side actions · High
GUIDE · CLAUDE CODE
Start with Skills that explicitly list Claude Code as a native target. Pick a narrow workflow first, then review what the package can access before you install it.
This is a decision page, not a claim that one Skill is universally best. The shortlist favors documented, source-linked options with clear boundaries.
SELECTION ORDER
Use these four checks in order. They keep an attractive directory card from becoming an overbroad installation.
Match one job to one Skill before building a larger stack
Prefer explicitly native Claude Code support over assumed portability
Check the first requested permission, especially browser, network, command, or write access
Open the listed source before trusting a score or install count
REVIEWABLE CANDIDATES
These are the six highest-scoring catalog entries that explicitly list native Claude Code support. Open each profile for source evidence, permissions, trade-offs, and Agent-specific installation steps. A score is not a safety approval.
Browser automation built for repeatable agent workflows.
Design constraints that push generated interfaces beyond generic AI UI.
Plan, implement, and evaluate high-quality MCP servers in Python or TypeScript.
Create, improve, and benchmark Agent Skills with trigger tests and comparative evaluation.
Review interfaces against practical web design and accessibility rules.
Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate.
COMMON QUESTIONS
A Skill is a folder of instructions and supporting resources that teaches Claude Code a repeatable workflow. Native support, source quality, permissions, and runtime safety still need separate checks.
Use project scope when the workflow should travel with one repository and be shared with its team. Use personal scope only for Skills you intentionally want available across repositories.
No. Install counts and scores are discovery signals, not proof of runtime behavior. Review the pinned source, requested access, first risk, and stop conditions before relying on a Skill.
DECISION BOUNDARY
A source-linked Skill may still change, request more access, or behave differently in your project. SkillSignal has not independently executed or security-certified every package.
KEEP EXPLORING
Use the directory matcher to combine your task, system, permission limit, price preference, and Claude Code fit. It uses deterministic rules and metadata only.
Open the Skill matcher ↗