smithery/GGPrompts

integration

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

Installation

$ npx skills add smithery/GGPrompts --skill integration

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/GGPrompts.

npx skills add smithery/GGPrompts

Browse all from smithery/GGPrompts

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,531 B
  • docs SUMMARY.md 116 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.