AC 7-habits-covey
Stephen R. Covey's "The 7 Habits of Highly Effective People" — an executable toolkit for principle-centered living, from personal effectiveness to interdependent leadership. Covers 5 use cases: ① Personal Effectiveness — ("How to be more proactive" "How to take control of my life") ② Goal Setting — ("How to set meaningful goals" "How to prioritize what matters") ③ Time Management — ("How to stop being busy but unproductive" "How to focus on what's important") ④ Relationship Building — ("How to build trust" "How to communicate better") ⑤ Leadership — ("How to lead by example" "How to be a better manager") Trigger when users say: "7 Habits" "Stephen Covey" "Be proactive" "Begin with the end in mind" "Put first things first" "Think win-win" "Seek first to understand" "Sharpen the saw" "How to be more effective" "Principle-centered leadership" or mention: effectiveness / proactivity / habits / Covey / time management / emotional bank account / circle of influence / paradigm shift.
Stephen R. Covey's "The 7 Habits of Highly Effective People" — an executable toolkit for principle-centered living, from personal effectiveness to…
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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: 8. 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 57/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
- 30Running it twice. 2 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 33 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1923 tokens
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 991: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 21 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 33 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: 91.