e2e

Automate end-to-end smoke testing of the Mycelium stack.

112|10|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/mycelium-io/mycelium --skill e2e-mycelium-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/mycelium-io/mycelium/tree/main/.claude/skills/e2e
Command: npx skills add https://github.com/mycelium-io/mycelium --skill e2e-mycelium-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end smoke testing of the Mycelium stack, including install verification, memory CRUD, search, coordination, and OpenClaw integration.

Core Features & Use Cases

  • Structured test phases that validate each subsystem of Mycelium from deployment to runtime coordination.
  • Deterministic outcomes with clear pass/fail criteria for each phase (health, memory, CLI negotiation, multi-session coordination, and OpenClaw).
  • Release-quality validation and regression checks for post-deploy assurance.

Quick Start

Run the structured end-to-end smoke tests against the live Mycelium stack.

Frequently Asked Questions about e2e

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

FAQPage Schema
How do I automate end-to-end smoke tests for the Mycelium stack?

You can automate end-to-end smoke tests for the Mycelium stack by running structured test phases against a live deployment, validating subsystems like memory, search, and coordination with deterministic pass or fail outcomes.

What is included in Mycelium post-deploy sanity checks?

Mycelium post-deploy sanity checks include structured test phases that validate installation, memory CRUD operations, CLI negotiation, multi-session coordination, and OpenClaw integration.

Do I need a live Mycelium deployment to run e2e regression testing?

Yes, you need a live or accessible Mycelium deployment to run e2e regression testing, as the skill validates runtime coordination and subsystems directly against the active stack.

Can I use this skill for release validation across Mycelium subsystems?

Yes, you can use this skill for release validation because it applies deterministic outcomes with clear failure criteria across install, memory, search, and OpenClaw integration phases.

What's the best way to validate OpenClaw integration after deployment?

The best way to validate OpenClaw integration is using structured e2e smoke tests that execute specific validation phases with clear logging and failure criteria against your live Mycelium stack.

Why does my Mycelium e2e test phase fail during multi-session coordination?

Your Mycelium e2e test phase fails during multi-session coordination when the deterministic criteria for runtime coordination are not met, with logs provided to identify the exact subsystem failure.