New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Office Hours

by mvschwarz in mvschwarz/openrig

YC-style product validation using six forcing questions. An agent skill from mvschwarz/openrig.

Apache-2.0Auto-check passedAgent Workflows

Install Office Hours

skills CLI
$ npx skills add mvschwarz/openrig --skill office-hours -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig office-hours --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/pm/office-hours .claude/skills/office-hours && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
office-hours
GitHub stars
6.2k
Token cost
~1.3k tokens
SKILL.md length
539 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

YC-style product validation using six forcing questions. An agent skill from mvschwarz/openrig.

  • Works in 9 steps: Demand Reality → Status Quo → Desperate Specificity → …
  • Agent Workflows work in your project
  • SKILL.md covers The Six Forcing Questions, Process and Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Office Hours is an agent skill from mvschwarz/openrig. YC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/office-hours”

Workflow steps

9 steps, taken from the step headings in SKILL.md.

  1. Demand Reality
  2. Status Quo
  3. Desperate Specificity
  4. Narrowest Wedge
  5. Observation / Surprise
  6. Future-Fit
  7. Get the Pitch
  8. Run the Questions
  9. Verdict

What it can do on your machine

Read from SKILL.md and the folder at commit a29dfbc. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Office Hours loads about 1.3k tokens when it runs. Until then it costs about 51 tokens; SKILL.md has 539 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~51
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit a29dfbc, republished under its Apache-2.0 licence (© mvschwarz). 539 words, ~1,261 tokens.

Download SKILL.mdSave it as .claude/skills/office-hours/SKILL.md (or your agent's skills folder).
name
office-hours
description
YC-style product validation using six forcing questions. Pressure-tests a feature idea before it becomes a requirement — ensuring real demand, a clear wedge, and evidence behind assumptions.

You are a YC-style product advisor running office hours. Your job is to pressure-test a feature idea before it becomes a requirement — ensuring there's real demand, a clear wedge, and evidence behind the assumption.

The Six Forcing Questions

Work through these sequentially. Each question builds on the previous answer.

1. Demand Reality

"Who is actively asking for this, and what evidence do you have?"

  • Name specific customers, meetings, or support tickets
  • Distinguish between "customers asked for this" vs "we think customers want this"
  • Search meeting notes and customer records for actual conversations
  • If no evidence: flag it. An assumption isn't demand.
2. Status Quo

"How are users solving this problem today, and why is that not good enough?"

  • Map the current workflow (Excel? Manual? Competitor tool?)
  • Reference persona profiles for current technology stack
  • Quantify the pain: time wasted, errors, cost, compliance risk
  • If the status quo is "fine": question whether this is a real problem
3. Desperate Specificity

"Who is the single most desperate user for this, and what does their day look like?"

  • Get to ONE specific person or company, not a category
  • Walk through their actual workflow step by step
  • What breaks for them? What's the moment of maximum frustration?
  • If nobody is desperate: this might be a "nice to have" not a "must have"
4. Narrowest Wedge

"What is the absolute smallest version of this that would solve the desperate user's problem?"

  • Strip away everything that isn't essential for that one user
  • What's the MVP that, if you shipped it tomorrow, would make them switch?
  • Reference existing capabilities — what already exists?
  • Resist the urge to scope-expand. Narrower is better.
5. Observation / Surprise

"What have you observed or learned that surprised you about this problem?"

  • Non-obvious insights from customer meetings, competitive research, or domain expertise
  • Things the team didn't expect to find
  • Industry-specific patterns or workflow quirks
  • If nothing surprised you: you might not understand the problem deeply enough yet
Show full SKILL.md (217 more words)Show less
6. Future-Fit

"If this succeeds, what does it unlock? If it fails, what have we learned?"

  • Does this feature compound? Does it make future features easier?
  • Does it strengthen competitive position or just maintain parity?
  • What's the learning value even if the feature doesn't land?

Process

Step 1: Get the Pitch

Ask the PM to describe the feature idea in 2-3 sentences. No jargon, no implementation details.

Step 2: Run the Questions

Work through all six questions. After each answer:

  • Summarize what you heard
  • Rate the strength of the answer (Strong / Needs Work / Red Flag)
  • Ask follow-up probes if the answer is vague
Step 3: Verdict

Save the assessment to the feature folder as validation.md.

markdown
---
title: "Validation: [Feature Name]"
type: validation
verdict: [GO | REFINE | PAUSE]
date: [today's date]
pm: [name]
feature: [feature-folder-name]
---

# Validation: [Feature Name]

## Demand Reality
**Rating: [Strong / Needs Work / Red Flag]**
[Summary of evidence. Name customers, deals, dollar amounts.]

## Status Quo
**Rating: [Strong / Needs Work / Red Flag]**
[Current workflow and pain. What tools they use today.]

## Desperate User
**Rating: [Strong / Needs Work / Red Flag]**
[The single most desperate user and their breaking point.]

## Narrowest Wedge
**Rating: [Strong / Needs Work / Red Flag]**
[The smallest thing worth shipping. What's in, what's out.]

## Surprise
**Rating: [Strong / Needs Work / Red Flag]**
[Non-obvious insights. What the team didn't expect to find.]

## Future-Fit
**Rating: [Strong / Needs Work / Red Flag]**
[What this unlocks. How it compounds.]

## Verdict: [GO / REFINE / PAUSE]
- **GO**: Strong evidence, clear wedge, proceed to requirements
- **REFINE**: Promise but gaps — do more research first (list what)
- **PAUSE**: Insufficient evidence of demand — revisit when evidence emerges

## Next Steps
- [Specific actions — what to do immediately after this assessment]

Naming matters. This file is read by downstream skills:

  • Context builder reads it for customer drivers and competitive context
  • Requirements writer reads it for demand evidence, scope, and personas
  • Executive summary reads it for the Problem, Why Now, and FAQ sections

Guidelines

  • Be constructively skeptical. Your job is to find weaknesses before the team invests in building.
  • Push for evidence, not opinions. "Customers want this" -> "Which customers? When did they say this?"
  • Don't kill ideas — sharpen them. Even a PAUSE verdict should include what evidence would change it.
  • The narrowest wedge is the most valuable question. Most features are scoped too broadly.

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/pm/office-hours of mvschwarz/openrig.

Open the folder on GitHubat commit a29dfbc

Compare with similar skills

Office Hours next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Office Hours compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Office Hours this skillmvschwarz/openrig6.2k—~1.3kAutomated safety check: PassApache-2.0
MCP Server Builderanthropics/skills180k63 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official38k10 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k35 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers297k2 repos~5.1kAutomated safety check: PassMIT
Skill CreatorAzure/azqr79589 repos~8.2kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 63 repos~2.3k tokens
    Agent WorkflowsAuto-check passed

  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    38k GitHub starsUsed in 10 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes

  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 35 repos~1.4k tokens
    Agent WorkflowsAuto-check passed

  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    297k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    795 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    38k GitHub starsUsed in 7 repos~2.8k tokens
    Agent WorkflowsAuto-check passed

More from mvschwarz/openrig

All 49 skills in this repo

  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    6.2k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    6.2k GitHub stars~864 tokensUpdated today
    Auto-check passed

  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    6.2k GitHub stars~2.6k tokensUpdated today
    Auto-check passed

  • Seat Continuity and Handover

    mvschwarz/openrig

    Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    6.2k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Addressable Markdown Loader

    mvschwarz/openrig

    Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    6.2k GitHub stars~341 tokensUpdated today
    Auto-check passed

  • Agent Starters

    mvschwarz/openrig

    Covers authoring, inspecting, refreshing, promoting and deprecating named Agent Starters, the reusable starting points for agent seats in a rig.

    6.2k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Office Hours

What does Office Hours do?

YC-style product validation using six forcing questions. An agent skill from mvschwarz/openrig. Office Hours is an agent skill from mvschwarz/openrig. YC-style product validation using six forcing questions.

When should I use Office Hours?

Office Hours fits situations like: agent Workflows work in your project.

How do I install Office Hours in Claude Code?

Run `npx skills add mvschwarz/openrig --skill office-hours -a claude-code`. Or copy the skill folder (skills/_canonical/pm/office-hours in mvschwarz/openrig) into .claude/skills/office-hours in your project. Claude Code loads it when a task matches its description.

How do I install Office Hours in Codex?

Run `npx skills add mvschwarz/openrig --skill office-hours -a codex`. Or copy the skill folder (skills/_canonical/pm/office-hours in mvschwarz/openrig) into .agents/skills/office-hours in your project. Codex loads it when a task matches its description.

Can I use Office Hours in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill office-hours -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/office-hours, .gemini/skills/office-hours, .github/skills/office-hours and .opencode/skills/office-hours in your project.

What does Office Hours need to run?

SKILL.md names no scripts, command-line tools or credentials: Office Hours is instructions for the agent only.

Does Office Hours access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Office Hours safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Office Hours use?

Office Hours is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Office Hours use?

About 1.3k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Office Hours?

Skills that share tags, products or a category with Office Hours: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Office Hours?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 6,242 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.