AB rental-property-manager
Manage residential rental properties — tenant screening, lease tracking, maintenance coordination, rent collection monitoring, vacancy optimization, and compliance reminders. Built for small landlords (1-50 units) who self-manage or use a lightweight property manager.
As a process B 65/100 · Nearly there — weak spots: result and completion, 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: 5. 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 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 55Failures and branches. 1 branches
- 100Tools and files. No external tools needed
- 100Steps. 31 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 815 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 268: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 31 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.