BD definite-optimism
Activate when: user says 'definite optimism,' 'Thiel's 2x2,' 'do we have a real plan or just options,' 'we're keeping our options open,' or asks whether a strategy/career/company is a concrete bet on the future or a diversified hedge; a plan consists mainly of process (iterate, A/B test, stay lean, stay flexible) with no falsifiable long-term thesis; someone must choose between committing to one path and preserving optionality. Do NOT activate when: the question is tactical execution inside an already-committed thesis (sprint planning, feature triage); genuine uncertainty is so high and reversal so cheap that optionality is correct for now and the user knows it; the user needs bet-sizing or probability math rather than a stance on planning itself. More: deciqai.com/c/definite-optimism
Activate when: user says 'definite optimism,' 'Thiel's 2x2,' 'do we have a real plan or just options,' 'we're keeping our options open,' or asks whether a…
As a process D 39/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 ≈ 5208 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 39/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. 13 mutating operations with no state check
- 60Tools and files. Uses tools (bash, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 5208 tokens
- 85Steps. 53 steps, 1 vague phrases
- 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 795: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 53 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.