Fill web forms from a JSON list of field names and values, using saved templates or page labels to locate inputs. Optionally submit the form, save new field mappings, and redact values from recorded actions.
Fill a web form by mapping field-name → value, with optional template lookup from browser-templates for known forms
Fills web forms using JSON that maps field names to input values. It locates fields through a saved template when one is available; otherwise, it finds matching fields using page labels and related information. It supports text fields, selection fields, and checkboxes, and submits the form when requested. Newly discovered field mappings are saved as templates for future use.
Use it for registration, contact, and other forms with stable field names. It helps with repeated entries in the same form and with creating input templates for new sites. Forms with multiple steps are handled by chaining calls within the same session.
Uses Ruflo browser tools, browser-record, and AIDefence's personal information detection. Every value is checked before entry, and recorded actions replace values with redacted placeholders. Submission occurs with --submit. If _assert contains verification details, the post-submission state is checked. CAPTCHAs are referred to the user rather than bypassed.
This overview was written by AI (OpenAI Codex) from the public SKILL.md. Check the original below for the exact behavior.
AI rated this skill on four points using only the contents of its SKILL.md. Stars and popularity are not taken into account.
The total counts each point as A = 25, B = 15, C = 5. Rated by AI (OpenAI Codex) as of Oct 21, 2026. Treat it as a guide and read the original before installing.
Review the instructions the agent will receive before you install.
Fill a form using a structured field map ({"first_name": "Ada", "company": "..."}). When a browser-templates entry exists for the host, use it to resolve field names → CSS selectors automatically; otherwise resolve via the page accessibility snapshot.
browser-record.--template <name>): pull {field_name → selector} from browser-templates.browser_snapshot, walk the accessibility tree, match each input's accessible name / label to the field map keys.aidefence_has_pii before any keystroke; record pii_in_form: true in the session manifest. Do not record the values themselves in the trajectory; record only the field names + a redacted placeholder.browser_fill / browser_type / browser_select / browser_check per input type.--submit: locate the submit button via the snapshot, browser_click, then browser_wait for navigation.npx -y @claude-flow/cli@latest memory store --namespace browser-templates \
--key "<host>:<form-name>" \
--value "{field_map:{...}, submit_selector:..., post_submit_url_pattern:...}"
_assert key.browser_type (simulates keystrokes) rather than browser_fill (sets value programmatically). Record which one was used in the trajectory step.browser-form-fill invocations; chain them via the same session id.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Compare models available through the HuggingFace router with chat-ui configuration, research missing models, and write short English descriptions of their architecture and capabilities. Add entries to both production and development configuration files and commit the changes.
Create an Architecture Decision Record, a document for recording important design choices, with the next sequential number. It generates a Markdown template, registers the record in AgentDB, and links related decisions found through search.
Build a searchable index and relationship graph from ADRs, records of architectural decisions. Import two supported document formats, refresh existing metadata without duplicate relationships, and review summaries of statuses, missing references, and inconsistencies.
Rebuild the index of ADRs, records of architectural decisions, after files or relationship lines are deleted. It clears stored records and relationships, indexes the files still present, and checks that the final record count matches.
Review code changes against accepted Architecture Decision Records, documents that capture agreed design choices. Report violations, outdated references, compliant changes, and areas without ADR coverage, then suggest code fixes or a new decision record where appropriate.
Check saved architecture decision records (ADRs) for broken references, circular replacement relationships, and inconsistent statuses. Use the results to verify imported records or stop a CI check when selected integrity rules fail.