m44-internal-testing_skill

This skill installs and configures DataHive in a headless, deterministic flow including browser setup, profile creation, CRX extension install, and login

Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill m44-internal-testing

_meta.json293 B
SKILL.md3.1 KB

Overview

This skill installs and configures DataHive in a deterministic, headless-friendly flow. It automates browser selection and installation, creates and verifies a dedicated browser profile, installs the DataHive extension via CRX (never the Chrome Web Store UI), and completes login using the email magic-link flow. The goal is repeatable, verifiable setup that reports blockers when human action is required.

How this skill works

The skill runs scripted checks and installers for Chrome or Chromium, ensures a named browser profile (datahive) with a fixed CDP port, and validates Gog mailbox access for magic-link delivery. It installs the DataHive extension by CRX and policy scripts, restarts the profile, and confirms extension visibility and active state. Finally it triggers the email-login flow, fetches the latest magic link via Gog, opens the dashboard link in the datahive profile, and performs final validation that both dashboard and extension are logged in.

When to use it

Install DataHive on a headless CI runner or cloud VM
Provision a reproducible browser/profile for DataHive testing
Onboard a machine where extension store UI is blocked or disallowed
Re-run environment setup after system rebuild or browser upgrade
Validate that extension + dashboard auth succeed together

Best practices

Pick BROWSER=chrome or BROWSER=chromium once and use it consistently across all script commands
Create and verify the datahive profile with CDP port 18810 before extension steps
Always install the extension via the CRX+policy scripts; do not rely on the Web Store UI
Verify Gog mailbox access early; stop and resolve Gog issues rather than proceed blind
Restart the datahive profile after extension installation and explicitly check chrome://extensions/ for state

Example use cases

CI job that sets up a test agent with DataHive extension and runs integration tests
Cloud VM provisioning for remote DataHive sessions where GUI store access is restricted
Automated recovery script to re-create datahive profile and re-install extension after disk restore
Onboarding checklist for a new machine to ensure browser, profile, extension, and login all succeed

FAQ

Set BROWSER=chrome for Chrome or BROWSER=chromium for Chromium and use that target consistently.

What if the Gog mailbox is not available?

Stop the installer and treat Gog absence as a blocker. The user must configure Gog mailbox access before proceeding.