tabtab
Use TabTab to run AI-powered tasks in a sandboxed multi-agent environment. Supported capabilities: - General agent: open-ended tasks, writing, research, summarisation - Data analysis: upload CSV / Excel files, run analytics, generate insights - Data collection: web scraping and browser automation to collect structured data - Chart generation: produce charts and visualisations from data - Deep research: long-form research with web search and synthesised reports - Database Q&A: natural-language to SQL queries against connected databases - Slide generation: create PowerPoint presentations - Web / HTML generation: produce web pages or UI prototypes Interact via REST API: create tasks, poll status, stream event logs, terminate tasks, and download sandbox output.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/bjwswang/tabtabTabTab Skill
Overview
The TabTab OpenPlatform exposes REST endpoints under /open/apis/v1/ that let you drive TabTab's multi-agent platform programmatically. Every request must carry an API Key in the Authorization header.
Authorization: Bearer sk-<32-hex-chars>
The API Key is obtained from the KMS page(https://tabtabai.com/api-key) in TabTab settings and stored as environment variable TABTAB_API_KEY.
Configuration — Set environment variables
Recommended: write to scripts/env (persists across sessions, not in shell history)
cat > "$(dirname "$0")/scripts/env" <<'EOF'
TABTAB_API_KEY="sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
TABTAB_BASE_URL="https://tabtabai.com" # optional
EOF
chmod 600 "$(dirname "$0")/scripts/env"
All scripts automatically source scripts/env on startup if the file exists — no further setup needed.
Security:
chmod 600ensures only you can read the file. Addscripts/envto.gitignoreto prevent accidental commits:echo "skills/tabtab/scripts/env" >> .gitignore
Alternative: export in shell session (lost on terminal close)
export TABTAB_API_KEY="sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
export TABTAB_BASE_URL="https://tabtabai.com" # optional
Warning: Commands typed with the key inline (e.g.
export TABTAB_API_KEY="sk-...") are saved to shell history (.bash_history/.zsh_history). Prefer thescripts/envfile approach above, or set the key via a password manager / secrets tool that avoids writing to history.
Verify configuration
echo "BASE_URL : ${TABTAB_BASE_URL:-https://tabtabai.com}"
echo "API_KEY : ${TABTAB_API_KEY:0:8}…" # print only first 8 chars for safety
# Verify API key is valid before proceeding — stop if this fails
bash scripts/hello.sh
| Variable | Required | Description |
|---|---|---|
TABTAB_API_KEY | ✅ | API Key in sk-… format obtained from KMS page |
TABTAB_BASE_URL | ❌ | Base URL of TabTab instance (default: https://tabtabai.com) |
If TABTAB_API_KEY is empty, all scripts will immediately exit with an error.
Required tools
The scripts depend on the following tools — confirm they are installed from trusted packages:
| Tool | Purpose |
|---|---|
curl | HTTP requests to the API |
jq | JSON parsing and transformation |
stat | File size check before upload (upload-files.sh) |
Step 0 — Verify connectivity
Check API Key validity before proceeding:
bash scripts/hello.sh
Expected (200):
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-bjwswang-tabtab": {
"enabled": true,
"auto_update": true
}
}
}