aetherbrowser-operator

Route online tasks through the AetherBrowser operator to capture page-state proof.

6|1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill aetherbrowser-operator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aetherbrowser-operator
Source: https://github.com/issdandavis/SCBE-AETHERMOORE/tree/main/external/codex-skills-live/aetherbrowser-operator
Command: npx skills add https://github.com/issdandavis/SCBE-AETHERMOORE --skill aetherbrowser-operator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Route online tasks through the AetherBrowser operator to establish signed-in sessions, capture page-state proof, and keep online work within the SCBE browser lane.

Core Features & Use Cases

  • Real browser surface: route complex tasks to AetherBrowser for authentic page-state, signed-in sessions, and proof artifacts.
  • Cross-surface coordination: coordinate with repo, terminal, Codespaces, and lane runner surfaces for multi-domain tasks.
  • Safety and governance: keep online work inside the SCBE browser lane, with deterministic actions and traceable evidence.

Quick Start

Tell your AI to route the task through the AetherBrowser operator to drive the online work, capture proof, and fall back to deterministic fetch when needed.

Frequently Asked Questions about aetherbrowser-operator

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

FAQPage Schema
How do I automate browser tasks across multiple platforms like GitHub and Notion?

To automate browser tasks across GitHub, Notion, and other surfaces, you route online work through the AetherBrowser operator to establish signed-in sessions and keep actions within a controlled browser lane. It coordinates multi-domain tasks and captures page-state proof artifacts.

How does browser automation capture proof artifacts for online task execution?

Browser automation captures proof artifacts by routing tasks through the AetherBrowser operator, which records deterministic actions and generates evidence JSON alongside title snapshots. This ensures traceable governance for web work executed across various online surfaces.

Can I coordinate browser automation with terminal and repo surfaces for complex workflows?

Yes, you can coordinate browser automation with terminal, repo, and Codespaces surfaces. The operator routes online work to the right browser surface first, then coordinates with built-in search or fetch tools to execute multi-domain tasks and maintain cross-surface workflows.

What is the best way to handle blocked pages during web automation?

The best way to handle blocked pages during web automation is to use deterministic fetch as a fallback. When the AetherBrowser operator encounters a blocked browser surface, it reverts to deterministic fetch tools to continue the online task and capture necessary evidence.

Does browser automation work for authenticated sessions on platforms like Shopify and Hugging Face?

Yes, browser automation works for authenticated sessions on Shopify, Hugging Face, and other supported surfaces. The AetherBrowser operator establishes real signed-in sessions to provide authentic page-state and capture accurate proof artifacts for your online tasks.

Why keep online task execution inside a dedicated browser lane?

Keeping online task execution inside a dedicated browser lane ensures safety and governance by enforcing deterministic actions. The SCBE browser lane maintains traceable evidence and coordinates with lane runner surfaces, preventing uncontrolled web interactions during multi-domain automation.