AC office-hours
YC Office Hours diagnostic — six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Adapted from Garry Tan's gstack office-hours skill. Use when asked to "brainstorm this", "I have an idea", "is this worth building", "office hours", "evaluate my startup", "诊断我的项目", "创业诊断", or when the user describes a new product idea and wants to know if it's worth pursuing.
As a process C 60/100 · Has gaps — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 60/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 15 mutating operations with no state check
- 40Consistency. Frontmatter name (office-hours) differs from the folder (yc-office-hours)
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 7 branches
- 85Steps. 55 steps, 1 vague phrases
- 100Execution cost. Instruction body is 3014 tokens
- 100Progress reporting. Reports progress
- low 11 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 437: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 55 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.