BD seven-questions-test
Activate when: user says 'seven questions,' 'Zero to One test,' 'Thiel checklist,' 'should I start this business,' 'is this startup idea any good,' or 'stress-test my startup idea'; a business idea, pivot, product line, or funding decision is about to proceed on enthusiasm rather than evidence; a pitch or plan is strong on one dimension (usually technology or market size) and silent on the others; the user wants a structured go/no-go gate before committing capital, time, or reputation to a venture. Do NOT activate when: the venture is already running and the question is a single-dimension diagnosis (pricing, one channel, one hire) — use the specific skill for that dimension instead; the decision is a small reversible experiment where a full seven-question gate is heavier than the bet itself; the user asked only to polish pitch wording, not to test whether the underlying business should exist. More: deciqai.com/c/seven-questions-test
Activate when: user says 'seven questions,' 'Zero to One test,' 'Thiel checklist,' 'should I start this business,' 'is this startup idea any good,' or…
As a process D 47/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
body-longSKILL.md body ≈ 5555 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 47/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 70Execution cost. Instruction body is 5555 tokens
- 85Steps. 54 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +3Description length 946: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +4Structure: 13 headings
- +3Step-by-step instructions: 54 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 67.