All 94 skillsWeb and data5 of 17
stryx:browser
When Claude must drive a live web page: open, click, fill a form, take a screenshot.
/stryx:browserInside its piece: 11 specks, one for each file on its shelf. Its sixteen group-mates glow on the open book behind it. The light splits toward teal, the band of Web and data.
In numbers
counted 2026-10-12 in the installed set- 8reference files
- 1helper scripts
- 11files in the skill
- 115KB on disk
- 10chapters
Use it when
in the skill’s own wordsWhen Claude has to drive or inspect a live web page
- open a URL
- click
- type
- fill or submit a form
- upload a file
- read the rendered page
- screenshot a page or element
- run JS in the page
- read console errors or network requests
- check computed CSS
- emulate a phone
- dark mode or slow network
- run Lighthouse
- record a trace or heap snapshot
- test a Chrome extension or PWA
- attach to Electron or a running Chrome over CDP
- when the user names chrome-devtools MCP
- the chrome-devtools CLI
- claude-in-chrome
- browser-use
- take_snapshot
- uid
- pageId
- isolatedContext or headless Chrome
- When browser tools fail (list_pages/new_page/navigate_page errors, "Could not find DevToolsActivePort", "Target closed", missing tools, a Chrome window popping up)
Not for
another skill does it- Scraping data at scale→ stryx:scraping
- E2E suites or browser-checking a branch→ stryx:test
- UX or accessibility audits→ stryx:design-audit
- What a trace or heap snapshot means for speed→ stryx:performance
- Why an app is broken→ stryx:debug
Inside the book
10 chapters, by title only- Hard rules
- Step 0: pick the driver
- The core loop
- Reading the page
- Changing conditions
- Evidence tools
- Files
- Extensions and PWAs
- When the driver fails
- Done check
Works with
the skills it names most- stryx:design-audit→When checking a design that exists: a UX walk-through, accessibility, polish or screen sizes.
- stryx:debug→Something is broken: a bug, an error, a crash, a failing test or wrong data.
- stryx:performance→Something is slow, laggy, too big or uses too much memory.
- stryx:test→When tests must be written or fixed, or you want the test written first (TDD).
- stryx:ai-power→When you are not sure which skill fits, or you say "load aipower": it is the map of all skills.
- stryx:scraping→When data must be pulled off websites, or a scraper comes back empty or blocked.
Claude loads it by itself when the moment comes; by hand, type the line at the top. It comes with the whole set: Installs all 94 skills, 32 agents and the brain program as one set. The skill’s own text is private source and is not shown here.