BC openclaw-office-hours
YC Office Hours-style product consultation that reframes problem definition before coding. Uses Startup/Builder modes to reveal demand truth, minimal entry point, metrics, and risk insights to avoid blind development. 中文：YC Office Hours 风格的产品前置咨询，在写代码前重构问题定义。通过 Startup / Builder 模式给出问题真相、最小切入、指标与风险洞察，避免盲目开发。 日本語：YC Office Hours形式の事前思考支援。コーディング前に問題定義を再構築し、Startup/Builderモードでユーザー・最小実行単位・観察可能性を整理。 한국어：코딩 전에 문제 정의를 재구성하는 Office Hours 스타일 컨설턴트. Startup/Builder 모드로 사용자 진실, 최소 실행 포인트, 지표와 위험 통찰을 도출해 판단 품질을 높입니다. Español：Replantea el problema antes de codificar con estilo Office Hours (Startup/Builder). Extrae verdad del problema, usuario objetivo, punto de entrada mínimo y señales para reducir producto sin validación.
As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 958 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 720: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.