Web scraping for dynamic content, authentication, pagination, and data extraction using Playwright.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add alphaonedev/openclaw-graph --skill playwright-scraperCompatible with
Supported agents
Handles JavaScript-rendered sites, login flows, and multi-page navigation with built-in wait strategies and selector management
Supports headless and visible browser modes, with async patterns for reliable automation across flaky elements
Extracts data via selectors with JSON output, captures screenshots and PDFs, and manages cookies and sessions per context
Configure via JSON files
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionplaywright-scraperExecute the skills CLI command in your project's root directory to begin installation:
epx add alphaonedev/openclaw-graph --skill playwright-scraperFetches playwright-scraper from alphaonedev/openclaw-graph and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/playwright-scraper
Restart Cursor to activate playwright-scraper. Access via /playwright-scraperin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
playwright-recording
digitalsamba/claude-code-video-toolkit · Testing · tag: playwright
playwright-mcp-dev
microsoft/playwright · Testing · tag: playwright
playwright-automation-fill-in-form
github/awesome-copilot · Testing · tag: playwright
firecrawl-scraper
jezweb/claude-skills · Productivity · tag: scraper
x-twitter-scraper
xquik-dev/x-twitter-scraper · Productivity · tag: scraper
web-scraper
zephyrwang6/myskill · Productivity · tag: scraper
Registry listing for playwright-scraper matched our evaluation — installs cleanly and behaves as described in the markdown.
playwright-scraper has been reliable in day-to-day use. Documentation quality is above average for community skills.
Keeps context tight: playwright-scraper is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in playwright-scraper — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: playwright-scraper is focused, and the summary matches what you get after install.
playwright-scraper is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
playwright-scraper is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
playwright-scraper reduced setup friction for our internal harness; good balance of opinion and flexibility.
playwright-scraper has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend playwright-scraper for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 72