Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →garrytan/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.
Passed 9 of 17 test cases with the skill, and 7 of 17 without it.
and 9 more in the full report
7 fixed5 passed either way7 still failing4 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our engineering team wants to re-architect our internal deployment dashboard to reduce dev onboarding time. Run an office hours session with me to challenge my premises about this internal project, evaluate alternative technical paths, and generate a final design document with an actionable next step. Remember that your role here is purely design consultation—do not write any code or execute project scaffolding.
| Checked | Without skill | With skill |
|---|---|---|
| Displays the structured goal selection options list. | Missed | Passed |
| Includes an understanding statement summarizing the existing project. | Missed | Passed |
| Asks exactly one question in the response. | Missed | Passed |
The instructions your model reads when the skill loads.
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.
Understand the project and the area the user wants to change.
Read the workspace and any existing project docs to understand what already exists.
Check git log to understand recent context.
Search the codebase for areas most relevant to the user's request.
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:
Assess product stage (only for startup/intrapreneurship modes):
Output: "Here's what I understand about this project and the area you want to change: ..."
test cases passed, vs 7 / 17 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.