How do I install the Terminals skill?

Run npx skillmds@latest add ggprompts/terminals 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 Terminals safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Terminals?

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 Terminals free to use?

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

Who published Terminals?

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

Terminals by ggprompts — Agent Skill

Name: Terminals
Author: GGPrompts

File contents

TabzChrome Terminal Management

Spawn terminals, manage workers, and orchestrate parallel Claude sessions.

Spawn API

TOKEN=$(cat /tmp/tabz-auth-token)
curl -X POST http://localhost:8129/api/spawn \
  -H "Content-Type: application/json" \
  -H "X-Auth-Token: $TOKEN" \
  -d '{"name": "Worker", "workingDir": "~/projects", "command": "claude"}'

Response:

{
  "success": true,
  "terminalId": "ctt-default-abc123",
  "tmuxSession": "ctt-default-abc123"
}

Spawn Options

Field	Type	Default	Description
`name`	string	"Claude Terminal"	Tab display name
`workingDir`	string	`$HOME`	Starting directory
`command`	string	-	Command to run after spawn
`profileId`	string	default	Profile for appearance

Parallel Workers with Worktrees

# Create isolated worktree (bd handles beads redirect automatically)
bd worktree create feature-branch

# Spawn worker there with BEADS_WORKING_DIR for MCP tools
PROJECT_DIR=$(pwd)
curl -X POST http://localhost:8129/api/spawn \
  -H "Content-Type: application/json" \
  -H "X-Auth-Token: $TOKEN" \
  -d "{\"name\": \"Feature Worker\", \"workingDir\": \"../feature-branch\", \"command\": \"BEADS_WORKING_DIR=$PROJECT_DIR claude\"}"

Key: BEADS_WORKING_DIR tells the beads MCP server where to find the database. Point it to the main repo, not the worktree.

Worker Prompts

Keep prompts simple - workers are vanilla Claude:

Fix the pagination bug in useTerminalSessions.ts around line 200.
Run tests when done: npm test
Close the issue: bd close TabzChrome-abc --reason="done"

Avoid prescriptive step-by-step pipelines. Let Claude work naturally.

Worker Management

List Workers

curl -s http://localhost:8129/api/agents | jq '.data[]'

Find by Name

curl -s http://localhost:8129/api/agents | jq -r '.data[] | select(.name == "V4V-ct9")'

Get Session ID

SESSION=$(curl -s http://localhost:8129/api/agents | jq -r '.data[] | select(.name == "V4V-ct9") | .id')

Kill Worker

curl -s -X DELETE "http://localhost:8129/api/agents/$SESSION" \
  -H "X-Auth-Token: $TOKEN"

Send Prompt via tmux

tmux send-keys -t "$SESSION" -l "Your prompt here"
sleep 0.5
tmux send-keys -t "$SESSION" Enter

References

See references/ for details:

spawn-api.md - Full API reference
worktree-setup.md - Git worktree patterns
worker-prompts.md - Prompt crafting guidelines

---name: terminalsdescription: 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.---# TabzChrome Terminal ManagementSpawn terminals, manage workers, and orchestrate parallel Claude sessions.## Spawn API```bashTOKEN=$(cat /tmp/tabz-auth-token)curl -X POST http://localhost:8129/api/spawn \ -H "Content-Type: application/json" \ -H "X-Auth-Token: $TOKEN" \ -d '{"name": "Worker", "workingDir": "~/projects", "command": "claude"}'```**Response:**```json{ "success": true, "terminalId": "ctt-default-abc123", "tmuxSession": "ctt-default-abc123"}```## Spawn Options| Field | Type | Default | Description ||-------|------|---------|-------------|| `name` | string | "Claude Terminal" | Tab display name || `workingDir` | string | `$HOME` | Starting directory || `command` | string | - | Command to run after spawn || `profileId` | string | default | Profile for appearance |## Parallel Workers with Worktrees```bash# Create isolated worktree (bd handles beads redirect automatically)bd worktree create feature-branch# Spawn worker there with BEADS_WORKING_DIR for MCP toolsPROJECT_DIR=$(pwd)curl -X POST http://localhost:8129/api/spawn \ -H "Content-Type: application/json" \ -H "X-Auth-Token: $TOKEN" \ -d "{\"name\": \"Feature Worker\", \"workingDir\": \"../feature-branch\", \"command\": \"BEADS_WORKING_DIR=$PROJECT_DIR claude\"}"```**Key:** `BEADS_WORKING_DIR` tells the beads MCP server where to find the database. Point it to the main repo, not the worktree.## Worker PromptsKeep prompts simple - workers are vanilla Claude:```Fix the pagination bug in useTerminalSessions.ts around line 200.Run tests when done: npm testClose the issue: bd close TabzChrome-abc --reason="done"```Avoid prescriptive step-by-step pipelines. Let Claude work naturally.## Worker Management### List Workers```bashcurl -s http://localhost:8129/api/agents | jq '.data[]'```### Find by Name```bashcurl -s http://localhost:8129/api/agents | jq -r '.data[] | select(.name == "V4V-ct9")'```### Get Session ID```bashSESSION=$(curl -s http://localhost:8129/api/agents | jq -r '.data[] | select(.name == "V4V-ct9") | .id')```### Kill Worker```bashcurl -s -X DELETE "http://localhost:8129/api/agents/$SESSION" \ -H "X-Auth-Token: $TOKEN"```### Send Prompt via tmux```bashtmux send-keys -t "$SESSION" -l "Your prompt here"sleep 0.5tmux send-keys -t "$SESSION" Enter```## ReferencesSee `references/` for details:- `spawn-api.md` - Full API reference- `worktree-setup.md` - Git worktree patterns- `worker-prompts.md` - Prompt crafting guidelines

Frequently asked questions

Terminals