How do I install the Tabz Integration skill?

Run npx skillmds@latest add ggprompts/tabz-integration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Tabz Integration safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Tabz Integration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Tabz Integration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Tabz Integration?

GGPrompts (@ggprompts) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Tabz Integration by ggprompts — Agent Skill

Name: Tabz Integration
Author: GGPrompts

File contents

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.

---name: tabz-integrationdescription: Integrate projects with TabzChrome terminals via HTML attributes, WebSocket, JS API, or Spawn API---# TabzChrome IntegrationHelp 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 StartFirst, 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 broadcastChrome Extension │ ▼Sidepanel → Terminal Tabs```For security considerations on HTTPS sites, see `references/security.md`.

Frequently asked questions

Tabz Integration