feat: add CloakBrowser CLI to public registry

[dreamor]

Summary

Add CloakBrowser CLI (@dreamor/cloakbrowser-cli) to the public registry.

CLI Details

Field	Value
Name	cloakbrowser
Display Name	CloakBrowser CLI
Entry Point	cloak
Package	@dreamor/cloakbrowser-cli (npm)
Category	web
Requires	Node.js >= 20, cloakbrowser >= 0.3.0, playwright-core >= 1.40.0

What CloakBrowser CLI Does

CloakBrowser CLI wraps the CloakBrowser stealth Chromium browser with a structured, agent-friendly command surface. It covers:

• Launch options: headless/no-headless, persistent context, fingerprint flags (platform, GPU, hardware concurrency, screen, WebRTC)
• Humanize behaviors: careful/default/fast presets with configurable delays
• Page operations: navigation, click, fill, type, scroll, select, drag, upload
• Content extraction: HTML, text, markdown, screenshots, PDF, a11y tree snapshots
• Session management: multi-page sessions with state save/restore
• Cookies & storage: get/set/clear cookies, localStorage, sessionStorage
• Network: HTTP requests with custom headers and body
• CDP gateway: direct Chrome DevTools Protocol access
• One-shot helpers: cloak fetch, cloak scrape for quick page retrieval
• Self-test: cloak doctor and cloak test --detector fingerprintjs

Clean Install Smoke Test

# 1. Install globally
npm install -g @dreamor/cloakbrowser-cli cloakbrowser playwright-core

# 2. Verify CLI is accessible
cloak --help
# Expected: prints usage/help text with all available commands

# 3. Run self-diagnostic
cloak doctor
# Expected: confirms Node.js, cloakbrowser binary, and playwright-core are all installed and compatible

# 4. (Optional) One-shot fetch test — requires cloakbrowser binary installed
cloak binary install            # one-time ~200MB Chromium download
cloak fetch https://example.com --markdown --pretty
# Expected: returns page content as markdown

Checklist

• Entry follows the registry schema (npm package manager fields)
• npm_package is a published npm package (@dreamor/cloakbrowser-cli)
• skill_md points to the SKILL.md in the source repo
• source_url points to the GitHub repository
• Description is concise and informative

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 711b124ed9

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Point skill_md at an existing upstream skill

The new registry entry advertises skill_md as https://github.com/dreamor/cloakbrowser-cli/blob/main/SKILL.md, but the upstream repository currently has no SKILL.md at that path (the repo listing only shows README/package files and the raw URL returns 404). Any cli-hub/UI user following this field to learn the agent usage guide for CloakBrowser will land on a broken link; either add the skill to the upstream repo or point this field at an existing document.

Useful? React with 👍 / 👎.

[yuh-yang]

Thanks for adding CloakBrowser to the public registry. I rechecked the external resources and the upstream SKILL.md/npm package are reachable now, so the earlier automated 404 comment is stale.

The remaining structural issue is that this PR also adds SKILL.md at the root of the CLI-Anything repository. For a third-party public registry entry, the skill should live in the upstream project and be referenced from public_registry.json; adding a root SKILL.md here is misleading and can conflict with this repository's own skill/plugin files. Please remove the root SKILL.md from this PR.

Please also include a clean install smoke note for npm install -g @dreamor/cloakbrowser-cli cloakbrowser playwright-core, cloak --help, and cloak doctor or an equivalent safe command.

[dreamor]

Hi @yuh-yang, thanks for catching that! You were right — the root SKILL.md was indeed introduced by this PR (commit 667ff11), not a pre-existing file. I had incorrectly compared against my fork's main which already carried that file from the earlier attempt.

I've now removed SKILL.md from this PR. The only remaining change is the public_registry.json entry, where the skill_md field points to the upstream project: https://github.com/dreamor/cloakbrowser-cli/blob/main/SKILL.md.