AC lifestage-value-curve
Activate when: someone asks 'what should I focus on at my age,' 'I feel like I'm wasting my best years,' 'how do I plan my career long-term,' 'what does my 40s/50s demand,' or a person is clearly investing for the wrong life stage (Heroic Age execution in the Golden Age, or Silver Age coasting in the Heroic Age). Do NOT activate when: the problem is domain skill acquisition unrelated to life-stage strategy; chronological and developmental age diverge significantly and more context is needed first. More: deciqai.com/c/lifestage-value-curve
Activate when: someone asks 'what should I focus on at my age,' 'I feel like I'm wasting my best years,' 'how do I plan my career long-term,' 'what does my…
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 4. 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 51/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. 2 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1907 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
- +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
- +1No license
- +2Single-language instructions
- +3Description length 544: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.