Skill

integration

Guides integration of projects with TabzChrome terminals via Markdown links, HTML attributes, WebSocket, JS API, or Spawn API for dashboards, buttons, and CLI tools.

Html

Javascript

Websocket

developer-tools

cli-tools

npx claudepluginhub ggprompts/tabzchrome --plugin tabz

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Help users integrate their projects with TabzChrome terminals.

Supporting Assets

references/cli-websocket.mdreferences/html-integration.mdreferences/javascript-api.mdreferences/markdown-links.mdreferences/security.mdreferences/spawn-api.md

SKILL.md

Similar Skills

terminals

138

Spawns and manages terminal tabs via TabzChrome REST API for workers, git worktrees, parallel Claude sessions, and tmux orchestration.

3 files

tabz

pinchtab-dev

8.9k

Develops and contributes to PinchTab Go browser control server with React dashboard. Runs dev commands, unit/E2E tests, git workflow, checks, and PR checklists.

pinchtab-pinchtab

chrome-cdp

Connects to local Chrome browser via DevTools Protocol to list tabs, snap accessibility tree, eval JS, navigate, click elements, type text, and screenshot live pages. Use after user approval for authenticated web app debugging.

1 file

bopen-tools

Stats

Parent Repo Stars138

Parent Repo Forks10

Last CommitFeb 2, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

TabzChrome Integration

Help users integrate their projects with TabzChrome terminals.

When to Use

Creating project dashboards with terminal buttons in markdown
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
Markdown `tabz:` links	None	Project dashboards, docs in file viewer
HTML `data-terminal-command`	None	Static buttons on web 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: "Markdown Links"
        description: "tabz: protocol for project dashboards in file viewer"
      - 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
Markdown Links	`references/markdown-links.md`
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.