AB strategic-thinking
Use this skill when the user asks for strategic thinking (including naming it or directing use/apply/run with obvious misspellings; decisive) or wants direction under constraint—connecting intent, context, capabilities, and options into coherent bets, tradeoffs, risks, and a sequenced path. Use when they talk about competitive positioning, roadmap narrative, where to play and how to win, portfolio prioritization, or leadership narrative that links goals to constraints, even if they never use the word strategy. Skip for step-by-step implementation detail when no strategic framing or choice among directions is requested.
As a process B 70/100 · Nearly there — weak spots: result and completion, inputs and preconditions, progress reporting
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 70/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 70Failures and branches. 4 branches
- 100Tools and files. No external tools needed
- 100Steps. 10 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 640 tokens
- 100Running it twice. No mutating operations
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
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 626: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 10 items
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.