scbe-browser-sidepanel-ops

Automate AetherBrowse browser enhancement, governance checks, and app-store packaging.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Build, improve, and package the local AetherBrowse browser with an AI sidepanel workflow, governance checks, and app-store-ready Android artifacts.

Core Features & Use Cases

  • Research: Collect source-backed ideas and governance-aligned improvements for the local browser.
  • Implement: Make small, deterministic changes to browser modules while preserving governance paths.
  • Validate: Run targeted tests and smoke tests to verify sidepanel and browser actions without regressions.
  • Package: Build and package artifacts for app stores (Play/Kindle) and generate a release manifest.
  • Evidence + Handoff: Emit a cross-talk summary with artifact paths, changes, risks, and next actions.

Quick Start

Apply a small, verifiable change to the local AetherBrowse browser and generate an app-store-ready artifact.

Frequently Asked Questions about scbe-browser-sidepanel-ops

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

FAQPage Schema
How do I automate browser packaging for app-store release with governance checks?

Automating browser packaging involves applying deterministic change workflows, running governance checks, and generating app-store-ready Android artifacts with a release manifest. This workflow targets local development and outputs verified build packages for Play and Kindle stores.

What is the best way to generate release notes for local browser development?

Generating release notes for local browser development requires deterministic change workflows that track small, verifiable module updates. The process emits a cross-talk summary containing artifact paths, applied changes, identified risks, and recommended next actions.

How do I validate sidepanel actions and browser modules without regressions?

Validating sidepanel actions and browser modules without regressions requires running targeted tests and smoke tests after making small deterministic changes. This verifies sidepanel functionality and browser actions while preserving governance paths throughout the workflow.

Can I build app-store-ready Android artifacts from local browser development?

Building app-store-ready Android artifacts from local browser development is supported by packaging workflows that target Play and Kindle stores. The process generates a release manifest and performs artifact verification to ensure proper store packaging.

What limitations exist when applying deterministic changes to browser modules?

Limitations when applying deterministic changes to browser modules include the requirement to preserve governance paths during modifications. Changes must remain small and verifiable, with targeted tests confirming no regressions in sidepanel or browser actions before packaging proceeds.