hiclaw-test

Run deterministic end-to-end tests for HiClaw Manager-Workers collaboration.

5.3k|652|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/agentscope-ai/HiClaw --skill hiclaw-test
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiclaw-test
Source: https://github.com/agentscope-ai/HiClaw/tree/main/tests/skills/hiclaw-test
Command: npx skills add https://github.com/agentscope-ai/HiClaw --skill hiclaw-test

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you reliably verify that HiClaw’s multi-agent Manager-Workers runtime installs correctly, passes functional tests, and provides actionable debug artifacts when tests hang or fail.

Core Features & Use Cases

  • End-to-end test cycle: Runs a full install → test → uninstall workflow to confirm core collaboration scenarios.
  • Targeted test execution: Supports running only install/uninstall steps or using an existing installation to skip rebuild time.
  • Hang diagnosis and debug exports: Exports debug logs and analyzes worker PHASE completion mention behavior to pinpoint root causes.
  • Use cases: Pre-merge CI/CD validation, issue diagnosis for stuck/hanging tests, and environment verification after configuration changes.

Quick Start

Run a complete HiClaw test cycle by creating ~/hiclaw-manager.env from hiclaw-manager.env.example and executing: set -a && . ~/hiclaw-manager.env && set +a && make test.

Frequently Asked Questions about hiclaw-test

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

FAQPage Schema
How do I troubleshoot a HiClaw multi-agent test that hangs during worker collaboration?

To troubleshoot a hanging multi-agent test, you can run a targeted test cycle to export debug logs and generate a hang analysis report that pinpoints root causes by examining worker PHASE completion behavior.

What's the best way to validate a multi-agent runtime in a CI/CD pipeline?

The best way to validate a multi-agent runtime in CI/CD is to execute a deterministic end-to-end install, test, and uninstall workflow that confirms core Manager-Workers collaboration scenarios and produces actionable debug artifacts.

Do I need Docker and specific environment variables to run end-to-end multi-agent tests?

Yes, you need Docker installed and a configured environment including HICLAW_LLM_API_KEY and optionally HICLAW_GITHUB_TOKEN to run end-to-end multi-agent tests and generate hang analysis reports.

Can I skip the installation rebuild step when running functional regression tests?

Yes, you can skip the rebuild time during functional regression testing by using an existing installation to run targeted test executions instead of completing the full install, test, and uninstall cycle.

Why does my multi-agent test fail during human intervention flows?

Multi-agent test failures during human intervention flows can be diagnosed by exporting debug logs from a full end-to-end test cycle, which analyzes worker interactions and hang behavior to identify the root cause.

How do I set up the environment to run a full multi-agent test cycle?

To set up the environment for a full multi-agent test cycle, create the manager environment file from the provided example, source it to load variables like HICLAW_LLM_API_KEY, and execute the test command.