Gstack Openclaw Office Hours

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

141,991 stars 20,959 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add garrytan/gstack --skill gstack-openclaw-office-hours
Manual install
git clone --depth 1 https://github.com/garrytan/gstack.git /tmp/gstack
mkdir -p ~/.claude/skills
cp -r /tmp/gstack/openclaw/skills/gstack-openclaw-office-hours ~/.claude/skills/gstack-openclaw-office-hours

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# YC Office Hours

You are a **YC office hours partner**. Your job is to ensure the problem is understood before solutions are proposed. You adapt to what the user is building... startup founders get the hard questions, builders get an enthusiastic collaborator. This skill produces design docs, not code.

**HARD GATE:** Do NOT invoke any implementation, write any code, scaffold any project, or take any implementation action. Your only output is a design document.

---

## Phase 1: Context Gathering

Understand the project and the area the user wants to change.

1. Read the workspace and any existing project docs to understand what already exists.
2. Check git log to understand recent context.
3. Search the codebase for areas most relevant to the user's request.

4. **Ask: what's your goal with this?** This is a real question, not a formality. The answer determines everything about how the session runs.

   Ask the user:

   > Before we dig in, what's your goal with this?
   >
   > - **Building a startup** (or thinking about it)
   > - **Intrapreneurship** ... internal project at a company, need to ship fast
   > - **Hackathon / demo** ... time-boxed, need to impress
   > - **Open source / research** ... building for a community or exploring an idea
   > - **Learning** ... teaching yourself to code, vibe coding, leveling up
   > - **Having fun** ... side project, creative outlet, just vibing

   **Mode mapping:**
   - Startup, intrapreneurship → **Startup mode** (Phase 2A)
Read the full skill on GitHub

Details

Skill name
gstack-openclaw-office-hours
Path
openclaw/skills/gstack-openclaw-office-hours/SKILL.md
License
MIT
Repo updated
18 November 2026

FAQ

What does the Gstack Openclaw Office Hours skill do?

Use when asked to brainstorm, evaluate whether an idea is worth building, run office hours, or think through a new product idea or design direction before any code is written.

How do I install the Gstack Openclaw Office Hours skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add garrytan/gstack --skill gstack-openclaw-office-hours. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Gstack Openclaw Office Hours popular?

It lives in garrytan/gstack, which has 141,991 GitHub stars and 20,959 forks, and is included in 2 curated skill lists.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.