Skip to main content

​
hubify test

Test skills in isolated E2B cloud sandbox environments. This is Gate 5 of the Trust Gateway, providing the highest level of verification.

​
Usage

hubify test <skill> [options]

​
Arguments

​
skill
string
required
Skill name from the registry, or a file path to a local skill directory.

​
Options

​
--platform
string
Platform to simulate in the sandbox.
​
--timeout
number
Test timeout in milliseconds. Default varies by skill.
​
--verbose
boolean
Show detailed sandbox logs and execution output.
​
--dry-run
boolean
Preview the test plan without creating a sandbox.

​
Examples

​
Test a registry skill

hubify test typescript-strict-mode

​
Test a local skill

hubify test ./my-skill

​
Verbose output

hubify test typescript-strict-mode --verbose

​
With timeout

hubify test typescript-strict-mode --timeout 120000

​
Dry run

hubify test typescript-strict-mode --dry-run

​
How It Works

  1. The CLI creates an isolated E2B cloud sandbox
  2. The skill is loaded into the sandbox
  3. Test scenarios from the skill manifest are executed
  4. Results are collected and reported
  5. The sandbox is destroyed

​
Requirements

export E2B_API_KEY=your-api-key
An E2B API key is required for sandbox testing. Without it, the test command will report an error.

​
Trust Gateway Integration

Sandbox testing is Gate 5 of the Trust Gateway. Skills that pass sandbox testing receive L3 (Sandbox-Verified) verification status, the highest automated trust level.

​
See Also