AF realestate
Real estate transaction support with affordability analysis, property evaluation, and offer strategy. Use when user mentions buying a home, selling property, house hunting, mortgages, inspections, or rental agreements. Calculates true affordability, evaluates properties systematically, builds offer strategies, reviews contracts, and tracks transaction milestones. NEVER provides investment advice.
As a process F 33/100 · Will not run — References files that are not bundled: references/affordability.md, references/evaluation.md, references/offers.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: references/affordability.md - warning
missing-refreference to a missing file: references/evaluation.md - warning
missing-refreference to a missing file: references/offers.md - warning
missing-refreference to a missing file: references/inspection.md - warning
missing-refreference to a missing file: references/selling.md - warning
missing-refreference to a missing file: references/leases.md - warning
missing-refreference to a missing file: references/closing.md
Process rating: all ten parameters 33/100
- 0Tools and files. 7 referenced file(s) missing: references/affordability.md, references/evaluation.md, references/offers.md
- 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
- 85Steps. 26 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 882 tokens
- 100Running it twice. No mutating operations
- 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
- +1No license
- +2Single-language instructions
- +3Description length 399: enough signal without eating the budget
- +4Structure: 14 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (5 code blocks)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.