Skip to content
Back to skills

Quantify Turn Loss

ASecurity

Quantify lost rent during unit turns and frame the work-order backlog as a retention risk. Reach for this on a turn or maintenance question.

  • 7 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 23, 2026
ai-agents

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add mcorbett51090/RavenClaude --skill quantify-turn-loss --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Quantify Turn Loss?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Quantify Turn Loss
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-quantify-turn-loss/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-quantify-turn-loss)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: quantify-turn-loss
description: "Quantify lost rent during unit turns and frame the work-order backlog as a retention risk. Reach for this on a turn or maintenance question."
---

# Skill: Quantify turn loss

Slow turns are lost rent and a satisfaction signal, not just a cost (§3 #3).

## Step 1 — Count vacant units and turn days
Vacant units awaiting turn and average turn days.

## Step 2 — Compute lost rent
Vacant units × turn days × daily rent via `property_management_calc.py turn-time` (§3 #3).

## Step 3 — Annualize the drag
Scale the per-turn loss to an annual run-rate.

## Step 4 — Frame the backlog risk
Read the work-order backlog age as a renewal risk (§3 #6).

## Output
A lost-rent read annualized with the backlog framed as retention risk.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…