browser-harness-authoring

Map repeatable website workflows into verified, site-specific Hermes browser skills.

58|6|Updated Jul 19, 2026
One-click install
npx skills add https://github.com/AtlasOmnia/hermes-custom-pack --skill browser-harness-authoring-atlasomnia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-harness-authoring
Source: https://github.com/AtlasOmnia/hermes-custom-pack/tree/main/skills/browser-harness-authoring
Command: npx skills add https://github.com/AtlasOmnia/hermes-custom-pack --skill browser-harness-authoring-atlasomnia

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Recurring website tasks force the agent to rediscover the same controls, selectors, and failure modes on every run, wasting tool turns and producing inconsistent results. This Skill turns a known website flow into a documented, verified harness that later sessions can replay deterministically. ## Core Features & Use Cases - Structured Site Survey: Records browser lane compatibility, semantic targets (role + accessible name), stable DOM fallbacks, checkpoints, and recovery paths for every step. - Safety-First Authoring: Enforces dummy-data-only surveys, a strict no-submit boundary, and explicit decision/side-effect gates so irreversible actions (purchases, bookings, submissions) are never crossed during authoring or verification. - Harness Validation & Verification: Ships a dependency-free Python validator (scripts/validate_harness.py) plus templates and a schema reference to check structure, dates, evidence, and prohibited content like session refs or secrets. - Use Case: Map the order-status flow on an e-commerce site once, verify it with dummy data, and install the generated harness so future Hermes sessions—or a read-only cron job—replay it without re-exploring the site. ## Quick Start Ask Hermes to map the order-status flow on a specific website using dummy data and to stop before any irreversible action.

Frequently Asked Questions about browser-harness-authoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a website workflow into a reusable Hermes skill?

Survey the flow one step at a time with dummy data, recording semantic targets, stable fallbacks, checkpoints, and recovery paths. Then write the harness from the included template, validate it with validate_harness.py, and replay it in a fresh session before marking it tested.

What is a browser harness in Hermes agent automation?

A browser harness is a site-specific SKILL.md that records the verified browser lane, semantic targets, expected checkpoints, failure modes, recovery paths, and decision gates for one narrow website flow. It lets execution replay known steps instead of exploring the site each time.

Can a browser harness submit forms or complete purchases automatically?

No. Authoring and verification must stop before any external side effect such as purchases, bookings, transfers, or submissions. Consequential execution requires explicit user confirmation immediately before the irreversible step, and cron scheduling is limited to read-only or reversible flows.

Why should I not save @e element refs in a harness?

Browser snapshot refs like @e12 are session-local and regenerated on every snapshot, so they break on replay. Harnesses must store accessibility roles, accessible names, labels, or stable attributes instead, with visual anchors only as a last resort.

How do I validate a generated browser harness?

Run python3 scripts/validate_harness.py against the generated SKILL.md. The dependency-free validator checks required sections, overview fields, step structure, verification evidence, dates, and prohibited content such as secrets or session-local refs.

When does a browser harness expire or need re-verification?

Default expiry is 30 days for ordinary consumer UI flows and 7 days for flows depending on vision, coordinates, or brittle selectors. High-consequence flows must be rechecked before every run, and any observed UI, domain, or authentication change triggers immediate re-authoring.