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

Best Practices

ASecurity

**Status:** Pattern **Domain:** Skilled trades contracting / field operations **Applies to:** `skilled-trades-contracting` ---

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

Works with

terminal

Security Analysis

A100/100

Pro scans all 21 files and shows the line behind each finding

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill best-practices --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Best Practices?

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

Security grade badge for Best Practices
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-best-practices/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-best-practices)

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

Download with Pro
Files
README.md
# Parts Availability at the Truck Determines First-Time-Fix, Not Just Technician Skill

**Status:** Pattern
**Domain:** Skilled trades contracting / field operations
**Applies to:** `skilled-trades-contracting`

---

## Why this exists

First-time-fix rate is often treated as a technician competency metric — the tech either knew how to fix it or didn't. In practice, the single most common cause of a callback or a same-day return trip is a missing part, not a missing skill. A tech who diagnoses correctly but doesn't carry the part has to return — and that return trip is a free truck roll, a scheduling disruption, and a customer experience failure. Truck stock — what is on each service vehicle, at what replenishment threshold, and how it is managed — directly determines first-time-fix rate independent of technician skill level. A poorly stocked truck is a built-in callback machine.

## How to apply

Manage truck stock as a structured inventory system with par levels, not as whatever happens to be left from the last job:

```
Truck Stock Audit — Vehicle [#] Technician: [Name] Date: [YYYY-MM-DD]
──────────────────────────────────────────────────────────────────────
Category          │ Item                        │ Par qty │ Current │ Reorder?
──────────────────┼─────────────────────────────┼─────────┼─────────┼────────
Capacitors        │ Run capacitor, 5μF–50μF std │ 5 ea    │         │
(HVAC)            │ Start capacitor, 88–108μF   │ 2 ea    │         │
                  │ Dual-run capacitor combo     │ 3 ea    │         │
──────────────────┼─────────────────────────────┼─────────┼─────────┼────────
Contactors (HVAC) │ 1-pole, 2-pole standard      │ 3 ea    │         │
──────────────────┼─────────────────────────────┼─────────┼─────────┼────────
Electrical        │ Breakers (common amperages)  │ 2 ea    │         │
                  │ Wire connectors, terminals   │ assorted│         │
──────────────────┼─────────────────────────────┼─────────┼─────────┼────────
Fittings / valves │ Common sizes for trade       │ [set]   │         │
──────────────────┼─────────────────────────────┼─────────┼─────────┼────────
Safety / PPE      │ Gloves, glasses, respirator  │ 1 set   │         │
──────────────────┼─────────────────────────────┼─────────┼─────────┼────────
Consumables       │ Wire nuts, tape, lubricant   │ min set │         │
```

**First-time-fix root cause analysis (for each callback):**

| Job # | Tech | Callback reason | Missing part? | Part name | Stocked next time? |
|---|---|---|---|---|---|
| | | | Y / N | | Y / N |

**Do:**
- Set truck-stock par levels based on actual job data — pull 6 months of parts-used reports from the job-management system and stock to the top 80% of most-used items by frequency.
- Audit truck stock weekly (or at the Monday morning pull-up) — missing parts tend to accumulate silently between audits.
- Track "parts not on truck" as a separate callback reason code in the dispatch/CRM system — it isolates the supply problem from the skill problem and creates a data trail for par-level adjustments.
- Assign the cost of a callback to the truck-stock budget line, not the labor budget, when the root cause is a missing part — the financial accountability drives the stocking behavior.

**Don't:**
- Blame the tech for a callback caused by a missing part that was not on the vehicle and not available at the supply house in a reasonable time window.
- Set truck stock purely on historical average usage without adjusting for seasonal demand — an HVAC truck stocked for shoulder-season repair volume will run short on capacitors and contactors during a summer heat wave.
- Ignore shrink and theft in truck stock — a truck that should have a part and doesn't is a trust-and-accountability issue as much as a replenishment issue; weekly audits surface it.

## Edge cases / when the rule does NOT apply

Commercial service contractors doing project work (new installs, large replacements) typically work from job-specific material lists pulled to the site in advance — truck stock par levels are less relevant than the job-staging and procurement process. Specialty trade contractors (refrigeration, high-voltage, specialty gas) with low call volume and high-value, low-frequency parts may find that stocking from a central supply chain is more economical than truck stock — the principle still applies, but the mechanism is warehouse-pull rather than truck-stocked par.

## See also
- [`../agents/field-operations-specialist.md`](../agents/field-operations-specialist.md) — owns dispatch, truck utilization, and first-time-fix metrics.
- [`../agents/trade-business-analyst.md`](../agents/trade-business-analyst.md) — tracks the callback rate and its cost impact in job costing.
- [`../knowledge/trades-economics.md`](../knowledge/trades-economics.md) — covers first-time-fix rate economics and callback cost quantification.

## Provenance

Codifies the truck-stock-driven first-time-fix discipline from ACCA and ServiceTitan/Hatch field-service management training; par-level management from actual call data is the standard recommendation in trade contractor business coaching programs [unverified — training knowledge].

---

_Last reviewed: 2026-06-05 by `claude`_

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 →