Skill creation · Claude Code, OpenClaw, Codex, AI Agent Suite
gstack adoption decision
Create, package, manage, or learn from reusable AI skill collections and marketplaces. Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA
Create, package, manage, or learn from reusable AI skill collections and marketplaces.
Who should use itSkill authors and teams turning agent workflows into reusable packages or suites.
Use this as a fit check before reading install commands.
Works withClaude Code / OpenClaw / Codex / AI Agent
Platform fit comes after the use case, not before it.
Adoption pathSource-verified setup
Setup evidence is available from README.md · Step 1: Install on your machine. Review the source before installing.
Trust signalREADME + SKILL.md
12 SKILL.md + README + install evidence, 86,466 stars, and today repo freshness at last scan.
Overview
What job does it solve?Skill creation
Create, package, manage, or learn from reusable AI skill collections and marketplaces.
Who should use it?Skill authors and teams turning agent workflows into reusable packages or suites.
building and managing AI skills for Claude Code users.
Works withClaude Code / OpenClaw / Codex / AI Agent
Check platform compatibility after confirming the use case fits your workflow.
How can I adopt it?Source-verified setup
Setup evidence is available from README.md · Step 1: Install on your machine. Review the source before installing.
Can I trust it?README + SKILL.md
12 SKILL.md + README + install evidence, 86,466 stars, and today repo freshness at last scan.
What to compare?5 related skills
Use the comparison list below to avoid adopting the first matching repo blindly.
Quick read
Use Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA
1. Install gstack (30 seconds — see below) 2. Run /office-hours — describe what you're building 3. Run /plan-ceo-review on any feature idea 4. Run /review on any branch with changes 5. Run /qa on your staging URL 6. Stop there. You'll know if this is for you.
Why we list it
Public because this is a source-backed cohesive skill suite with enough current evidence to qualify for the shortlist.
Current GitHub metadata is available for garrytan/gstack.
50 SKILL.md file(s) were found in the recursive tree scan.
Trusted install evidence was extracted from 1 source file(s).
Adoption path for gstack
Primary adoption path
Setup evidence extracted from README.md · Step 1: Install on your machine. Review source before installing.
Open Claude Code and paste this. Claude does the rest.
Install gstack: run git clone --single-branch --depth 1 https://github.com/garrytan/gstack.git ~/.claude/skills/gstack && cd ~/.claude/skills/gstack && ./setup then add a "gstack" section to CLAUDE.md that says to use the /browse skill from gstack for all web browsing, never use mcp\_\_claude-in-chrome\_\_\* tools, and lists the available skills: /office-hours, /plan-ceo-review, /plan-eng-review, /plan-design-review, /design-consultation, /design-shotgun, /design-html, /review, /ship, /land-and-deploy, /canary, /benchmark, /browse, /connect-chrome, /qa, /qa-only, /design-review, /setup-browser-cookies, /setup-deploy, /setup-gbrain, /retro, /investigate, /document-release, /codex, /cso, /autoplan, /plan-devex-review, /devex-review, /careful, /freeze, /guard, /unfreeze, /gstack-upgrade, /learn. Then ask the user if they also want to add gstack to the current project so teammates get it.
Step 2: Team mode — auto-update for shared repos (recommended)
From inside your repo, paste this. Switches you to team mode, bootstraps the repo so teammates get gstack automatically, and commits the change:
No vendored files in your repo, no version drift, no manual upgrades. Every Claude Code session starts with a fast auto-update check (throttled to once/hour, network-failure-safe, completely silent).
Swap required for optional if you'd rather nudge teammates than block them.
Native OpenClaw Skills (via ClawHub)
Four methodology skills that work directly in your OpenClaw agent, no Claude Code
These are conversational skills. Your OpenClaw agent runs them directly via chat.
SKILL.md excerpt
SKILL.md
Plan Mode Safe Operations
In plan mode, allowed because they inform the plan: $B, $D, codex exec/codex review, writes to ~/.gstack/, writes to the plan file, and open for generated artifacts.
Chosen mode: full | artifacts-only | off
"$_BRAIN_CONFIG_BIN" set gbrain_sync_mode
"$_BRAIN_CONFIG_BIN" set gbrain_sync_mode_prompted true
If A/B and `~/.gstack/.git` is missing, ask whether to run `gstack-brain-init`. Do not block the skill.
At skill END before telemetry:
If `NEEDS_SETUP`:
1. Tell the user: "gstack browse needs a one-time build (~10 seconds). OK to proceed?" Then STOP and wait.
2. Run: `cd && ./setup`
3. If `bun` is not installed:
actual_sha=$(shasum -a 256 "$tmpfile" | awk '{print $1}')
if [ "$actual_sha" != "$BUN_INSTALL_SHA" ]; then
echo "ERROR: bun install script checksum mismatch" >&2
echo " expected: $BUN_INSTALL_SHA" >&2
echo " got: $actual_sha" >&2
rm "$tmpfile"; exit 1
fi
BUN_VERSION="$BUN_VERSION" bash "$tmpfile"
rm "$tmpfile"
fi
## QA Workflows
> **Credential safety:** Use environment variables for test credentials.
> Set them before running: `export TEST_EMAIL="..." TEST_PASSWORD="..."`
# Set up dialog handling BEFORE triggering
$B dialog-accept # will auto-accept next alert/confirm
$B click "#delete-button" # triggers confirmation dialog
$B dialog # see what dialog appeared
$B snapshot -D # verify the item was deleted