Verify Output SDK development services are running. Use when debugging workflows, starting development, encountering connection errors, services may be down, or when you see "ECONNREFUSED" or timeout errors.
Checks Output SDK services (Docker, API, Temporal) are running. Use when encountering connection errors, timeouts, or before debugging workflows to diagnose service issues.
/plugin marketplace add growthxai/output-claude-plugins/plugin install growthxai-outputai-plugins-outputai@growthxai/output-claude-pluginsThis skill is limited to using the following tools:
This skill verifies that all required Output SDK development services are running and healthy. The Output SDK requires three services for local development: Docker containers, the API server, and the Temporal server with its UI.
docker ps | grep output
Expected: You should see containers related to output running. If no containers appear, Docker may not be running or the services haven't been started.
curl -s http://localhost:3001/health
Expected: Returns a health status response. If this fails with "Connection refused", the API server is not running.
curl -s http://localhost:8080 > /dev/null && echo "Temporal UI accessible" || echo "Temporal UI not accessible"
Expected: "Temporal UI accessible". If not accessible, Temporal server may not be running.
# Start all development services
npx output dev
Wait 30-60 seconds for all services to initialize, then re-run the checks.
# Restart all services using Docker Compose
docker compose down
docker compose up -d
lsof -i :3001 and lsof -i :8080docker compose logsIF docker_not_running:
ACTION: Start Docker Desktop/daemon
WAIT: for Docker to initialize
IF no_output_containers:
RUN: npx output dev
WAIT: 30-60 seconds for services
IF api_not_responding:
CHECK: port 3001 for conflicts
RUN: output dev (if not already running)
IF temporal_not_accessible:
CHECK: port 8080 for conflicts
CHECK: docker compose logs for Temporal errors
IF all_services_healthy:
PROCEED: with workflow debugging
Scenario: User reports "connection refused" when running a workflow
# First, check if services are running
docker ps | grep output
# Output: (empty - no containers)
# Start services
npx output dev
# Wait and verify
sleep 60
curl -s http://localhost:3001/health
# Output: {"status":"healthy"}
Scenario: Partial service failure
# API responds but Temporal doesn't
curl -s http://localhost:3001/health # Works
curl -s http://localhost:8080 # Fails
# Check Temporal logs
docker compose logs temporal
# Restart just Temporal
docker compose restart temporal
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.