Webcmd Adapter Authoring

You are an agent writing an adapter for a site. The goal of this skill is a 30-minute loop from zero context to a passing webcmd browser verify.

Use the existing tools throughout: webcmd browser *, webcmd doctor, webcmd browser init, and webcmd browser verify. This skill does not introduce new commands.

Browser-profile auth commands must reuse registerSiteAuthCommands. Keep only site-specific verify and openLogin logic in the adapter. The login row must return action_required and verify_command (normally webcmd <site> whoami); after the user reports done, agents run that returned command and verification must succeed before retrying the original workflow. Credentials, MFA, and CAPTCHA always use human handoff: CAPTCHA stops automation until the user reports done and verification succeeds, and adapter code must not collect or type passwords or secrets.

Commands whose primary operation searches or discovers matching items from a corpus must set tags: ['search']. Add short keywords only for non-obvious intent synonyms; do not infer tags from command names alone when authoring new adapters.

When debugging browser-backed adapters, start with --trace on --keep-tab true --window foreground. --trace on writes a trace artifact every round, and summary.md is the entry point for reviewing both failures and successes. --keep-tab true --window foreground keeps the tab lease alive and puts the browser window in front so you can inspect the final page state.

Precheck: Know Your Lane

Use coverage-matrix.md for a quick self-test before implementation. Ask three questions: