Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Agent Browser Assistant

v1.0.0

For browser automation tasks, web data scraping, form filling, page screenshots, UI testing, and more.

0· 0·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for openlark/agent-browser-assistant.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Agent Browser Assistant" (openlark/agent-browser-assistant) from ClawHub.
Skill page: https://clawhub.ai/openlark/agent-browser-assistant
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Canonical install target

openclaw skills install openlark/agent-browser-assistant

ClawHub CLI

Package manager switcher

npx clawhub@latest install agent-browser-assistant
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The name/description (browser automation, scraping, testing) is plausible, but the SKILL.md references reusing a user's browser profile and reading/writing local file paths (uploads, PDF export). Those capabilities normally require explicit access to browser profile data or filesystem paths, yet the skill declares no config paths, credentials, or permissions — an incoherence.
!
Instruction Scope
Runtime instructions allow arbitrary page snapshots, evaluation of arbitrary JS (fn parameter), and capturing full page structure/screenshots. They also show file uploads and saving PDFs to local paths. These instructions permit collecting sensitive page content and local files; the skill gives broad, open-ended authority without limits or data-handling rules.
Install Mechanism
Instruction-only skill with no install spec or downloaded artifacts. No code is written to disk by the skill itself, which reduces supply-chain risk.
!
Credentials
The skill declares no environment variables or credentials, yet explicitly references reusing a user's browser profile and local filesystem paths. Accessing a browser profile can expose cookies/session tokens; file upload examples reference absolute paths. The requested capabilities are disproportionate to the declared requirements and lack justification.
Persistence & Privilege
The skill is not marked always:true and does not request persistent installation. However, its instructions encourage reuse of an existing user browser profile (which is effectively access to other application data). Autonomous invocation is allowed by default — consider that an agent using this skill could access sensitive browsing state when invoked.
What to consider before installing
Before installing or using this skill, ask the provider/platform these questions: (1) What exactly does the platform 'browser' tool do and where does it run (sandbox vs host browser)? Does profile="user" actually load the local browser profile or just a named sandbox profile? (2) Are file uploads and PDF writes sandboxed, or can the skill read arbitrary host filesystem paths? (3) Where do snapshots and scraped data go — are they stored locally, sent to external endpoints, or returned to other services? (4) Can the skill execute arbitrary JS on pages and, if so, is that logged/audited? Practical precautions: test in an isolated environment first (no real credentials or PII), avoid passing real passwords or secrets in commands, deny profile reuse unless you understand scope, restrict file-path access, require explicit consent for any operations that access local browser data, and enable logging/auditing of browser actions. If the vendor cannot clearly justify how profile and filesystem access is limited, treat this skill as high-risk and do not grant it access to real user data.

Like a lobster shell, security has layers — review code before you run it.

latestvk97dsnx78xbbknswcrq7frqsrh85kzk4
0downloads
0stars
1versions
Updated 3h ago
v1.0.0
MIT-0

Agent Browser Assistant

An intelligent browser control assistant providing browser automation, data scraping, and testing capabilities.

Use Cases

Opening web pages, clicking/typing/scrolling, taking screenshots/recordings, extracting web content, exporting table data, automated form filling, batch operations, scheduled tasks, login authentication, UI testing, regression testing.

Quick Start

Use the browser tool for all browser operations:

# Open a web page
browser(action="open", url="https://example.com")

# Take a screenshot
browser(action="screenshot")

# Click an element
browser(action="act", kind="click", ref="button-submit")

# Type text
browser(action="act", kind="type", ref="input-username", text="user@example.com")

# Scroll the page
browser(action="act", kind="scroll", y=500)

# Get a page snapshot
browser(action="snapshot")

Core Capabilities

1. Page Operations

OperationDescriptionExample
openOpen a specified URLaction="open", url="..."
snapshotGet page structureaction="snapshot"
screenshotTake a page screenshotaction="screenshot"
navigateNavigate to a URLaction="navigate", url="..."
closeClose a tabaction="close", targetId="..."

2. Element Interaction

Use the act operation for page interaction:

  • click: Click an element (ref: element reference)
  • type: Type text (ref: input reference, text: content)
  • press: Press a keyboard key (key: key name)
  • hover: Hover over an element
  • select: Select from a dropdown
  • fill: Fill a form (fields: field dictionary)
  • scroll: Scroll the page (x/y: coordinates)

3. Data Scraping

Extract data from web pages:

# Get a page snapshot to analyze structure
browser(action="snapshot")

# Extract table data - using selector
browser(action="act", kind="evaluate", selector="table.data", fn="Array.from(document.querySelectorAll('tr')).map(r => Array.from(r.querySelectorAll('td')).map(c => c.innerText))")

4. Automated Workflows

Automated form filling:

browser(action="act", kind="fill", fields=[
    {"ref": "input-email", "value": "user@example.com"},
    {"ref": "input-password", "value": "password123"}
])
browser(action="act", kind="click", ref="button-login")

Batch operations:

# Iterate through list items
for i in range(1, 6):
    browser(action="act", kind="click", ref=f"item-{i}")

5. Testing Capabilities

UI testing scenarios:

  • Regression Testing: Verify that page functionality works correctly
  • Performance Monitoring: Page load time
  • Element Existence Check: Verify that key elements are visible

Advanced Usage

Waiting for Page Load

browser(action="act", kind="wait", loadState="domcontentloaded", timeMs=5000)

Handling Dialogs

browser(action="dialog", kind="accept")  # Confirm
# or
browser(action="dialog", kind="dismiss")  # Cancel

File Upload

browser(action="upload", ref="input-file", paths=["C:/path/to/file.pdf"])

PDF Export

browser(action="pdf", path="C:/output/page.pdf")

Configuration Options

ParameterDescriptionDefault
profileBrowser profile"openclaw"
targetBrowser target"sandbox"
slowlySlow motion modefalse
timeoutMsTimeout duration30000

Common Selector Patterns

  • Button: button[type="submit"], #submit-btn
  • Input: input[name="email"], #username
  • Link: a[href*="login"]
  • Table: table.data tr
  • List: .item-list li

Notes

  1. Use snapshot to get page structure before performing element operations
  2. Dynamic content may require waiting for it to finish loading
  3. For logged-in state operations, use profile="user" to reuse the user's browser
  4. For large-scale data scraping, consider pagination to avoid timeouts

Comments

Loading comments...