Alan
Community@ilm-alan
Alan's registry covers browser-driven page interaction via Playwright, human-voice prose rewriting, and token-based frontend visual design.
Agent Skills by Alan
Showing 3 vetted skills indexed across 3 GitHub repositories.
Ilm-Alanbrowser-use
Automate browser interactions, testing, and page capture through the playwright-cli command line.
Ilm-Alanhumanizer
Rewrite prose to remove AI-generated patterns and inject human voice.
Ilm-Alanfrontend-design
Design frontend visuals with strict token definitions for palette, typography, grid, and texture.
Frequently Asked Questions About Alan
FAQPage SchemaWhat tasks can I perform with Alan's browser-use skill?▼
You can navigate live pages, click elements, fill and submit forms, run JavaScript in-page, capture ARIA snapshots, screenshots, and PDFs, manage tabs, cookies, and localStorage, inspect and mock network requests, record traces and video, and run or debug Playwright tests.
Who should use these skills?▼
Frontend engineers and QA testers debugging UI behavior or running Playwright suites benefit from browser-use, designers needing consistent palette, typography, grid, and texture tokens use frontend-design, and writers or editors use humanizer to strip AI-generated patterns from prose.
How does browser-use run and what does it require?▼
It invokes the local playwright-cli binary via Bash to control a real browser, and can attach to the user's signed-in Chrome for authenticated tasks. It requires playwright-cli installed locally; static fetches without JavaScript, auth, or interaction should use simpler fetching instead.
When should browser-use be skipped?▼
Skip it for static content fetches where no JavaScript, authentication, or interaction is needed, when a dedicated browser MCP is already loaded and preferred, or when simply reading plain documentation pages. It is purpose-built for live page interaction and Playwright test debugging.