opendevbrowser 0.0.15 → 0.0.17

package/skills/data-extraction/SKILL.md

@@ -1,128 +0,0 @@
----
-name: data-extraction
-description: This skill should be used when the user asks to "extract data from a page", "scrape tables", "collect paginated results", "parse list/card content", or "export structured web data" with OpenDevBrowser.
-version: 1.1.0
----
-
-# Data Extraction Skill
-
-Use this guide to collect structured data from dynamic pages with predictable output quality.
-
-## Extraction Planning
-
-Define the schema before interacting:
-
-1. Define output fields and required keys.
-2. Identify page regions that contain those fields.
-3. Capture a fresh snapshot and map refs to schema fields.
-
-```text
-opendevbrowser_snapshot sessionId="<session-id>" format="actionables"
-```
-
-## Table Extraction
-
-For semantic HTML tables:
-
-1. Wait for table visibility.
-2. Snapshot and identify table/container refs.
-3. Extract targeted table HTML.
-4. Parse rows/cells in the host script.
-
-```text
-opendevbrowser_wait sessionId="<session-id>" until="networkidle"
-opendevbrowser_dom_get_html sessionId="<session-id>" ref="<table-ref>"
-```
-
-For virtualized or grid UIs, extract per-row/card refs and normalize in post-processing.
-
-## List and Card Extraction
-
-For repeated list/card content:
-
-1. Snapshot and identify repeating item refs.
-2. Extract only needed nodes per item (`title`, `price`, `meta`, `url`).
-3. Normalize records to a stable schema.
-
-```text
-opendevbrowser_dom_get_text sessionId="<session-id>" ref="<item-title-ref>"
-opendevbrowser_get_attr sessionId="<session-id>" ref="<item-link-ref>" name="href"
-```
-
-## Pagination Patterns
-
-### Numbered or Next/Previous Pagination
-
-1. Extract current page records.
-2. Click next/page ref.
-3. Wait for load.
-4. Re-snapshot and continue until terminal state.
-
-```text
-opendevbrowser_click sessionId="<session-id>" ref="<next-ref>"
-opendevbrowser_wait sessionId="<session-id>" until="networkidle"
-opendevbrowser_snapshot sessionId="<session-id>" format="actionables"
-```
-
-### Infinite Scroll
-
-1. Extract visible records.
-2. Scroll incrementally.
-3. Wait for newly loaded items.
-4. Stop when no new unique records appear.
-
-```text
-opendevbrowser_scroll sessionId="<session-id>" dy=1000
-opendevbrowser_wait sessionId="<session-id>" until="networkidle"
-```
-
-### Load More Button
-
-1. Extract visible records.
-2. Click load-more ref.
-3. Wait and re-snapshot.
-4. Repeat until button disappears or no new data arrives.
-
-## Structured Data Shortcuts
-
-When available, prefer embedded structured data:
-
-- JSON-LD scripts
-- Microdata attributes (`itemscope`, `itemprop`)
-
-```text
-opendevbrowser_dom_get_text sessionId="<session-id>" ref="<json-ld-script-ref>"
-```
-
-Parse JSON-LD in the host script and merge with extracted UI records if needed.
-
-## Quality Controls
-
-Apply quality checks during extraction:
-
-- Deduplicate by stable key (URL, ID, composite key).
-- Track page number and source URL per record.
-- Record null/missing fields explicitly.
-- Validate record counts per page before continuing.
-
-Use `opendevbrowser_network_poll` when extraction depends on API completion.
-
-```text
-opendevbrowser_network_poll sessionId="<session-id>" max=50
-```
-
-## Export Pattern
-
-Perform export in the host environment (outside tool calls):
-
-- Normalize to JSON for structured pipelines.
-- Convert to CSV only after schema normalization.
-- Keep raw extraction artifacts when auditability is required.
-
-## Compliance and Rate Limits
-
-Follow site constraints:
-
-- Respect robots, terms, and legal boundaries.
-- Add pacing between page transitions when needed.
-- Stop on repeated 429/403 responses and apply cooldown/retry policy.

package/skills/form-testing/SKILL.md

@@ -1,106 +0,0 @@
----
-name: form-testing
-description: This skill should be used when the user asks to "test a form", "verify validation", "check submission behavior", "test multi-step forms", or "debug form errors" with OpenDevBrowser.
-version: 1.1.0
----
-
-# Form Testing Skill
-
-Use this guide for comprehensive validation, submission, and error-state testing.
-
-## Form Discovery Pass
-
-Start every form suite with structural discovery:
-
-1. Capture `actionables` snapshot.
-2. Map refs for each input, control, and submit button.
-3. Record required and optional fields.
-4. Record dependent/conditional fields.
-
-```text
-opendevbrowser_snapshot sessionId="<session-id>" format="actionables"
-```
-
-## Validation Matrix
-
-Build a deterministic matrix per field type:
-
-| Category | Cases |
-|---|---|
-| Required | empty value, whitespace-only, valid value |
-| Email | valid format, missing `@`, missing domain |
-| Numeric | below min, above max, boundary values |
-| Length | below min length, exact bounds, above max length |
-| Pattern | valid regex match, invalid charset, malformed input |
-| Select/Radio | no selection, valid selection, invalid dependent state |
-
-Re-snapshot after each invalid submit to capture updated error refs.
-
-## Submission Workflow
-
-Run positive-path submission only after field validation is complete:
-
-1. Fill required fields.
-2. Set select/radio/checkbox controls.
-3. Verify submit button is enabled.
-4. Submit and wait for network/UI completion.
-
-```text
-opendevbrowser_type sessionId="<session-id>" ref="<text-ref>" text="valid value"
-opendevbrowser_select sessionId="<session-id>" ref="<select-ref>" values=["expected-option"]
-opendevbrowser_check sessionId="<session-id>" ref="<terms-ref>"
-opendevbrowser_is_enabled sessionId="<session-id>" ref="<submit-ref>"
-opendevbrowser_click sessionId="<session-id>" ref="<submit-ref>"
-opendevbrowser_wait sessionId="<session-id>" until="networkidle"
-```
-
-## Error-State Assertions
-
-For invalid submissions, assert three dimensions:
-
-1. Error text is present and specific.
-2. Accessibility attributes are set correctly (for example `aria-invalid="true"`).
-3. Focus behavior moves to first invalid field when applicable.
-
-```text
-opendevbrowser_get_attr sessionId="<session-id>" ref="<field-ref>" name="aria-invalid"
-opendevbrowser_dom_get_text sessionId="<session-id>" ref="<error-ref>"
-```
-
-## Multi-Step Form Pattern
-
-For wizard-style forms:
-
-1. Validate and submit current step.
-2. Wait for next-step container ref.
-3. Continue step-by-step until final submit.
-4. Verify completion state and any generated confirmation ID.
-
-Use `opendevbrowser_wait` with `ref` checks between steps.
-
-## Network Verification
-
-Correlate UI behavior with network activity:
-
-- Poll network events after submit.
-- Confirm expected endpoint, method, and status.
-- Flag silent frontend failures where UI does not surface server errors.
-
-```text
-opendevbrowser_network_poll sessionId="<session-id>" max=50
-```
-
-## File Upload Limitation
-
-Current tool surface does not provide direct file input attachment.
-
-- Handle upload steps manually, or
-- Extend tooling with a dedicated upload capability before automating file-input paths.
-
-## Regression-Friendly Batch Pattern
-
-Use `opendevbrowser_run` to keep suites deterministic and compact:
-
-```text
-opendevbrowser_run sessionId="<session-id>" steps=[{"action":"snapshot","args":{"format":"actionables"}},{"action":"type","args":{"ref":"<field-ref>","text":""}},{"action":"click","args":{"ref":"<submit-ref>"}},{"action":"snapshot","args":{"format":"outline"}}]
-```

package/skills/login-automation/SKILL.md

@@ -1,108 +0,0 @@
----
-name: login-automation
-description: This skill should be used when the user asks to "automate login", "test authentication", "sign in programmatically", "validate login errors", or "verify session persistence" with OpenDevBrowser.
-version: 1.1.0
----
-
-# Login Automation Skill
-
-Use this guide for deterministic login flows and authentication checks.
-
-## Secure Credential Handling
-
-Handle credentials outside skill files and source code:
-
-- Resolve credentials from environment variables or a secret manager in the orchestration layer.
-- Pass resolved values at runtime only.
-- Avoid logging secrets in transcripts, fixtures, or screenshots.
-
-## Preflight Checklist
-
-Before typing credentials:
-
-1. Launch or connect to the intended session mode.
-2. Navigate to the login URL.
-3. Wait for page readiness.
-4. Capture a fresh snapshot and identify refs.
-
-```text
-opendevbrowser_goto sessionId="<session-id>" url="https://example.com/login"
-opendevbrowser_wait sessionId="<session-id>" until="networkidle"
-opendevbrowser_snapshot sessionId="<session-id>" format="actionables"
-```
-
-## Canonical Login Flow
-
-Execute login in a strict order:
-
-1. Type identifier into email/username ref.
-2. Type password into password ref.
-3. Click submit.
-4. Wait for navigation or authenticated UI state.
-5. Re-snapshot for post-login verification.
-
-```text
-opendevbrowser_type sessionId="<session-id>" ref="<identifier-ref>" text="<resolved-identifier>"
-opendevbrowser_type sessionId="<session-id>" ref="<password-ref>" text="<resolved-password>"
-opendevbrowser_click sessionId="<session-id>" ref="<submit-ref>"
-opendevbrowser_wait sessionId="<session-id>" until="networkidle"
-opendevbrowser_snapshot sessionId="<session-id>" format="outline"
-```
-
-## Success Validation
-
-Validate more than one signal:
-
-- URL or route changed to expected authenticated location.
-- Authenticated-only UI ref becomes visible.
-- Login request in `opendevbrowser_network_poll` returns expected status.
-
-```text
-opendevbrowser_network_poll sessionId="<session-id>" max=50
-```
-
-Use `opendevbrowser_is_visible` or `opendevbrowser_get_attr` for deterministic assertions.
-
-## Error and Recovery Handling
-
-Handle common blockers explicitly:
-
-- Invalid credentials: assert error banner text near form.
-- CAPTCHA/challenge: classify as manual checkpoint.
-- MFA prompt: continue with second-factor workflow if test account supports it.
-- Lockout/rate limit: stop retries and rotate test account or cooldown window.
-
-After any failure, re-snapshot before retrying to avoid stale refs.
-
-## MFA Flow Pattern
-
-For MFA-capable test flows:
-
-1. Submit primary credentials.
-2. Wait for MFA input ref.
-3. Enter OTP/ref-based code.
-4. Submit and validate authenticated state.
-
-```text
-opendevbrowser_wait sessionId="<session-id>" ref="<mfa-input-ref>" state="visible"
-opendevbrowser_type sessionId="<session-id>" ref="<mfa-input-ref>" text="<resolved-otp>"
-opendevbrowser_click sessionId="<session-id>" ref="<mfa-submit-ref>"
-```
-
-## Session Persistence Checks
-
-Use persistent profiles when verifying remembered sessions:
-
-```text
-opendevbrowser_launch profile="auth-test" persistProfile=true noExtension=true
-```
-
-Then reopen and verify whether re-authentication is required.
-
-## Batch Script Pattern
-
-Use `opendevbrowser_run` for compact, repeatable flows:
-
-```text
-opendevbrowser_run sessionId="<session-id>" steps=[{"action":"goto","args":{"url":"https://example.com/login"}},{"action":"wait","args":{"until":"networkidle"}},{"action":"snapshot","args":{"format":"actionables"}},{"action":"type","args":{"ref":"<identifier-ref>","text":"<resolved-identifier>"}},{"action":"type","args":{"ref":"<password-ref>","text":"<resolved-password>"}},{"action":"click","args":{"ref":"<submit-ref>"}},{"action":"wait","args":{"until":"networkidle"}},{"action":"snapshot","args":{"format":"outline"}}]
-```