prose-qa 0.2.0 → 0.2.3

package/skills/agent-browser/bundled/electron/SKILL.md

@@ -0,0 +1,236 @@
+---
+name: electron
+description: Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
+allowed-tools: Bash(agent-browser:*), Bash(npx agent-browser:*)
+---
+
+# Electron App Automation
+
+Automate any Electron desktop app using agent-browser. Electron apps are built on Chromium and expose a Chrome DevTools Protocol (CDP) port that agent-browser can connect to, enabling the same snapshot-interact workflow used for web pages.
+
+## Core Workflow
+
+1. **Launch** the Electron app with remote debugging enabled
+2. **Connect** agent-browser to the CDP port
+3. **Snapshot** to discover interactive elements
+4. **Interact** using element refs
+5. **Re-snapshot** after navigation or state changes
+
+```bash
+# Launch an Electron app with remote debugging
+open -a "Slack" --args --remote-debugging-port=9222
+
+# Connect agent-browser to the app
+agent-browser connect 9222
+
+# Standard workflow from here
+agent-browser snapshot -i
+agent-browser click @e5
+agent-browser screenshot slack-desktop.png
+```
+
+## Launching Electron Apps with CDP
+
+Every Electron app supports the `--remote-debugging-port` flag since it's built into Chromium.
+
+### macOS
+
+```bash
+# Slack
+open -a "Slack" --args --remote-debugging-port=9222
+
+# VS Code
+open -a "Visual Studio Code" --args --remote-debugging-port=9223
+
+# Discord
+open -a "Discord" --args --remote-debugging-port=9224
+
+# Figma
+open -a "Figma" --args --remote-debugging-port=9225
+
+# Notion
+open -a "Notion" --args --remote-debugging-port=9226
+
+# Spotify
+open -a "Spotify" --args --remote-debugging-port=9227
+```
+
+### Linux
+
+```bash
+slack --remote-debugging-port=9222
+code --remote-debugging-port=9223
+discord --remote-debugging-port=9224
+```
+
+### Windows
+
+```bash
+"C:\Users\%USERNAME%\AppData\Local\slack\slack.exe" --remote-debugging-port=9222
+"C:\Users\%USERNAME%\AppData\Local\Programs\Microsoft VS Code\Code.exe" --remote-debugging-port=9223
+```
+
+**Important:** If the app is already running, quit it first, then relaunch with the flag. The `--remote-debugging-port` flag must be present at launch time.
+
+## Connecting
+
+```bash
+# Connect to a specific port
+agent-browser connect 9222
+
+# Or use --cdp on each command
+agent-browser --cdp 9222 snapshot -i
+
+# Auto-discover a running Chromium-based app
+agent-browser --auto-connect snapshot -i
+```
+
+After `connect`, all subsequent commands target the connected app without needing `--cdp`.
+
+## Tab Management
+
+Electron apps often have multiple windows or webviews. Use tab commands to list and switch between them:
+
+```bash
+# List all available targets (windows, webviews, etc.)
+agent-browser tab
+
+# Switch to a specific tab by index
+agent-browser tab 2
+
+# Switch by URL pattern
+agent-browser tab --url "*settings*"
+```
+
+## Webview Support
+
+Electron `<webview>` elements are automatically discovered and can be controlled like regular pages. Webviews appear as separate targets in the tab list with `type: "webview"`:
+
+```bash
+# Connect to running Electron app
+agent-browser connect 9222
+
+# List targets -- webviews appear alongside pages
+agent-browser tab
+# Example output:
+#   0: [page]    Slack - Main Window     https://app.slack.com/
+#   1: [webview] Embedded Content        https://example.com/widget
+
+# Switch to a webview
+agent-browser tab 1
+
+# Interact with the webview normally
+agent-browser snapshot -i
+agent-browser click @e3
+agent-browser screenshot webview.png
+```
+
+**Note:** Webview support works via raw CDP connection.
+
+## Common Patterns
+
+### Inspect and Navigate an App
+
+```bash
+open -a "Slack" --args --remote-debugging-port=9222
+sleep 3  # Wait for app to start
+agent-browser connect 9222
+agent-browser snapshot -i
+# Read the snapshot output to identify UI elements
+agent-browser click @e10  # Navigate to a section
+agent-browser snapshot -i  # Re-snapshot after navigation
+```
+
+### Take Screenshots of Desktop Apps
+
+```bash
+agent-browser connect 9222
+agent-browser screenshot app-state.png
+agent-browser screenshot --full full-app.png
+agent-browser screenshot --annotate annotated-app.png
+```
+
+### Extract Data from a Desktop App
+
+```bash
+agent-browser connect 9222
+agent-browser snapshot -i
+agent-browser get text @e5
+agent-browser snapshot --json > app-state.json
+```
+
+### Fill Forms in Desktop Apps
+
+```bash
+agent-browser connect 9222
+agent-browser snapshot -i
+agent-browser fill @e3 "search query"
+agent-browser press Enter
+agent-browser wait 1000
+agent-browser snapshot -i
+```
+
+### Run Multiple Apps Simultaneously
+
+Use named sessions to control multiple Electron apps at the same time:
+
+```bash
+# Connect to Slack
+agent-browser --session slack connect 9222
+
+# Connect to VS Code
+agent-browser --session vscode connect 9223
+
+# Interact with each independently
+agent-browser --session slack snapshot -i
+agent-browser --session vscode snapshot -i
+```
+
+## Color Scheme
+
+The default color scheme when connecting via CDP may be `light`. To preserve dark mode:
+
+```bash
+agent-browser connect 9222
+agent-browser --color-scheme dark snapshot -i
+```
+
+Or set it globally:
+
+```bash
+AGENT_BROWSER_COLOR_SCHEME=dark agent-browser connect 9222
+```
+
+## Troubleshooting
+
+### "Connection refused" or "Cannot connect"
+
+- Make sure the app was launched with `--remote-debugging-port=NNNN`
+- If the app was already running, quit and relaunch with the flag
+- Check that the port isn't in use by another process: `lsof -i :9222`
+
+### App launches but connect fails
+
+- Wait a few seconds after launch before connecting (`sleep 3`)
+- Some apps take time to initialize their webview
+
+### Elements not appearing in snapshot
+
+- The app may use multiple webviews. Use `agent-browser tab` to list targets and switch to the right one
+
+### Cannot type in input fields
+
+- Try `agent-browser keyboard type "text"` to type at the current focus without a selector
+- Some Electron apps use custom input components; use `agent-browser keyboard inserttext "text"` to bypass key events
+
+## Supported Apps
+
+Any app built on Electron works, including:
+
+- **Communication:** Slack, Discord, Microsoft Teams, Signal, Telegram Desktop
+- **Development:** VS Code, GitHub Desktop, Postman, Insomnia
+- **Design:** Figma, Notion, Obsidian
+- **Media:** Spotify, Tidal
+- **Productivity:** Todoist, Linear, 1Password
+
+If an app is built with Electron, it supports `--remote-debugging-port` and can be automated with agent-browser.

package/skills/agent-browser/bundled/slack/SKILL.md

@@ -0,0 +1,285 @@
+---
+name: slack
+description: Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
+allowed-tools: Bash(agent-browser:*), Bash(npx agent-browser:*)
+---
+
+# Slack Automation
+
+Interact with Slack workspaces to check messages, extract data, and automate common tasks.
+
+## Quick Start
+
+Connect to an existing Slack browser session or open Slack:
+
+```bash
+# Connect to existing session on port 9222 (typical for already-open Slack)
+agent-browser connect 9222
+
+# Or open Slack if not already running
+agent-browser open https://app.slack.com
+```
+
+Then take a snapshot to see what's available:
+
+```bash
+agent-browser snapshot -i
+```
+
+## Core Workflow
+
+1. **Connect/Navigate**: Open or connect to Slack
+2. **Snapshot**: Get interactive elements with refs (`@e1`, `@e2`, etc.)
+3. **Navigate**: Click tabs, expand sections, or navigate to specific channels
+4. **Extract/Interact**: Read data or perform actions
+5. **Screenshot**: Capture evidence of findings
+
+```bash
+# Example: Check unread channels
+agent-browser connect 9222
+agent-browser snapshot -i
+# Look for "More unreads" button
+agent-browser click @e21  # Ref for "More unreads" button
+agent-browser screenshot slack-unreads.png
+```
+
+## Common Tasks
+
+### Checking Unread Messages
+
+```bash
+# Connect to Slack
+agent-browser connect 9222
+
+# Take snapshot to locate unreads button
+agent-browser snapshot -i
+
+# Look for:
+# - "More unreads" button (usually near top of sidebar)
+# - "Unreads" toggle in Activity tab (shows unread count)
+# - Channel names with badges/bold text indicating unreads
+
+# Navigate to Activity tab to see all unreads in one view
+agent-browser click @e14  # Activity tab (ref may vary)
+agent-browser wait 1000
+agent-browser screenshot activity-unreads.png
+
+# Or check DMs tab
+agent-browser click @e13  # DMs tab
+agent-browser screenshot dms.png
+
+# Or expand "More unreads" in sidebar
+agent-browser click @e21  # More unreads button
+agent-browser wait 500
+agent-browser screenshot expanded-unreads.png
+```
+
+### Navigating to a Channel
+
+```bash
+# Search for channel in sidebar or by name
+agent-browser snapshot -i
+
+# Look for channel name in the list (e.g., "engineering", "product-design")
+# Click on the channel treeitem ref
+agent-browser click @e94  # Example: engineering channel ref
+agent-browser wait --load networkidle
+agent-browser screenshot channel.png
+```
+
+### Finding Messages/Threads
+
+```bash
+# Use Slack search
+agent-browser snapshot -i
+agent-browser click @e5  # Search button (typical ref)
+agent-browser fill @e_search "keyword"
+agent-browser press Enter
+agent-browser wait --load networkidle
+agent-browser screenshot search-results.png
+```
+
+### Extracting Channel Information
+
+```bash
+# Get list of all visible channels
+agent-browser snapshot --json > slack-snapshot.json
+
+# Parse for channel names and metadata
+# Look for treeitem elements with level=2 (sub-channels under sections)
+```
+
+### Checking Channel Details
+
+```bash
+# Open a channel
+agent-browser click @e_channel_ref
+agent-browser wait 1000
+
+# Get channel info (members, description, etc.)
+agent-browser snapshot -i
+agent-browser screenshot channel-details.png
+
+# Scroll through messages
+agent-browser scroll down 500
+agent-browser screenshot channel-messages.png
+```
+
+### Taking Notes/Capturing State
+
+When you need to document findings from Slack:
+
+```bash
+# Take annotated screenshot (shows element numbers)
+agent-browser screenshot --annotate slack-state.png
+
+# Take full-page screenshot
+agent-browser screenshot --full slack-full.png
+
+# Get current URL for reference
+agent-browser get url
+
+# Get page title
+agent-browser get title
+```
+
+## Sidebar Structure
+
+Understanding Slack's sidebar helps you navigate efficiently:
+
+```
+- Threads
+- Huddles
+- Drafts & sent
+- Directories
+- [Section Headers - External connections, Starred, Channels, etc.]
+  - [Channels listed as treeitems]
+- Direct Messages
+  - [DMs listed]
+- Apps
+  - [App shortcuts]
+- [More unreads] button (toggles unread channels list)
+```
+
+Key refs to look for:
+- `@e12` - Home tab (usually)
+- `@e13` - DMs tab
+- `@e14` - Activity tab
+- `@e5` - Search button
+- `@e21` - More unreads button (varies by session)
+
+## Tabs in Slack
+
+After clicking on a channel, you'll see tabs:
+- **Messages** - Channel conversation
+- **Files** - Shared files
+- **Pins** - Pinned messages
+- **Add canvas** - Collaborative canvas
+- Other tabs depending on workspace setup
+
+Click tab refs to switch views and get different information.
+
+## Extracting Data from Slack
+
+### Get Text Content
+
+```bash
+# Get a message or element's text
+agent-browser get text @e_message_ref
+```
+
+### Parse Accessibility Tree
+
+```bash
+# Full snapshot as JSON for programmatic parsing
+agent-browser snapshot --json > output.json
+
+# Look for:
+# - Channel names (name field in treeitem)
+# - Message content (in listitem/document elements)
+# - User names (button elements with user info)
+# - Timestamps (link elements with time info)
+```
+
+### Count Unreads
+
+```bash
+# After expanding unreads section:
+agent-browser snapshot -i | grep -c "treeitem"
+# Each treeitem with a channel name in the unreads section is one unread
+```
+
+## Best Practices
+
+- **Connect to existing sessions**: Use `agent-browser connect 9222` if Slack is already open. This is faster than opening a new browser.
+- **Take snapshots before clicking**: Always `snapshot -i` to identify refs before clicking buttons.
+- **Re-snapshot after navigation**: After navigating to a new channel or section, take a fresh snapshot to find new refs.
+- **Use JSON snapshots for parsing**: When you need to extract structured data, use `snapshot --json` for machine-readable output.
+- **Pace interactions**: Add `sleep 1` between rapid interactions to let the UI update.
+- **Check accessibility tree**: The accessibility tree shows what screen readers (and your automation) can see. If an element isn't in the snapshot, it may be hidden or require scrolling.
+- **Scroll in sidebar**: Use `agent-browser scroll down 300 --selector ".p-sidebar"` to scroll within the Slack sidebar if channel list is long.
+
+## Limitations
+
+- **Cannot access Slack API**: This uses browser automation, not the Slack API. No OAuth, webhooks, or bot tokens needed.
+- **Session-specific**: Screenshots and snapshots are tied to the current browser session.
+- **Rate limiting**: Slack may rate-limit rapid interactions. Add delays between commands if needed.
+- **Workspace-specific**: You interact with your own workspace -- no cross-workspace automation.
+
+## Debugging
+
+### Check console for errors
+
+```bash
+agent-browser console
+agent-browser errors
+```
+
+### Get current page state
+
+```bash
+agent-browser get url
+agent-browser get title
+agent-browser screenshot page-state.png
+```
+
+## Example: Full Unread Check
+
+```bash
+#!/bin/bash
+
+# Connect to Slack
+agent-browser connect 9222
+
+# Take initial snapshot
+echo "=== Checking Slack unreads ==="
+agent-browser snapshot -i > snapshot.txt
+
+# Check Activity tab for unreads
+agent-browser click @e14  # Activity tab
+agent-browser wait 1000
+agent-browser screenshot activity.png
+ACTIVITY_RESULT=$(agent-browser get text @e_main_area)
+echo "Activity: $ACTIVITY_RESULT"
+
+# Check DMs
+agent-browser click @e13  # DMs tab
+agent-browser wait 1000
+agent-browser screenshot dms.png
+
+# Check unread channels in sidebar
+agent-browser click @e21  # More unreads button
+agent-browser wait 500
+agent-browser snapshot -i > unreads-expanded.txt
+agent-browser screenshot unreads.png
+
+# Summary
+echo "=== Summary ==="
+echo "See activity.png, dms.png, and unreads.png for full details"
+```
+
+## References
+
+- **Slack docs**: https://slack.com/help
+- **Web experience**: https://app.slack.com
+- **Keyboard shortcuts**: Type `?` in Slack for shortcut list