BB 10-leadership-virtues-for-disruptive-times
Tom Ziglar's "10 Leadership Virtues for Disruptive Times" — a Coach Leadership toolkit for navigating uncertainty and leading remote teams with kindness, humility, and purpose. Covers 6 use cases: ① Coach Leadership transformation — ("how do i lead a remote team" "what is coach leadership") ② Building team atmosphere — ("my team feels disconnected" "how to create team culture virtually") ③ Selfless leadership and respect — ("how to earn respect as a leader" "putting team first") ④ Self-control under pressure — ("i lose my temper at work" "how to stay calm in heated meetings") ⑤ Positive leadership and energy — ("how to keep team motivated" "positive leadership techniques") ⑥ Perseverance through setbacks — ("how to handle failure as a leader" "keep going when things go wrong") Trigger when users say: "lead through change" "remote team leadership" "coach leader" "ziglar" "leadership virtues" "disruptive times" "selfless leader" "build team culture" "handle crisis as leader" or mention: tom ziglar / zig ziglar / coach leadership / post-pandemic leadership / virtual team management.
Tom Ziglar's "10 Leadership Virtues for Disruptive Times" — a Coach Leadership toolkit for navigating uncertainty and leading remote teams with kindness…
As a process B 73/100 · Nearly there — weak spots: result and completion, progress reporting
How to improve
- Shorten the description to 1024 characters.
- 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: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1096 chars, limit 1024
Process rating: all ten parameters 73/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 39 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2189 tokens
- 100Running it twice. Mutating operations check current state
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)
- +3Description length 1096: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 22 example trigger phrases
- +4Structure: 11 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.