One-click install
npx skills add https://github.com/mk-knight23/AI-ASSISTANT-CURSOR --skill claw-ecosystem
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: claw-ecosystem
Source: https://github.com/mk-knight23/AI-ASSISTANT-CURSOR/tree/main/skills/claw-ecosystem
Command: npx skills add https://github.com/mk-knight23/AI-ASSISTANT-CURSOR --skill claw-ecosystem

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Manually managing five separate Claw ecosystem gateway services (each with unique runtimes, commands, and configurations) is time-consuming and prone to human error, especially when working on projects that rely on all services running simultaneously.

Core Features & Use Cases

  • Unified Fleet Management: Start, stop, check status, or restart all five Claw gateways (OpenClaw, ZeroClaw, NanoBot, PicoClaw, NanoClaw) with a single command, or manage individual services as needed.
  • Built-in Troubleshooting: Includes guidance for resolving common issues like port conflicts, configuration errors, container runtime failures, and API key misconfigurations for each gateway.
  • Use Case: If you are developing a feature that requires all Claw services to be running, you can spin up the entire fleet in one step instead of running 5 separate startup commands, and verify all services are healthy with a single status check.

Quick Start

Use the claw-ecosystem skill to start all Claw ecosystem gateways and confirm they are running without errors.

Frequently Asked Questions about claw-ecosystem

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

FAQPage Schema
How do I manage multiple gateway services without running separate start commands for each?

Multi-service control is achieved by providing unified fleet management for all gateway services. You can start, stop, check status, or restart the entire ecosystem with a single command instead of manually handling each service.

What is the best way to troubleshoot runtime and configuration errors across a fleet of gateway services?

Runtime troubleshooting for gateway fleets is handled with built-in guidance for resolving port conflicts, API key misconfigurations, and container runtime failures. This centralized approach eliminates manual debugging across individual services.

Can I restart just one specific gateway service if the rest of the fleet is already running?

Individual gateway services can be managed as needed without affecting the rest of the fleet. You can issue a targeted restart for a single service while the other ecosystem components continue running uninterrupted.

How do I verify that all services in a multi-service gateway ecosystem are healthy and running?

You can verify fleet health with a single unified status check command. This validates that all five heterogeneous gateway services are running simultaneously without errors, replacing the need to check each service individually.

Why does managing heterogeneous gateway services manually lead to configuration errors?

Manually managing heterogeneous gateways causes errors because each service has unique runtimes, commands, and configurations. Coordinating these diverse services by hand is time-consuming and prone to human error during simultaneous operations.

Does claw-ecosystem provide unified log access for all components in the gateway fleet?

Unified log access for all fleet components is provided by the claw-ecosystem skill. This allows you to retrieve and review logs from all five gateway services through a single centralized interface for efficient troubleshooting.