M44 Internal Testing OpenClaw Plugin & Skill | ClawHub
Looking to integrate M44 Internal Testing into your AI workflows? This free OpenClaw plugin from ClawHub helps you automate web & frontend development tasks instantly, without having to write custom tools from scratch.
What this skill does
Install and set up DataHive in a deterministic headless-friendly flow: (1) check/install browser (Chrome or Chromium), (2) check/create DataHive browser profile, (3) check Gog mailbox access, (4) install DataHive extension via CRX only (never Chrome Web Store UI), (5) login via email magic link and verify both dashboard and extension are logged in. Use for requests like 'install datahive', 'setup everything for datahive', or 'install datahive extension'.
Install
openclaw skills install @tuleyko/m44-internal-testingnpx clawhub@latest install m44-internal-testingFull SKILL.md
Open original| name | description |
|---|---|
| datahive-installer | Install and set up DataHive in a deterministic headless-friendly flow: (1) check/install browser (Chrome or Chromium), (2) check/create DataHive browser profile, (3) check Gog mailbox access, (4) install DataHive extension via CRX only (never Chrome Web Store UI), (5) login via email magic link and verify both dashboard and extension are logged in. Use for requests like 'install datahive', 'setup everything for datahive', or 'install datahive extension'. |
SKILL.md content below is scrollable.
DataHive Installer
Follow this exact sequence.
Browser selection
- Select browser target first:
BROWSER=chromefor Google ChromeBROWSER=chromiumfor Chromium
- Use the same browser target consistently in all script steps.
1) Check browser installation
- Run
BROWSER=<target> scripts/check_browser.sh. - If missing, install with:
BROWSER=<target> scripts/install_browser.sh
- Re-run browser check and continue only when target browser is confirmed.
2) Check DataHive browser profile
- Check whether browser profile
datahiveexists in OpenClaw config. - If profile is missing, create profile
datahivewith CDP port18810. - Continue only when profile
datahiveis available and startable.
3) Check Gog availability
- Verify Gog auth/account is available for the default mailbox.
- If Gog is unavailable, stop and report blocker:
- User must set up Gog first.
4) Install DataHive extension via CRX only
- Use extension ID
bonfdkhbkkdoipfojcnimjagphdnfedb. - Do not use Chrome Web Store UI.
- Run:
BROWSER=<target> scripts/install_extension_crx.sh bonfdkhbkkdoipfojcnimjagphdnfedbscripts/install_extension_policy.sh bonfdkhbkkdoipfojcnimjagphdnfedb
- Restart the
datahivebrowser profile after script execution. - Open
chrome://extensions/indatahiveprofile and verify:- Extension card
DataHiveis visible - Extension is enabled/active
- Browser shows managed/policy state when applicable
- Extension card
- If verification fails, stop and report extension-install blocker.
5) Login flow + final validation (required)
- Open DataHive login in
datahiveprofile. - Use email login only (no Google OAuth).
- Enter default email and click Login with email.
- Fetch latest DataHive magic-link email via Gog.
- Open
https://dashboard.datahive.ai/auth?token=....
After finishing the login flow, run this final validation exactly:
- Make sure you are in browser profile
datahive. - Confirm the dashboard is logged in while using browser profile
datahive. - Confirm the DataHive extension is installed in browser profile
datahive.
Completion Criteria
- Target browser is installed and runnable.
datahivebrowser profile exists and runs.- Gog mailbox access works.
- Login flow is completed via email magic link.
- Final validation passed:
- Active profile is
datahive. - Dashboard is logged in in
datahiveprofile. - DataHive extension is installed in
datahiveprofile.
- Active profile is
Resources
scripts/check_browser.shscripts/install_browser.shscripts/install_extension_crx.shscripts/install_extension_policy.shreferences/email-access.md