💬 Commit message: Update 2026-02-08 03:05:28, 17 files, 662 lines
📁 Files changed: 17 📝 Lines changed: 662 • plugin.json • .mcp.json • README.md • analyze.md • compare.md • end.md • extract.md • fill.md • goto.md • restore.md • save.md • scrape.md • screenshot.md • start.md • package.json • browser.ts • mcp.ts
This commit is contained in:
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Analyze the current page content and structure
|
||||
---
|
||||
|
||||
Use the analyze_page MCP prompt to analyze the current browser page.
|
||||
|
||||
If the browser is not launched, first navigate to a URL using the goto tool, then analyze the page structure, content, and interactive elements.
|
||||
|
||||
Provide:
|
||||
1. A summary of the page purpose
|
||||
2. Key interactive elements (forms, buttons, links)
|
||||
3. Notable structure or patterns
|
||||
4. Suggestions for useful actions
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Compare page states with screenshots before and after an action
|
||||
---
|
||||
|
||||
Compare page states:
|
||||
|
||||
1. Take an initial screenshot of the current page
|
||||
2. Ask what action to perform (click, navigate, submit, etc.)
|
||||
3. Perform the requested action
|
||||
4. Take another screenshot
|
||||
5. Describe the visual and structural differences
|
||||
|
||||
What action would you like to perform between screenshots? $ARGUMENTS
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
description: End the current browsing session and close the browser
|
||||
---
|
||||
|
||||
End the current browsing session.
|
||||
|
||||
Use the `close` tool to close the browser. This will:
|
||||
1. Close all browser pages
|
||||
2. Clear the browser state
|
||||
3. Free up system resources
|
||||
|
||||
The browser can be relaunched with any navigation command (goto, start, etc.)
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Extract structured data from the current page
|
||||
---
|
||||
|
||||
Extract structured data from the current browser page.
|
||||
|
||||
Selector (optional): $ARGUMENTS
|
||||
|
||||
Steps:
|
||||
1. If a selector is provided, use the query tool to find matching elements
|
||||
2. Analyze the page structure to identify data patterns
|
||||
3. Extract and structure the data in a useful format (JSON, table, etc.)
|
||||
4. Identify patterns that could help with similar pages
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Help fill out a form on the current page
|
||||
---
|
||||
|
||||
Fill form with data: $ARGUMENTS
|
||||
|
||||
Steps:
|
||||
1. Use the query tool to find form inputs (input, textarea, select)
|
||||
2. Identify required fields and their types
|
||||
3. If data is provided, parse it and fill the matching fields using the type tool
|
||||
4. Report what was filled and any issues encountered
|
||||
|
||||
If no data provided, describe the form fields found and ask what to fill in.
|
||||
@@ -0,0 +1,12 @@
|
||||
---
|
||||
description: Navigate to a URL and describe what you find
|
||||
---
|
||||
|
||||
Navigate to: $ARGUMENTS
|
||||
|
||||
Steps:
|
||||
1. Use the goto tool to navigate to the URL
|
||||
2. Take a screenshot to see the page
|
||||
3. Describe what you see
|
||||
4. Identify the main interactive elements
|
||||
5. Suggest what actions might be useful
|
||||
@@ -0,0 +1,13 @@
|
||||
---
|
||||
description: Restore a previously saved browsing session
|
||||
---
|
||||
|
||||
Restore session from: $ARGUMENTS
|
||||
|
||||
Use the `session_restore` tool to restore a previously saved session:
|
||||
- Navigate to the saved URL
|
||||
- Restore all cookies
|
||||
- Restore localStorage data
|
||||
- Restore sessionStorage data
|
||||
|
||||
If no path is specified, restore from `session.json` in the current directory.
|
||||
@@ -0,0 +1,15 @@
|
||||
---
|
||||
description: Save the current browsing session state to a file
|
||||
---
|
||||
|
||||
Save the current session state to: $ARGUMENTS
|
||||
|
||||
Use the `session_save` tool to save:
|
||||
- Current URL and page title
|
||||
- All cookies
|
||||
- localStorage data
|
||||
- sessionStorage data
|
||||
|
||||
If no path is specified, save to `session.json` in the current directory.
|
||||
|
||||
This allows you to restore the session later with `/claude-browse:restore`.
|
||||
@@ -0,0 +1,14 @@
|
||||
---
|
||||
description: Scrape content from a webpage
|
||||
---
|
||||
|
||||
Scrape and extract content from: $ARGUMENTS
|
||||
|
||||
Steps:
|
||||
1. Navigate to the URL using `goto`
|
||||
2. Wait for the page to load
|
||||
3. Query the page structure to understand the layout
|
||||
4. Extract the relevant content using `query` and `eval` tools
|
||||
5. Return the structured data
|
||||
|
||||
Focus on extracting meaningful content (text, links, data) rather than raw HTML.
|
||||
@@ -0,0 +1,9 @@
|
||||
---
|
||||
description: Take a screenshot of the current page
|
||||
---
|
||||
|
||||
Take a screenshot of the current browser page and analyze its contents.
|
||||
|
||||
If the browser hasn't been started yet, ask for a URL first, navigate there, then take the screenshot.
|
||||
|
||||
Use the `screenshot` tool with fullPage=$ARGUMENTS if specified (true/false), otherwise use default viewport.
|
||||
@@ -0,0 +1,11 @@
|
||||
---
|
||||
description: Start an interactive browsing session
|
||||
---
|
||||
|
||||
Start an interactive browser session. Use the browser tools to:
|
||||
1. Navigate to URLs with `goto`
|
||||
2. Take screenshots to see page content
|
||||
3. Query elements with CSS selectors
|
||||
4. Click and type to interact with pages
|
||||
|
||||
The browser is headless WebKit (Safari engine). Start by asking what URL to visit.
|
||||
Reference in New Issue
Block a user