AC rich-dad-poor-dad-kiyosaki
Robert Kiyosaki's "Rich Dad Poor Dad" — an executable toolkit that reframes how you think about money, assets, and financial freedom using the 6 Lessons framework. Covers 5 use cases: ① Financial Mindset — ("How to think about money differently" "Why am I always broke") ② Asset Building — ("How to buy assets not liabilities" "What counts as an asset") ③ Passive Income — ("How to make money while I sleep" "How to escape the rat race") ④ Financial Education — ("What school didn't teach me about money" "How to become financially literate") ⑤ Entrepreneurship — ("How to start a business" "How to take financial risks") Trigger when users say: "Rich Dad Poor Dad" "Robert Kiyosaki" "How to get rich" "Financial freedom" "How to escape the rat race" "Assets vs liabilities" "Passive income" "Money mindset" or mention: personal finance / financial literacy / investing / wealth / rich dad / poor dad / assets / liabilities / rat race / cashflow / financial freedom / passive income.
Robert Kiyosaki's "Rich Dad Poor Dad" — an executable toolkit that reframes how you think about money, assets, and financial freedom using the 6 Lessons…
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. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1745 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 983: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +5Description quotes 19 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 32 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.