growthub-worker-kits

Resolve Growthub worker kit workspaces via env vars and apply operator runbooks.

48|12|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/Growthub-ai/growthub-local --skill growthub-worker-kits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: growthub-worker-kits
Source: https://github.com/Growthub-ai/growthub-local/tree/main/.claude/skills/growthub-worker-kits
Command: npx skills add https://github.com/Growthub-ai/growthub-local --skill growthub-worker-kits

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unifiedly manage any Growthub worker kit by resolving workspace paths from environment variables and orchestrating kit-specific operator runbooks, removing manual setup variance.

Core Features & Use Cases

  • Uniform workspace path resolution using ${<KIT>_HOME} env vars with sensible defaults to prevent path drift.
  • Per-kit operator runbook consumption (CLAUDE) and consistent dispatch to kit-specific skills.
  • Quickstart-driven onboarding with validation and safe, non-destructive guidance before interactive steps.
  • Supports run, inspect, install, and fork workflows across all kits in a cohesive, agent-agnostic pattern.
  • Governance-ready workflow with standardized logging, export considerations, and kit packaging readiness.

Quick Start

Resolve the kit workspace using the canonical environment variable and then run the kit’s QUICKSTART steps.

Frequently Asked Questions about growthub-worker-kits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve workspace paths for automation kits using environment variables?

Workspace path resolution uses canonical ${<KIT>_HOME} environment variables with sensible defaults to prevent path drift and ensure consistent kit orchestration. This standardizes automation setup across different execution environments.

What is a worker kit operator runbook and how does it standardize workspace governance?

A worker kit operator runbook provides per-kit governance instructions that standardize run, inspect, install, and fork workflows into a consistent, agent-agnostic pattern. It serves as the source of truth for kit-specific operations.

How do I run QUICKSTART steps for a worker kit without manual setup variance?

Execute the kit's QUICKSTART steps after resolving the workspace via canonical environment variables, which provides validation and safe, non-destructive guidance before any interactive steps begin.

Can I use worker kit automation across different agent platforms without changing my workflow?

Yes, worker kit automation applies an agent-agnostic pattern across all kits, enabling consistent dispatch to kit-specific skills regardless of the agent platform. This maintains uniform governance and operational consistency.

What limitations exist when orchestrating multiple worker kits with environment variable resolution?

Orchestration requires valid env-var resolution, QUICKSTART adherence, and a per-kit operator runbook as the source of truth. Kits lacking these elements cannot be uniformly managed within this governance framework.

Does Growthub worker kit automation support fork and install workflows alongside standard run operations?

Yes, worker kit automation supports run, inspect, install, and fork workflows across all kits within a cohesive pattern. This enables comprehensive lifecycle management with standardized logging and governance.