ClawHub

TeamClaw Setup

v1.0.1

Install, configure, validate, or troubleshoot the TeamClaw OpenClaw plugin for virtual software-team workflows. Use when users want TeamClaw setup help, cont...

⭐ 0· 154·1 current·1 all-time
by@topcheer

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for topcheer/teamclaw-setup.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "TeamClaw Setup" (topcheer/teamclaw-setup) from ClawHub.
Skill page: https://clawhub.ai/topcheer/teamclaw-setup
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install teamclaw-setup

ClawHub CLI

Package manager switcher

npx clawhub@latest install teamclaw-setup
Security Scan
VirusTotalVirusTotal
Pending
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The skill's name, description, and included config snippets align with installing and validating TeamClaw. One minor discrepancy: the registry metadata lists no required binaries, but the instructions reference commands the user will need (npx, openclaw, curl, docker, kubectl). This is an omission in declared requirements rather than a functional mismatch with the stated purpose.
✓
Instruction Scope
SKILL.md confines itself to install/config/validation steps for TeamClaw: showing commands, minimal config snippets, health checks, and smoke tests. It does not instruct reading unrelated system files, requesting secrets, or sending data to unknown endpoints. It references network resources (npm, GitHub Container Registry) only as expected for installing packages and images.
✓
Install Mechanism
This is an instruction-only skill (no install spec, no code files), which is low risk. The guidance suggests using npx and openclaw CLI and points to ghcr.io for runtime images — these are reasonable for a plugin installer. Users should still exercise normal caution when running remote installers (npx).
✓
Credentials
The skill declares no required environment variables or credentials and the instructions do not ask for secrets. The only environment/network requirements are reachability of controller URLs, access to container registries, and presence of tooling (docker, kubectl) when those modes are chosen — all proportionate to the documented deployment modes.
✓
Persistence & Privilege
always is false, the skill is user-invocable, and model invocation is enabled (normal). The skill does not request permanent presence, nor does it instruct modifying other skills or system-wide settings.
Assessment
This skill is an instruction-only installer and appears coherent with its purpose. Before using it: 1) Note the SKILL.md expects tools like npx, openclaw, curl, docker, and kubectl — ensure you have the ones you need for your chosen install mode. 2) The recommended installer uses npx (downloads and runs an npm package); if you prefer, inspect the package or use the manual plugin path. 3) The runtime image comes from ghcr.io (container registry); ensure your environment can pull from that registry. 4) Follow the provided health-check and smoke-test commands to verify a safe, minimal installation. 5) If you need higher assurance, review the upstream GitHub repo and the npm package contents before running installers. Overall: coherent and expected for a TeamClaw setup guide.

Like a lobster shell, security has layers — review code before you run it.

Links

Homepagehttps://github.com/topcheer/teamclaw
Repositoryhttps://github.com/topcheer/teamclaw
Docshttps://github.com/topcheer/teamclaw/blob/main/INSTALL.md
latestvk9767xeger09bexha331p06vfd83v6rz
154downloads
0stars
2versions
Updated 1mo ago
v1.0.1
MIT-0
@topcheer
latest
Download

TeamClaw Setup

Guide users to the smallest working TeamClaw installation first, then expand.

Default workflow

  1. Prefer the guided installer first:

    npx -y @teamclaws/teamclaw install

  2. Use manual plugin install only when the user wants direct control:

    openclaw plugins install @teamclaws/teamclaw

    If the user explicitly wants the ClawHub package path, use:

    openclaw plugins install clawhub:@teamclaws/teamclaw

  3. Recommend controller + localRoles for the first successful run unless the user explicitly needs distributed or on-demand workers immediately.

  4. Read references/install-modes.md before generating config. Pick the smallest matching topology and reuse the provided snippets.

  5. Read references/validation-checklist.md before finishing. Always give the user:

    • one health-check command
    • one UI URL
    • one tiny smoke-test requirement
    • one or two likely failure checks for the chosen topology

Installation guidance

  • Start with a single machine and localRoles.

  • Keep TeamClaw taskTimeoutMs large for real model runs.

  • Keep OpenClaw agents.defaults.timeoutSeconds at least as large as the TeamClaw task window in seconds.

  • For docker or kubernetes, require a reachable workerProvisioningControllerUrl.

  • For docker, mention the published runtime image:

    ghcr.io/topcheer/teamclaw-openclaw:latest

What to produce

When helping a user, produce:

  1. the exact install command
  2. the minimal config snippet for the chosen topology
  3. the startup command
  4. the validation commands and first smoke-test task

Do not push users into distributed, Docker, or Kubernetes first unless they asked for it or already have the surrounding infrastructure ready.

Comments

Loading comments...