Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Estimate And Dvi Workflow

ASecurity

Turn a write-up and a digital vehicle inspection (DVI) into a sold, defensible estimate: verified complaint, diagnostic authorization, DVI evidence per line, labor-guide hours x shop rate, parts at matrix, sell-now vs sell-later triage, and declined-work follow-up. Labor times/rates verify-at-use; no PII.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agentsrustgogit

Works with

cli

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill estimate-and-dvi-workflow --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Estimate And Dvi Workflow?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Estimate And Dvi Workflow
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-estimate-and-dvi-workflow/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-estimate-and-dvi-workflow)

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

Download with Pro
Files
SKILL.md
---
name: estimate-and-dvi-workflow
description: "Turn a write-up and a digital vehicle inspection (DVI) into a sold, defensible estimate: verified complaint, diagnostic authorization, DVI evidence per line, labor-guide hours x shop rate, parts at matrix, sell-now vs sell-later triage, and declined-work follow-up. Labor times/rates verify-at-use; no PII."
---

# Estimate & DVI Workflow

The estimate is where trust and gross profit meet. A good one is evidence-backed, priced from the guide and the matrix, authorized before the work starts, and honest about what can wait.

> **Advisory, operations decision-support — not legal/consumer-protection advice.** Estimate-authorization and disclosure rules are state-specific and `[verify-at-use]`. Labor-guide times, the shop rate, and the parts matrix are inputs set upstream; you apply them. No customer PII — reason in job types.

## The workflow

1. **Write-up: capture the real concern.** Record the complaint in the customer's words and the conditions (noise when cold, pulls left under braking). A vague write-up produces a comeback.
2. **Authorize the diagnostic.** Get explicit authorization (and any diagnostic fee disclosed) before the tech investigates. `[verify-at-use]` on the local disclosure rule.
3. **Inspect with the DVI.** Photos, measurements, and readings per line item — the evidence is the sale. A brake measurement and a photo beat "your brakes are low."
4. **Price from the guide and the matrix.** Labor-guide hours x the shop rate; parts at the matrix. No off-the-cuff discounting (that erodes the effective labor rate).
5. **Triage sell-now vs sell-later.** Safety/failure-imminent now; wear items with life left as a **dated deferred-service recommendation**. Present the ranked list, let the customer choose the pace.
6. **Authorize the repair, then follow up the declines.** Get the approval in writing/recorded; log every decline with its urgency and part life for recontact.

## Metrics

| Metric | Reads | Note |
|---|---|---|
| DVI completion rate | ROs with a full inspection / total | Missed inspections are unsold work |
| Estimate close rate | approved $ / presented $ | The counter's conversion |
| Hours-per-RO | billed hours / RO | Rises with evidence-led triage |
| Declined-work recovery | declined $ later sold / declined $ | The follow-up asset paying off |

## Anti-patterns

- Selling the part before showing the inspection evidence.
- Starting the diagnostic or repair without documented authorization.
- Presenting only the cheapest fix and hiding the deferred work (dishonest either way).
- Letting declined lines vanish instead of logging them for recontact.

## See also

- Traverse the **price a job (labor + parts matrix)** and **declined-work follow-up** trees in [`../../knowledge/auto-repair-shop-decision-trees.md`](../../knowledge/auto-repair-shop-decision-trees.md).
- [`../ro-lifecycle-and-comeback-control/SKILL.md`](../ro-lifecycle-and-comeback-control/SKILL.md), [`../../templates/repair-order-workflow.md`](../../templates/repair-order-workflow.md).
- Best practices: [`../../best-practices/sell-the-inspection-not-the-part.md`](../../best-practices/sell-the-inspection-not-the-part.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →