aetherbrowse-ops

Manage AetherBrowse browser stack startup, health checks, and governance logging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manage the AetherBrowse browser stack to ensure reliable startup, health checks, and governance logging.

Core Features & Use Cases

  • Starting, stopping, monitoring, and coordinating the 3-stack components (runtime server, worker, and electron GUI)
  • Health and governance visibility through dedicated endpoints and logs
  • Use cases include daily ops, incident response, and rollout verification

Quick Start

Start the AetherBrowse stack and monitor its health endpoints to confirm the system is operational.

Frequently Asked Questions about aetherbrowse-ops

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

FAQPage Schema
How do I start the AetherBrowse stack and verify it is running?

To start the AetherBrowse stack, execute the runtime commands for the server, worker, and Electron GUI components, then monitor the dedicated health endpoints to confirm operational status.

What is the best way to monitor health and governance logs for a multi-component browser stack?

Monitoring health and governance logs for a browser stack involves querying dedicated health endpoints and reviewing runtime, worker, and Electron GUI logs to ensure reliable startup and operational visibility.

Can I use this operational guidance for incident response and deployment rollout verification?

Yes, the operational guidance supports incident response and rollout verification by providing procedural steps for starting, stopping, and checking the status of the runtime, worker, and Electron GUI components.

Does this approach require external dependencies to manage the runtime, worker, and Electron GUI?

No external dependencies are required to manage the runtime, worker, and Electron GUI components, as the procedural guidance relies on internal runtime commands, health endpoints, and governance artifacts.

Why is my AetherBrowse worker component failing health checks during startup?

If the AetherBrowse worker component fails health checks during startup, review the governance logs and verify that the runtime server is operational before initiating the worker and Electron GUI components.

What steps are needed to safely stop the AetherBrowse runtime, worker, and GUI components?

To safely stop the AetherBrowse components, follow the procedural guidance within the runtime commands to halt the server, worker, and Electron GUI while ensuring governance logs capture the shutdown events.