Run any Skill in Manus with one click

Get Started

tabz-integration

Stars145

Forks10

UpdatedJanuary 18, 2026 at 05:47

Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

GGPrompts

GGPrompts/TabzChrome

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Computer Occupations, All OtherComputer and Mathematical Occupations·SOC 15-1299

File Explorer

6 files

SKILL.md

readonly

name	tabz-integration
description	Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API
user-invocable	true

TabzChrome Integration

Help users integrate their projects with TabzChrome terminals.

When to Use

Adding "Run in Terminal" buttons to web pages
Creating CLI tools that queue commands to TabzChrome
Building prompt libraries with fillable templates
Programmatically spawning terminal tabs

Integration Methods

Method	Auth	Best For
HTML `data-terminal-command`	None	Static buttons on docs/tool pages
WebSocket + websocat	File token	CLI/tmux workflows
WebSocket + JS	API token	Prompt libraries, web apps
POST /api/spawn	Token	Creating new terminal tabs

Quick Start

First, ask which integration the user needs:

questions:
  - question: "Which TabzChrome integration methods do you need?"
    header: "Integration"
    multiSelect: true
    options:
      - label: "HTML Buttons"
        description: "data-terminal-command for 'Run in Terminal' buttons"
      - label: "CLI/Scripts"
        description: "WebSocket via websocat for shell scripts"
      - label: "Web App JS"
        description: "JavaScript WebSocket for prompt libraries"
      - label: "Spawn API"
        description: "POST /api/spawn to create new tabs"

Then provide the relevant reference:

Selection	Reference
HTML Buttons	`references/html-integration.md`
CLI/Scripts	`references/cli-websocket.md`
Web App JS	`references/javascript-api.md`
Spawn API	`references/spawn-api.md`

Authentication Summary

Context	Method
CLI / Scripts	`TOKEN=$(cat /tmp/tabz-auth-token)`
Extension Settings	Click "API Token" → "Copy Token"
External web pages	User pastes token (stored in localStorage)

Architecture Overview

Web Page / CLI / App
        │
        ▼
TabzChrome Backend (localhost:8129)
        │
        ▼ WebSocket broadcast
Chrome Extension
        │
        ▼
Sidepanel → Terminal Tabs

For security considerations on HTTPS sites, see references/security.md.

More from this repository

same repository

integration

GGPrompts/TabzChrome

Integrate projects with TabzChrome terminals via Markdown links, HTML attributes, WebSocket, JS API, or Spawn API

2026-03-03145

terminals

GGPrompts/TabzChrome

Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.

2026-01-22145

browser

GGPrompts/TabzChrome

Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.

2026-01-22145

tabz-terminals

GGPrompts/TabzChrome

Spawn and manage terminal tabs via TabzChrome REST API. Use when spawning workers, creating terminals programmatically, setting up worktrees for parallel work, or crafting prompts for Claude workers.

2026-01-21145

tabz-browser

GGPrompts/TabzChrome

Browser automation via 70 tabz MCP tools. Use when taking screenshots, filling forms, debugging network requests, testing responsive design, or using text-to-speech notifications.

2026-01-19145

tabz-development

GGPrompts/TabzChrome

Patterns for building and debugging TabzChrome itself. Use when working on Terminal.tsx, xterm.js integration, WebSocket I/O, resize handling, or any TabzChrome extension/backend code.

2026-01-16145

TabzChrome Integration

Help users integrate their projects with TabzChrome terminals.

When to Use

Adding "Run in Terminal" buttons to web pages

Creating CLI tools that queue commands to TabzChrome

Building prompt libraries with fillable templates

Programmatically spawning terminal tabs

Integration Methods

Method

Auth

Best For

HTML data-terminal-command

None

Static buttons on docs/tool pages

WebSocket + websocat

File token

CLI/tmux workflows

WebSocket + JS

API token

Prompt libraries, web apps

POST /api/spawn

Token

Creating new terminal tabs

Quick Start

First, ask which integration the user needs:

questions: - question: "Which TabzChrome integration methods do you need?" header: "Integration" multiSelect: true options: - label: "HTML Buttons" description: "data-terminal-command for 'Run in Terminal' buttons" - label: "CLI/Scripts" description: "WebSocket via websocat for shell scripts" - label: "Web App JS" description: "JavaScript WebSocket for prompt libraries" - label: "Spawn API" description: "POST /api/spawn to create new tabs"

Then provide the relevant reference:

Selection

Reference

HTML Buttons

references/html-integration.md

CLI/Scripts

references/cli-websocket.md

Web App JS

references/javascript-api.md

Spawn API

references/spawn-api.md

Authentication Summary

Context

Method

CLI / Scripts

TOKEN=$(cat /tmp/tabz-auth-token)

Extension Settings

Click "API Token" → "Copy Token"

External web pages

User pastes token (stored in localStorage)

Architecture Overview

Web Page / CLI / App │ ▼ TabzChrome Backend (localhost:8129) │ ▼ WebSocket broadcast Chrome Extension │ ▼ Sidepanel → Terminal Tabs

For security considerations on HTTPS sites, see references/security.md.