Skill flagged — suspicious patterns detected

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

Lybic Sandbox

v0.1.3

Lybic Sandbox is a cloud sandbox built for agents and automation workflows. Think of it as a disposable cloud computer you can spin up on demand. Agents can perform GUI actions like seeing the screen, clicking, typing, and handling pop ups, which makes it a great fit for legacy apps and complex flows where APIs are missing or incomplete. It is designed for control and observability. You can monitor execution in real time, stop it when needed, and use logs and replay to debug, reproduce runs, and evaluate reliability. For long running tasks, iterative experimentation, or sensitive environments, sandboxed execution helps reduce risk and operational overhead.

0· 1.1k·0 current·0 all-time
bylybic@aenjoy

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for aenjoy/lybic-sandbox.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Lybic Sandbox" (aenjoy/lybic-sandbox) from ClawHub.
Skill page: https://clawhub.ai/aenjoy/lybic-sandbox
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: LYBIC_ORG_ID, LYBIC_API_KEY
Required binaries: pip3, python3
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 aenjoy/lybic-sandbox

ClawHub CLI

Package manager switcher

npx clawhub@latest install lybic-sandbox
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the requested capabilities: the skill controls Lybic sandboxes, performs GUI automation, runs code, copies files, and creates HTTP port mappings. Required env vars (LYBIC_ORG_ID, LYBIC_API_KEY) and python/pip requirements align with the Python SDK usage.
Instruction Scope
SKILL.md and examples instruct the agent to create sandboxes, execute arbitrary code/commands, download files from external URLs, and create public HTTP port mappings. These are powerful but expected for a sandbox controller; watch for examples that print mapping tokens or download arbitrary external content (which is expected but increases exposure).
Install Mechanism
Install uses Homebrew formulas for python3 and pipx (low-risk). The runtime docs also instruct 'pip install lybic' (PyPI). Minor inconsistency: the install metadata claims the pipx brew formula 'creates binaries: pip3', which is not the usual mapping (pipx typically provides 'pipx', not 'pip3'); this is likely a packaging/doc mismatch but not an obvious malware indicator.
Credentials
Only Lybic-specific credentials are required (LYBIC_ORG_ID, LYBIC_API_KEY); those are appropriate and proportionate to the skill's purpose. No unrelated secrets or system config paths are requested.
Persistence & Privilege
always is false and the skill doesn't request to modify other skills or system-wide settings. Autonomous invocation is allowed (default) which is normal for skills; no elevated persistence was requested.
Assessment
This skill appears to do what it says: control Lybic sandboxes via the official Python SDK. Before installing: 1) Treat LYBIC_API_KEY/LYBIC_ORG_ID like sensitive credentials — the skill can create and control sandboxes, run arbitrary code there, access networks, and expose services publicly; give it the minimal-permission API key needed and be ready to rotate/revoke keys. 2) Be cautious about examples that download arbitrary URLs or create public HTTP port mappings — these are expected features but can expose data or run untrusted content. 3) The install metadata has a small inconsistency (pipx listed as providing pip3) — verify installation commands on your platform before running them. 4) Verify the provenance of this package (source is listed as unknown) and, if you require higher assurance, obtain the SDK/publishers from an official Lybic release channel or your org's approved repository. If you plan to run sensitive workloads, review your network/isolation policy for Lybic sandboxes and avoid placing sensitive credentials or internal network access into sandboxes that are made public via port mappings.

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

Runtime requirements

🧫 Clawdis
Binspip3, python3
EnvLYBIC_ORG_ID, LYBIC_API_KEY

Install

Install python3 (brew)
Bins: python3
brew install python3
Install Pip (brew)
Bins: pip3
brew install pipx
latestvk97bk5n1jddsvv7amxgx93d7dx80w5j5
1.1kdownloads
0stars
4versions
Updated 51m ago
v0.1.3
MIT-0

Lybic Sandbox Control Skill

You are an expert at controlling Lybic cloud sandboxes using the Lybic Python SDK.

Your Capabilities

You can help users interact with Lybic cloud sandboxes to:

  1. Manage Sandboxes

    • Create sandboxes (Windows/Linux/Android)
    • List, get details, and delete sandboxes
    • Monitor sandbox state and lifecycle
  2. Perform GUI Automation

    • Desktop (Windows/Linux): Mouse clicks, keyboard input, scrolling, dragging
    • Mobile (Android): Touch, swipe, long press, app management
    • Take screenshots for visual feedback
  3. Execute Code and Commands

    • Run Python, Node.js, Go, Rust, Java code
    • Execute shell commands and scripts
    • Handle stdin/stdout/stderr with base64 encoding
  4. Manage Files

    • Download files from URLs into sandbox
    • Copy files within sandbox or between locations
    • Read and write files in sandbox
  5. Network Operations

    • Create HTTP port mappings
    • Forward sandbox ports to public URLs
    • Enable external access to sandbox services
  6. Project Management

    • Create and organize projects
    • Manage sandboxes within projects
    • Track organization usage

Prerequisites

The Lybic Python SDK must be installed:

pip install lybic

Users need Lybic credentials set via environment variables:

  • LYBIC_ORG_ID - Organization ID
  • LYBIC_API_KEY - API key

Of course, these two parameters can also be manually specified and passed to the client.

import asyncio
from lybic import LybicClient, LybicAuth

async def main():
    async with LybicClient(LybicAuth(
            org_id="your_org_id", # Lybic organization ID
            api_key="your_api_key"
         )) as client:
        # Your code here
        pass

Code Guidelines

1. Always use async/await pattern

import asyncio
from lybic import LybicClient

async def main():
    async with LybicClient() as client:
        # Your code here
        pass

if __name__ == '__main__':
    asyncio.run(main())

2. Use proper error handling

try:
    result = await client.sandbox.create(name="test", shape="beijing-2c-4g-cpu-linux")
    print(f"Created: {result.id}")
except Exception as e:
    print(f"Error: {e}")

3. Handle base64 encoding for process I/O

import base64

# For stdin
code = "print('hello')"
stdin_b64 = base64.b64encode(code.encode()).decode()

# For stdout/stderr
result = await client.sandbox.execute_process(...)
output = base64.b64decode(result.stdoutBase64 or '').decode()

4. Use fractional coordinates for GUI actions

# Recommended: Resolution-independent
action = {
    "type": "mouse:click",
    "x": {"type": "/", "numerator": 1, "denominator": 2},  # 50%
    "y": {"type": "/", "numerator": 1, "denominator": 2},  # 50%
    "button": 1
}

# Alternative: Absolute pixels (less portable)
action = {
    "type": "mouse:click",
    "x": {"type": "px", "value": 500},
    "y": {"type": "px", "value": 300},
    "button": 1
}

Common Patterns

Pattern 1: Create sandbox and run code

import asyncio
import base64
from lybic import LybicClient

async def run_code_in_sandbox():
    async with LybicClient() as client:
        # Create linux based code sandbox
        sandbox = await client.sandbox.create(
            name="code-runner",
            shape="beijing-2c-4g-cpu-linux"
        )
        
        # Execute code
        code = "print('Hello from sandbox')"
        result = await client.sandbox.execute_process(
            sandbox.id,
            executable="python3",
            stdinBase64=base64.b64encode(code.encode()).decode()
        )
        
        print(base64.b64decode(result.stdoutBase64).decode())
        
        # Cleanup
        await client.sandbox.delete(sandbox.id)

asyncio.run(run_code_in_sandbox())

Pattern 2: GUI automation with screenshot

import asyncio
from lybic import LybicClient

async def automate_gui():
    async with LybicClient() as client:
        sandbox_id = "SBX-xxxx"
        
        # Take initial screenshot
        url, img, _ = await client.sandbox.get_screenshot(sandbox_id)
        img.show()
        
        # Click at center
        await client.sandbox.execute_sandbox_action(
            sandbox_id,
            action={
                "type": "mouse:click",
                "x": {"type": "/", "numerator": 1, "denominator": 2},
                "y": {"type": "/", "numerator": 1, "denominator": 2},
                "button": 1
            }
        )
        
        # Type text
        await client.sandbox.execute_sandbox_action(
            sandbox_id,
            action={
                "type": "keyboard:type",
                "content": "Hello!"
            }
        )
        
        # Press Enter
        await client.sandbox.execute_sandbox_action(
            sandbox_id,
            action={
                "type": "keyboard:hotkey",
                "keys": "Return"
            }
        )

asyncio.run(automate_gui())

Pattern 3: Download file and process

import asyncio
import base64
from lybic import LybicClient
from lybic.dto import FileCopyItem, HttpGetLocation, SandboxFileLocation

async def download_and_process():
    async with LybicClient() as client:
        sandbox_id = "SBX-xxxx"
        
        # Download file
        await client.sandbox.copy_files(
            sandbox_id,
            files=[
                FileCopyItem(
                    id="dataset",
                    src=HttpGetLocation(url="https://example.com/data.csv"),
                    dest=SandboxFileLocation(path="/tmp/data.csv")
                )
            ]
        )
        
        # Process with Python
        code = """
import pandas as pd
df = pd.read_csv('/tmp/data.csv')
print(df.describe())
"""
        result = await client.sandbox.execute_process(
            sandbox_id,
            executable="python3",
            stdinBase64=base64.b64encode(code.encode()).decode()
        )
        
        print(base64.b64decode(result.stdoutBase64).decode())

asyncio.run(download_and_process())

Action Reference

Mouse Actions (Computer Use)

# Click
{"type": "mouse:click", "x": {...}, "y": {...}, "button": 1}  # 1=left, 2=right

# Double-click
{"type": "mouse:doubleClick", "x": {...}, "y": {...}, "button": 1}

# Move
{"type": "mouse:move", "x": {...}, "y": {...}}

# Drag
{"type": "mouse:drag", "startX": {...}, "startY": {...}, "endX": {...}, "endY": {...}}

# Scroll
{"type": "mouse:scroll", "x": {...}, "y": {...}, "stepVertical": -5, "stepHorizontal": 0}

Keyboard Actions (Computer Use)

# Type text
{"type": "keyboard:type", "content": "Hello, World!"}

# Hotkey
{"type": "keyboard:hotkey", "keys": "ctrl+c"}  # Copy
{"type": "keyboard:hotkey", "keys": "Return"}  # Enter
{"type": "keyboard:hotkey", "keys": "ctrl+shift+s"}  # Save as

Touch Actions (Mobile Use)

# Tap
{"type": "touch:tap", "x": {...}, "y": {...}}

# Long press
{"type": "touch:longPress", "x": {...}, "y": {...}, "duration": 2000}

# Swipe
{"type": "touch:swipe", "x": {...}, "y": {...}, "direction": "up", "distance": {...}}

# Android buttons
{"type": "android:back"}
{"type": "android:home"}

App Management (Mobile Use)

# Start app
{"type": "os:startApp", "packageName": "com.android.chrome"}
{"type": "os:startAppByName", "name": "Chrome"}

# Close app
{"type": "os:closeApp", "packageName": "com.android.chrome"}
{"type": "os:closeAppByName", "name": "Chrome"}

# List apps
{"type": "os:listApps"}

Common Actions

# Screenshot
{"type": "screenshot"}

# Wait
{"type": "wait", "duration": 3000}  # milliseconds

# Task status
{"type": "finished", "message": "Task completed"}
{"type": "failed", "message": "Error occurred"}

Best Practices

  1. Use fractional coordinates: More portable across different screen resolutions
  2. Take screenshots: Help verify GUI state before and after actions
  3. Handle errors: Always wrap API calls in try-except blocks
  4. Clean up resources: Delete sandboxes when done to avoid charges
  5. Base64 encode I/O: Remember stdin/stdout use base64 encoding
  6. Check exit codes: Use exitCode to verify process success (0 = success)

Sandbox Shapes

Lybic determines the operating system type of the cloud sandbox through the shape parameter when creating the sandbox.

  • Windows: beijing-2c-4g-cpu
  • Linux: beijing-2c-4g-cpu-linux
  • Android: acep-shenzhen-enhanced or acep-wenzhou-common-pro

Troubleshooting

  1. Sandbox not ready: Wait longer after creation, check status with get()
  2. Action fails: Verify coordinates are within screen bounds
  3. Process timeout: Long-running processes need special handling (see docs)
  4. File not found: Ensure paths exist in sandbox before accessing
  5. Import errors: Verify package is pre-installed or install with pip3 install

When to Use This Skill

Use this skill when users need to:

  • Run code in an isolated cloud environment
  • Automate GUI applications (desktop or mobile)
  • Test web services in a sandbox
  • Process data in a clean environment
  • Interact with applications remotely
  • Perform browser automation
  • Test mobile apps on Android

Documentation

For detailed API reference:

Remember

  • Always check if credentials are set before running code
  • Provide clear explanations of what the code does
  • Show complete working examples
  • Handle errors gracefully
  • Clean up resources (delete sandboxes) when appropriate
  • Take screenshots to verify GUI actions
  • Use async/await consistently

Comments

Loading comments...