YC Office Hours with two modes. Startup mode asks six forcing questions around demand reality, status quo, specificity, wedge, observation, and future-fit. Builder mode is for side projects and open source. It saves a design doc and is intended to run before implementation work.
Automate repetitive workflows and reduce manual effort
Example: Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example: Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example: Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
Time estimate: 15-45 minutes depending on use case complexity
Prerequisites
Submit your Claude Code skill and start earning
epx add garrytan/gstack --skill gstackCompatible with
Supported agents
YC Office Hours with two modes. Startup mode asks six forcing questions around demand reality, status quo, specificity, wedge, observation, and future-fit. Builder mode is for side projects and open source. It saves a design doc and is intended to run before implementation work. Imported from office-hours/SKILL.md in garrytan/gstack.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionoffice-hoursExecute the skills CLI command in your project's root directory to begin installation:
epx add garrytan/gstack --skill gstackFetches office-hours from garrytan/gstack and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
.cursor/skills/office-hours
Restart Cursor to activate office-hours. Access via /office-hoursin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
benchmark-models
garrytan/gstack · gstack-multi-ai · same repo
cso
garrytan/gstack · gstack-security · same repo
to-prd
mattpocock/skills · productivity · 2 shared tags
release-planning
aj-geddes/useful-ai-prompts · Productivity · tag: planning
concise-planning
sickn33/antigravity-awesome-skills · Productivity · tag: planning
gstack-workflow-assistant
aradotso/trending-skills · Productivity · tag: gstack
Keeps context tight: office-hours is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend office-hours for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: office-hours is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for office-hours matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for office-hours matched our evaluation — installs cleanly and behaves as described in the markdown.
office-hours fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
office-hours is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
office-hours reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added office-hours from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: office-hours is focused, and the summary matches what you get after install.
showing 1-10 of 64