What problem does it solve?
Automating web form submission requires resolving field names to CSS selectors, handling different input types, and protecting sensitive values from leaking into logs. This Skill standardizes that workflow with reusable per-site templates and a mandatory PII gate.
Core Features & Use Cases
- Template-based selector resolution: Reuse stored field-name-to-selector mappings from the browser-templates memory namespace for known forms, or resolve fields via the page accessibility snapshot.
- PII protection: Every value passes an aidefence_has_pii check before typing, and trajectories record only field names with redacted placeholders.
- Multi-input support: Handles text fields, selects, and checkboxes with browser_fill, browser_type, browser_select, and browser_check, plus optional submit and post-submit verification.
- Use Case: Automate a recurring signup or checkout form by storing its selector template once, then replaying submissions with new field values across sessions.
Quick Start
Fill the contact form at the given URL using the field map in fields.json and submit it with the stored template for that site.
