opendevbrowser 0.0.10

package/skills/data-extraction/SKILL.md

@@ -0,0 +1,136 @@
+---
+name: data-extraction
+description: Patterns for extracting structured data from web pages including tables, lists, and paginated content with OpenDevBrowser.
+version: 1.0.0
+---
+
+# Data Extraction Skill
+
+## Table Extraction
+
+1. Navigate to page with data table:
+   ```
+   opendevbrowser_goto url="https://example.com/data"
+   ```
+
+2. Wait for table to load:
+   ```
+   opendevbrowser_wait state="networkidle"
+   ```
+
+3. Get table HTML structure:
+   ```
+   opendevbrowser_dom_get_html ref="[table-ref]"
+   ```
+
+4. Parse the HTML to extract rows and cells.
+
+### Common Table Patterns
+
+Standard HTML tables:
+```html
+<table>
+  <thead><tr><th>Header</th></tr></thead>
+  <tbody><tr><td>Data</td></tr></tbody>
+</table>
+```
+
+CSS-based grids:
+```html
+<div class="grid">
+  <div class="row">
+    <div class="cell">Data</div>
+  </div>
+</div>
+```
+
+## List Extraction
+
+For unordered/ordered lists:
+1. Identify list container ref
+2. Extract text content:
+   ```
+   opendevbrowser_dom_get_text ref="[list-ref]"
+   ```
+
+For card-based layouts:
+1. Identify repeating pattern
+2. Extract each card's content individually
+
+## Pagination Handling
+
+### Numbered Pagination
+
+1. Extract current page data
+2. Find "Next" or page number button:
+   ```
+   opendevbrowser_snapshot
+   ```
+3. Click next page:
+   ```
+   opendevbrowser_click ref="[next-button-ref]"
+   ```
+4. Wait for new content:
+   ```
+   opendevbrowser_wait state="networkidle"
+   ```
+5. Repeat until no more pages
+
+### Infinite Scroll
+
+1. Extract visible data
+2. Scroll to load more:
+   ```
+   opendevbrowser_scroll direction="down" amount=1000
+   ```
+3. Wait for new content
+4. Repeat until no new items appear
+
+### Load More Button
+
+1. Extract visible data
+2. Click "Load More":
+   ```
+   opendevbrowser_click ref="[load-more-ref]"
+   ```
+3. Wait for new content
+4. Repeat until button disappears
+
+## Data Export Workflow
+
+1. Collect all extracted data in structured format
+2. Use `opendevbrowser_run` to serialize data:
+   ```javascript
+   return JSON.stringify(collectedData, null, 2);
+   ```
+
+## Handling Dynamic Content
+
+For JavaScript-rendered content:
+
+1. Wait for specific element to appear
+2. Use network polling to detect data loading:
+   ```
+   opendevbrowser_network_poll
+   ```
+3. Take snapshot after XHR/Fetch completes
+
+## Structured Data Detection
+
+Look for embedded structured data:
+- JSON-LD scripts: `<script type="application/ld+json">`
+- Microdata attributes: `itemscope`, `itemprop`
+- RDFa attributes: `typeof`, `property`
+
+Extract via:
+```
+opendevbrowser_run script="return document.querySelector('script[type=\"application/ld+json\"]')?.textContent"
+```
+
+## Rate Limiting Considerations
+
+When extracting large datasets:
+- Add delays between page requests
+- Monitor for rate limit responses (429 status)
+- Respect robots.txt and terms of service
+- Consider using persistent profile to maintain session

package/skills/form-testing/SKILL.md

@@ -0,0 +1,113 @@
+---
+name: form-testing
+description: Comprehensive form testing patterns including validation, submission, and error handling with OpenDevBrowser.
+version: 1.0.0
+---
+
+# Form Testing Skill
+
+## Form Field Discovery
+
+1. Take a snapshot to map all form elements:
+   ```
+   opendevbrowser_snapshot
+   ```
+
+2. Identify field types:
+   - Text inputs: `<input type="text">`
+   - Email fields: `<input type="email">`
+   - Number fields: `<input type="number">`
+   - Select dropdowns: `<select>`
+   - Checkboxes: `<input type="checkbox">`
+   - Radio buttons: `<input type="radio">`
+   - Textareas: `<textarea>`
+   - File uploads: `<input type="file">`
+
+3. Note required fields (often marked with `required` attribute or asterisk).
+
+## Validation Testing
+
+Test each field's validation rules:
+
+### Required Fields
+1. Leave field empty
+2. Submit form
+3. Verify error message appears
+
+### Email Validation
+Test with:
+- Valid email: `user@example.com`
+- Missing @: `userexample.com`
+- Missing domain: `user@`
+- Invalid TLD: `user@example`
+
+### Length Constraints
+- Minimum length: Enter fewer characters than required
+- Maximum length: Enter more characters than allowed
+- Boundary values: Test exact min/max limits
+
+### Pattern Matching
+For fields with regex patterns:
+- Valid pattern match
+- Invalid characters
+- Edge cases
+
+## Form Submission Workflow
+
+1. Fill all required fields:
+   ```
+   opendevbrowser_type ref="[field-ref]" text="value"
+   ```
+
+2. For select dropdowns:
+   ```
+   opendevbrowser_select ref="[select-ref]" value="option-value"
+   ```
+
+3. For checkboxes:
+   ```
+   opendevbrowser_click ref="[checkbox-ref]"
+   ```
+
+4. Submit the form:
+   ```
+   opendevbrowser_click ref="[submit-ref]"
+   ```
+
+5. Wait for response:
+   ```
+   opendevbrowser_wait state="networkidle"
+   ```
+
+## Error Message Verification
+
+After invalid submission:
+
+1. Take new snapshot to capture error state
+2. Look for error messages near each field
+3. Verify error text matches expected message
+4. Check ARIA attributes for accessibility
+
+## Multi-Step Forms
+
+For wizard-style forms:
+
+1. Complete current step
+2. Click next/continue button
+3. Wait for next step to load
+4. Repeat until completion
+5. Verify final submission
+
+## File Upload Testing
+
+1. Use `opendevbrowser_run` to execute file input script
+2. Verify file preview appears
+3. Test file type restrictions
+4. Test file size limits
+
+## Form Reset Testing
+
+1. Fill form with data
+2. Click reset button
+3. Verify all fields cleared
+4. Verify any default values restored

package/skills/login-automation/SKILL.md

@@ -0,0 +1,98 @@
+---
+name: login-automation
+description: Best practices for automating login flows and authentication testing with OpenDevBrowser.
+version: 1.0.0
+---
+
+# Login Automation Skill
+
+## Credential Handling
+
+Store credentials securely using environment variables or config files outside the repository.
+
+Never hardcode credentials in test scripts or skill files.
+
+Use `opendevbrowser_type` with `sensitive: true` (if available) for password fields.
+
+## Form Detection Workflow
+
+1. Take a snapshot to identify login form elements:
+   ```
+   opendevbrowser_snapshot
+   ```
+
+2. Look for common patterns:
+   - Input fields with `type="email"`, `type="text"`, `name="username"`
+   - Input fields with `type="password"`
+   - Submit buttons with text containing "Sign in", "Log in", "Submit"
+
+3. Use refs to target form elements reliably.
+
+## Authentication Flow
+
+1. Navigate to login page:
+   ```
+   opendevbrowser_goto url="https://example.com/login"
+   ```
+
+2. Wait for form to load:
+   ```
+   opendevbrowser_wait state="networkidle"
+   ```
+
+3. Take snapshot to get refs:
+   ```
+   opendevbrowser_snapshot
+   ```
+
+4. Enter username/email:
+   ```
+   opendevbrowser_type ref="[email-input-ref]" text="user@example.com"
+   ```
+
+5. Enter password:
+   ```
+   opendevbrowser_type ref="[password-input-ref]" text="password123"
+   ```
+
+6. Click submit:
+   ```
+   opendevbrowser_click ref="[submit-button-ref]"
+   ```
+
+7. Wait for navigation:
+   ```
+   opendevbrowser_wait state="networkidle"
+   ```
+
+## Error Handling
+
+After login attempt, verify success:
+
+1. Check URL changed to expected destination
+2. Look for error messages in snapshot
+3. Verify session cookies are set via network poll
+
+Common failure patterns:
+- "Invalid credentials" messages
+- CAPTCHA challenges
+- Multi-factor authentication prompts
+- Rate limiting or lockout
+
+## MFA Handling
+
+For TOTP-based MFA:
+1. Generate code using appropriate library
+2. Wait for MFA input field to appear
+3. Enter the code
+4. Submit
+
+For SMS/Email MFA:
+- Requires manual intervention or test account bypass
+
+## Session Persistence
+
+Use persistent browser profiles to maintain sessions across runs:
+```
+opendevbrowser_launch profile="test-user" persistProfile=true
+```

package/skills/opendevbrowser-best-practices/SKILL.md

@@ -0,0 +1,81 @@
+---
+name: opendevbrowser-best-practices
+description: Use when the user asks to write browser scripts, automate navigation, use snapshot refs, or extract DOM elements. Provides script-first, snapshot/ref guidance.
+version: 0.1.0
+---
+
+# OpenDevBrowser Best Practices
+
+Use this guide to generate fast, reliable, script-first workflows without bloating tools or output.
+
+## Core Workflow (Snapshot -> Refs -> Actions)
+
+Prefer the snapshot/ref loop as the primary interaction model:
+
+1. Navigate or focus the target page.
+2. Capture a snapshot to obtain stable refs.
+3. Act on refs (click, type, select, scroll).
+4. Re-snapshot after navigation or large DOM changes.
+
+Use refs instead of raw selectors whenever possible.
+
+## Script-First Execution
+
+Batch related actions in a single run to reduce round-trips:
+
+- Use `opendevbrowser_run` for multi-step actions.
+- Keep steps small and deterministic.
+- End each run with a state check (snapshot or targeted extraction).
+
+Match the arguments used in the single-action tools.
+
+## Waiting and Stability
+
+Stabilize the page before acting:
+
+- Use `opendevbrowser_wait` after navigation and before interacting with newly rendered UI.
+- Prefer `networkidle` or `load` when the UI is fully dynamic.
+- Wait for a ref state when targeting specific elements.
+
+## Token-Efficient Extraction
+
+Keep outputs small and scoped:
+
+- Use `opendevbrowser_dom_get_text` or `opendevbrowser_dom_get_html` only on specific refs.
+- Avoid dumping full page HTML.
+- Use snapshot cursor paging when content is large.
+
+## Debug Signals (Lightweight)
+
+Use polling tools only when needed:
+
+- Use `opendevbrowser_console_poll` to check for runtime errors.
+- Use `opendevbrowser_network_poll` to confirm API calls and statuses.
+
+## Example Patterns
+
+### Login Flow (Batch)
+
+1. `goto` login URL.
+2. `wait` for page load.
+3. `snapshot` to get refs.
+4. `type` email/password refs.
+5. `click` submit ref.
+6. `wait` for navigation.
+7. `snapshot` to confirm state.
+
+### Targeted Extraction
+
+1. `snapshot` to get ref for the desired element.
+2. `dom_get_text` on that ref.
+
+## Mode Guidance
+
+- Use Mode A (managed) by default for zero-config operation.
+- Use Mode C (extension) only when existing logged-in tabs are required.
+
+## Safe Defaults
+
+- Keep CDP local-only by default.
+- Redact secrets in snapshot output.
+- Avoid raw CDP unless explicitly enabled.

package/skills/opendevbrowser-continuity-ledger/SKILL.md

@@ -0,0 +1,45 @@
+---
+name: opendevbrowser-continuity-ledger
+description: Maintain an OpenDevBrowser continuity ledger in opendevbrowser_continuity.md for long-running tasks and resumable work.
+version: 1.0.0
+---
+
+# OpenDevBrowser Continuity Ledger
+
+Use a lightweight ledger to keep long-running tasks on track across sessions or context compaction.
+
+## When to use
+- Multi-step work that spans several actions
+- Refactors, migrations, or release work
+- Investigations with multiple findings
+- Any task likely to resume later
+
+## Ledger file
+- Always use `opendevbrowser_continuity.md` at the repo root.
+- Create it if it does not exist.
+- Keep it short and factual.
+
+## Exact template (copy as-is)
+
+```markdown
+# OpenDevBrowser Continuity Ledger
+
+Goal (incl. success criteria):
+- Constraints/Assumptions:
+- Key decisions:
+- State:
+  - Done:
+  - Now:
+  - Next:
+- Open questions (UNCONFIRMED if needed):
+- Working set (files/ids/commands):
+```
+
+## Update rules
+1. At the start of a long task, read the ledger and refresh Goal/Now/Next.
+2. Update the ledger when goals, decisions, or progress state change.
+3. Record important tool outcomes briefly.
+4. If context is lost, rebuild the ledger from visible state and mark gaps as `UNCONFIRMED`.
+
+## Reply pattern
+Start replies with a short "Ledger Snapshot" (Goal + Now/Next + Open questions) when the ledger is in use.