crabbox

Run remote Linux Vitest and Docker/E2E test workloads via Crabbox.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/brikkoAI/brikko-studio --skill crabbox-brikkoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crabbox
Source: https://github.com/brikkoAI/brikko-studio/tree/main/packages/core/.agents/skills/crabbox
Command: npx skills add https://github.com/brikkoAI/brikko-studio --skill crabbox-brikkoai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual overhead of provisioning, configuring, and managing remote Linux environments for Brikko Studio's broad test suites, CI parity checks, Docker/E2E testing, and secrets validation, ensuring consistent, reproducible test runs without local environment setup.

Core Features & Use Cases

  • Default Blacksmith Testbox integration: Runs full and filtered Vitest test suites, CI parity checks, and Docker/E2E gates on pre-configured remote Linux boxes with automatic resource cleanup.
  • Multi-backend fallback support: Includes direct Blacksmith CLI and owned AWS/Hetzner fallback workflows if the default Crabbox path fails, minimizing test downtime.
  • Use Case: For example, when validating a cross-package code change for Brikko Studio, use this Skill to automatically run the full test suite on a remote Linux environment, collect results, and clean up resources without manual server management.

Quick Start

Use the crabbox skill to run the full Brikko Studio test suite on a remote Blacksmith Testbox and retrieve the test results.

Frequently Asked Questions about crabbox

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run Vitest test suites on a remote Linux environment without manual server setup?

You can run Vitest test suites on a remote Linux environment by using automated remote environment provisioning, which automatically handles server configuration, test execution, result collection, and resource cleanup.

What is the best way to automate CI parity checks for Docker and E2E testing remotely?

Automating CI parity checks for Docker and E2E testing remotely involves executing reproducible validation workloads on pre-configured Linux boxes, ensuring consistent test gates without local environment dependencies.

Can I use AWS or Hetzner as a fallback if the default Blacksmith Testbox integration fails during remote testing?

Yes, you can use direct Blacksmith CLI and owned AWS or Hetzner environments as multi-backend fallback workflows if the default remote testing path fails, minimizing test downtime.

Does remote Linux test automation handle resource cleanup automatically after a test run?

Yes, remote Linux test automation includes automatic resource cleanup via Testbox integrations, ensuring that provisioned environments and associated resources are removed after test execution and result collection.

How does secrets validation work during remote CI/CD test execution?

Secrets validation during remote CI/CD test execution works by applying reproducible validation workloads to the remote Linux environment, ensuring configuration parity and secure checks without local setup.