← Back to Skills Marketplace
avalon-467

TeamClaw

by hou xinyuan · GitHub ↗ · v0.1.3
cross-platform ⚠ suspicious
450
Downloads
0
Stars
1
Active Installs
11
Versions
Install in OpenClaw
/install teamclaw
Description
A high-performance Agent subsystem for complex multi-agent orchestration. It provides a visual workflow canvas (OASIS) to coordinate OpenClaw agents, automat...
Usage Guidance
This package implements a full multi-agent orchestration platform (web UI, bots, scheduler, public tunnel) and matches its description — but several red flags mean you should not install it blindly: - Metadata mismatch: the registry says 'no required env vars' but the code and SKILL.md require many secrets (LLM_API_KEY, OPENCLAW_API_KEY, INTERNAL_TOKEN, TELEGRAM/QQ secrets). Treat that inconsistency as a transparency issue. - Highly privileged token: INTERNAL_TOKEN is used by bots to call the system as arbitrary users (INTERNAL_TOKEN:username:...). Do NOT provide an INTERNAL_TOKEN unless you fully trust the code and run it in an isolated environment. - Auto-downloads & tunneling: scripts claim to auto-download cloudflared and bark-server and can expose the service publicly. Verify exactly which URLs the scripts download from (inspect scripts/tunnel.py, packaging/launcher.sh, build scripts) and prefer running behind a firewall or in a disposable VM/container. - Filesystem access: the service will read local files such as an OpenClaw sessions.json and write .env, logs, and user_data. Provide only paths you are comfortable exposing to the service. - Prompt-injection artifact: SKILL.md contains detected unicode-control characters. Open the raw file and ensure there are no hidden control characters that could affect parsers or cause unexpected behavior. Practical next steps before installing: 1. Review the repository source locally (especially scripts/tunnel.py, selfskill/scripts/*, run.sh, launcher.py) to see what is downloaded and what URLs are used. 2. Run initially in an isolated VM or container with no outbound network access (or with controlled egress) to inspect behavior. 3. Do not set INTERNAL_TOKEN or any admin keys until you are confident of the code. If you must test bots, create a throwaway INTERNAL_TOKEN limited to a test account or run without bot integrations. 4. If you plan to expose the service, require strong UI authentication, limit public exposure to a reverse proxy with access controls, and rotate any keys/passwords you use during testing. If you want, I can: (A) list the specific files to inspect first (scripts/tunnel.py, selfskill/scripts/run.sh, packaging/launcher.py, chatbot/setup.py), or (B) scan the provided tunnel and downloader scripts for download URLs and extraction logic.
Capability Analysis
Type: OpenClaw Skill Name: teamclaw Version: 0.1.3 TeamClaw is a comprehensive multi-agent orchestration platform that provides a visual workflow canvas (OASIS), social bot integrations (Telegram/QQ), and computer use capabilities. It features a robust set of MCP tools for command execution (mcp_commander.py), file management (mcp_filemanager.py), and network access via Cloudflare Tunnels (scripts/tunnel.py). While the bundle includes high-risk capabilities such as remote command execution and automated binary downloads (e.g., bark-server from GitHub in scripts/launcher.py), these are clearly aligned with its stated purpose of enabling complex agent orchestration and computer use. The implementation demonstrates security awareness through features like command whitelisting, path traversal protection, user-level isolation, and SHA-256 password hashing.
Capability Assessment
Purpose & Capability
The code and instructions implement a multi-agent orchestration system, OASIS forum, web UI, Telegram/QQ bots, and a Cloudflare tunnel exactly as the description says — so the capability set aligns with the name/description. However the registry metadata claims no required environment variables while SKILL.md and the code clearly require/expect many secrets (LLM_API_KEY, OPENCLAW_API_KEY/OPENCLAW_SESSIONS_FILE, INTERNAL_TOKEN, TELEGRAM/QQ tokens, PUBLIC_DOMAIN, etc.). That mismatch reduces transparency and is unexpected.
Instruction Scope
SKILL.md and the included scripts instruct the agent to: write/modify .env, create user accounts, read local OpenClaw sessions.json (path requested explicitly), start long-running services, and optionally expose the UI publicly via Cloudflare tunnels. Instructions also discuss auto-downloading binaries (bark-server, cloudflared) and starting background processes. These are within the stated purpose but significantly broaden runtime scope (filesystem reads, persistent services, network egress, and public exposure). The SKILL.md also contains detected prompt-injection artifacts (unicode-control-chars), indicating the documentation itself may include hidden control characters — review the raw file.
Install Mechanism
There is no formal install spec in the registry, but multiple scripts (e.g., scripts/tunnel.py, launcher.py, run.sh) claim to auto-download binaries like cloudflared and a bark-server. Auto-downloading and extracting executables at first-run is higher risk because the download sources/URLs are not declared in the metadata. The repository includes many files so code will be written to disk and launched as services if you run the provided scripts.
Credentials
The skill expects several high-privilege secrets: LLM provider API key(s), OPENCLAW_API_KEY, INTERNAL_TOKEN, TELEGRAM_BOT_TOKEN, QQ credentials, and possibly a PUBLIC_DOMAIN value. These are plausible for the advertised functionality, but INTERNAL_TOKEN is effectively an admin-level token that the bots use to impersonate users (format INTERNAL_TOKEN:username:TG). Providing INTERNAL_TOKEN grants broad authority to call the system as arbitrary users; this is high-risk and must be treated as sensitive. Registry metadata claiming 'none' for required env vars is inconsistent with the runtime requirements.
Persistence & Privilege
The package runs persistent background services (FastAPI/Flask endpoints, scheduler, bot processes) when started via run.sh / launcher.py. The registry flags do not set always:true, so it won't be force-included automatically, but installing/starting it will create long-lived processes and open ports (and the scripts can expose them publicly). The skill does not appear to modify other skills' configs, but it does write .env and log files in the project tree and can download binaries.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install teamclaw
  3. After installation, invoke the skill by name or use /teamclaw
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.3
- Introduced a new frontend structure with dedicated static JS/CSS and HTML templates. - Significant updates to core modules: scheduler, experts, agent, and engine files. - Enhanced and refactored Web UI with a more modular static/templating approach. - Improvements and corrections to documentation including README, SKILL.md, and OASIS_GUIDE.md. - Added orchestration logic and expanded base system prompt data. - Expanded project with 5 new files for frontend assets and templates.
v0.1.2
TeamClaw v0.1.2 - Added OASIS_GUIDE.md, providing additional documentation for the OASIS workflow. - Updated setup, launcher, and script logic to improve clarity about headless/interactive startup and bot integration (Telegram/QQ) handling. - SKILL.md majorly revised: now emphasizes order of configuration (setup → configure → add-user), requirements for user account creation before first launch, and how to avoid interactive script blocking in production. - Improved documentation for Bark push, Telegram and QQ bots: clarifies required environment variables and startup modes. - Various minor documentation corrections and clarifications in configuration, API, and feature explanations.
v0.1.1
safety update for skill md and env setting
v0.1.0
Initial public release of TeamClaw — a multi-agent orchestration and workflow platform. - Introduces OASIS: real-time visual multi-agent workflow orchestration with web UI. - Supports major LLM backends (DeepSeek, OpenAI, Gemini, Claude, Anthropic, Ollama) and TTS options. - Integrates with social platforms (Telegram, QQ) for bot control. - Provides easy remote/public secure access via Cloudflare Tunnel. - Includes agent chat API (OpenAI-compatible), task scheduling, and push notification system. - Deployment managed by simple non-interactive scripts for setup, user management, and configuration.
v1.0.6
TeamClaw 1.0.6 Changelog - Removed temporary file `README_tmp.html` from the repository. - No changes to functionality or user-facing features.
v1.0.5
description and skill md update
v1.0.4
https://github.com/Avalon-467/Teamclaw - **Conversational Agent**: A LangGraph-based multi-tool AI assistant supporting streaming/non-streaming conversations - **OASIS Forum**: A multi-expert parallel discussion/execution engine for orchestrating multiple agents - **Scheduled Tasks**: An APScheduler-based task scheduling center
v1.0.3
A high-performance Agent subsystem designed for complex multi-agent orchestration (OASIS), visual multi-agent workflow orchestration, automated computer use tasks, and real-time visual monitoring via a dedicated Web UI.
v1.0.2
Overview Teamclaw is a multifunctional AI Agent service providing: Conversational Agent: A multi-tool AI assistant based on LangGraph that supports streaming/non-streaming conversations OASIS Forum: A multi-expert parallel discussion/execution engine that orchestrates collaboration among multiple Agents Scheduled Tasks: A task scheduling center based on APScheduler Bark Push: Mobile push notifications Web UI Frontend: A complete chat interface
v1.0.1
Initial release of Teamclaw, a multi‑agent orchestration subsystem. Introduces visual workflow editing for multi‑agent tasks. OASIS engine ensures stable and efficient orchestration of agents. Real‑time Web UI for monitoring and management.
v1.0.0
Visual Workflow Editing: Intuitive UI for designing and managing multi‑agent workflows. High‑Performance OASIS Engine: Stable, efficient orchestration of multiple agents at scale. Real‑Time Web Monitoring: Transparent execution tracking and interactive management via browser.
Metadata
Slug teamclaw
Version 0.1.3
License
All-time Installs 1
Active Installs 1
Total Versions 11
Frequently Asked Questions

What is TeamClaw?

A high-performance Agent subsystem for complex multi-agent orchestration. It provides a visual workflow canvas (OASIS) to coordinate OpenClaw agents, automat... It is an AI Agent Skill for Claude Code / OpenClaw, with 450 downloads so far.

How do I install TeamClaw?

Run "/install teamclaw" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is TeamClaw free?

Yes, TeamClaw is completely free (open-source). You can download, install and use it at no cost.

Which platforms does TeamClaw support?

TeamClaw is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created TeamClaw?

It is built and maintained by hou xinyuan (@avalon-467); the current version is v0.1.3.

💬 Comments