AC vestafolio-achat-vs-location
Compare final net wealth between buying a primary residence with a mortgage and renting while investing savings, over a chosen horizon, using Vestafolio's simulator API, after asking the simulator's questions (available savings first, market assumptions, purchase scenario, rent scenario). Use when a user asks whether to buy or rent, "acheter ou louer", "est-ce rentable d'acheter ma résidence principale", rent vs buy break-even, or what owning really costs versus renting in France.
Compare final net wealth between buying a primary residence with a mortgage and renting while investing savings, over a chosen horizon, using Vestafolio's…
As a process C 64/100 · Has gaps — weak spots: inputs and preconditions, running it twice, progress reporting
The same skill appears in 1 more place: ClawHub
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 64/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 100Steps. 41 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2925 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)
- +1No license
- +2Single-language instructions
- +5Description quotes 2 example trigger phrases
- +3Description length 485: enough signal without eating the budget
- +4Structure: 10 headings
- +3Step-by-step instructions: 41 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.