Automate browser interactions, test web pages and work with Playwright tests.
Diagnose and fix Claude in Chrome MCP extension connectivity issues.
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms…
Develop, debug, and deploy Apify Actors - serverless cloud programs for web scraping, automation, and data processing.
Diagnose and fix Claude in Chrome MCP extension connectivity issues.
Deep research and analysis tool. Generates comprehensive HTML reports on any topic, domain, paper, or technology. Use when user asks to…
Automate Agentql tasks via Rube MCP (Composio).
Expert in building browser extensions that solve real problems -
Diagnose Firefox DevTools MCP setup issues.
Use this skill for requests related to web research; it provides a structured approach to conducting comprehensive web research
Debug Bright Data Scraping Browser sessions using the Browser Sessions API.
Control Chrome browser via Claude extension.
Navigate Firefox to a URL and take a DOM snapshot for interaction
Automate web browser interactions using natural language via CLI commands.
Expert in building Chrome Extensions using Manifest V3.
Automates browser interactions including navigation, form filling, and data extraction using AI-driven snapshots.
Browser automation with persistent page state.
Integrate Apify into an existing JavaScript/TypeScript or Python application using the apify-client package.
Complete browser automation with Playwright.
Browser automation CLI for AI agents. Use when the user needs to inspect, test, or automate browser behavior: navigating pages, filling…
Monitor competitor pricing, features, changelogs, dashboards, and product changes with Firecrawl.
Web, Search & Scraping agent skills on mcprush shape how an agent reads and quotes what it finds, so an answer arrives with the source attached rather than with a confident paraphrase of one. The kinds are workflow, expertise, output format, voice & style and guardrail, and the one a skill belongs to, where its author declared it, is the fastest way to guess what it will do to your prompt.
What to look at before installing one is what it costs in context and what it takes away: a guardrail that refuses an action and a voice that rewrites a sentence are both skills, and only one of them will stop the agent doing something. Every skill here says what it costs in context, which kind it is where its author declared one, what it needs beside it to work and the licence it is published under, next to the publisher it came from and whether that publisher has been verified. The filters on the left narrow it further and the sort at the top decides what comes first.
A skill is not connected to anything: there is no endpoint to authorise and nothing routed through the gateway. Installing one drops a folder of instructions into the client’s own skill folder, and uninstalling it is deleting that folder. The exact line for each client is on the skill’s own page, because it differs by client rather than by skill.