Technical Analyst
tradermonty/claude-trading-skills
This skill should be used when analyzing weekly price charts for stocks, stock indices, cryptocurrencies, or forex pairs.
Reduce driver turnover by fixing what actually makes drivers leave — the pay comparison that is real, the home-time reliability, the dispatch relationship, and the first ninety days where most…
Install Driver Retention Plan
$ npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills driver-retention-plan --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/driver-retention-plan .claude/skills/driver-retention-plan && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "driver-retention-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-plan into .claude/skills/driver-retention-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "driver-retention-plan", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-planType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills driver-retention-plan --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/driver-retention-plan .agents/skills/driver-retention-plan && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "driver-retention-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-plan into .agents/skills/driver-retention-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "driver-retention-plan", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills driver-retention-plan --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/driver-retention-plan .cursor/skills/driver-retention-plan && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "driver-retention-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-plan into .cursor/skills/driver-retention-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "driver-retention-plan", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/driver-retention-plan--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills driver-retention-plan --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/driver-retention-plan .gemini/skills/driver-retention-plan && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "driver-retention-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-plan into .gemini/skills/driver-retention-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "driver-retention-plan", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills driver-retention-planInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/driver-retention-plan .github/skills/driver-retention-plan && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "driver-retention-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-plan into .github/skills/driver-retention-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "driver-retention-plan", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills driver-retention-plan --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/driver-retention-plan .opencode/skills/driver-retention-plan && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "driver-retention-plan" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/driver-retention-plan into .opencode/skills/driver-retention-plan/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "driver-retention-plan", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
driver-retention-plan- GitHub stars
- 1.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 772 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reduce driver turnover by fixing what actually makes drivers leave — the pay comparison that is real, the home-time reliability, the dispatch relationship, and the first ninety days where most…
- Works in 7 steps: Split turnover by tenure. Under 90 days… → Price turnover properly. Recruiting,… → Compare take-home, not rate per mile.… → …
- Asked to improve driver retention
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: Segment by Tenure,… and Output Format, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Driver Retention Plan is an agent skill from mohitagw15856/pm-claude-skills. Reduce driver turnover by fixing what actually makes drivers leave — the pay comparison that is real, the home-time reliability, the dispatch relationship, and the first ninety days where most departures are decided. Use when asked to improve driver retention, reduce turnover, understand why drivers are leaving, or design a driver onboarding or referral programme. Produces the turnover analysis by tenure and cause, the true cost of turnover, the exit-driver findings, the prioritised interventions, and the…
Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Business, Finance & HR. The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked to improve driver retention
- Reduce turnover
- Understand why drivers are leaving
- Design a driver onboarding
Example prompts
- “/driver-retention-plan”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Split turnover by tenure. Under 90 days is a recruiting-and-onboarding failure. One to two years is usually pay or home time. Long-tenure…
- Price turnover properly. Recruiting, training, onboarding, the unseated truck's lost revenue, and the ramp to full productivity. The real…
- Compare take-home, not rate per mile. Drivers compare what lands in their account. Detention that goes unpaid and miles that do not…
- Measure home-time reliability, not the policy. The promise is rarely the problem; the variance is. Track promised versus actual and show it.
- Look at dispatch as a retention factor. Turnover concentrated under one dispatcher is a management finding, and a common one.
- Talk to stayers, not just leavers. Exit interviews capture a rehearsed reason. Stay interviews find the problem while it is still fixable.
- Fix the first 90 days first. It is usually the largest single band and the cheapest to change.
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Driver Retention Plan loads about 1.5k tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 772 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 772 words, ~1,536 tokens.
Download SKILL.mdSave it as
.claude/skills/driver-retention-plan/SKILL.md (or your agent's skills folder).- name
- driver-retention-plan
- description
- Reduce driver turnover by fixing what actually makes drivers leave — the pay comparison that is real, the home-time reliability, the dispatch relationship, and the first ninety days where most departures are decided. Use when asked to improve driver retention, reduce turnover, understand why drivers are leaving, or design a driver onboarding or referral programme. Produces the turnover analysis by tenure and cause, the true cost of turnover, the exit-driver findings, the prioritised interventions, and the first-90-days plan.
Driver Retention Plan
Drivers rarely leave over the pay rate itself; they leave over the gap between what was described at hiring and what the job turned out to be. Home time that slips, a dispatcher who favours other drivers, equipment that keeps breaking, and a first month with no support. This finds which of those is actually costing you drivers, prices the turnover honestly, and fixes the ones that matter.
What This Skill Produces
- Turnover analysis by tenure — because leaving at 30 days and leaving at three years have entirely different causes
- The true cost of turnover — recruiting, onboarding, unseated truck days, and the productivity ramp, which together are usually far larger than assumed
- Exit and stay findings — what leavers say, and more usefully what current drivers say before they leave
- The reality-versus-promise gap — what recruiting describes against what the job delivers
- Prioritised interventions — ranked by drivers retained per pound, not by ease
- The first-90-days plan — where most turnover is actually determined
Required Inputs
Ask for these if not provided:
- Turnover data — by tenure band, by fleet or lane, by dispatcher, and over time
- Exit reasons — what leavers gave, and whether anyone probed past the first answer
- The pay picture — actual take-home including detention and accessorials, versus the market for the same work
- Home time — what is promised at recruitment and what is actually delivered
- The equipment and dispatch position — vehicle age and reliability, and how loads are assigned
Framework: Segment by Tenure, Price the Loss, Fix the Promise Gap
- Split turnover by tenure. Under 90 days is a recruiting-and-onboarding failure. One to two years is usually pay or home time. Long-tenure departures are often equipment or a specific dispatcher. One number hides all three.
- Price turnover properly. Recruiting, training, onboarding, the unseated truck's lost revenue, and the ramp to full productivity. The real figure per driver is usually large enough to change the conversation about pay.
- Compare take-home, not rate per mile. Drivers compare what lands in their account. Detention that goes unpaid and miles that do not materialise both show up there.
- Measure home-time reliability, not the policy. The promise is rarely the problem; the variance is. Track promised versus actual and show it.
- Look at dispatch as a retention factor. Turnover concentrated under one dispatcher is a management finding, and a common one.
- Talk to stayers, not just leavers. Exit interviews capture a rehearsed reason. Stay interviews find the problem while it is still fixable.
- Fix the first 90 days first. It is usually the largest single band and the cheapest to change.
Output Format
Show full SKILL.md (336 more words)Show less
Driver retention plan: [operation] · [period]
Turnover
| Tenure band | Leavers | Rate | Stated reason | Probable actual cause |
|---|---|---|---|---|
| 0–90 days | ||||
| 90 days–1 year | ||||
| 1–2 years | ||||
| 2 years+ | ||||
| By dispatcher: [concentration, if any] · By lane/fleet: [concentration] |
Cost of turnover
| Component | Per driver |
|---|---|
| Recruiting and advertising | |
| Onboarding, training, orientation | |
| Unseated truck (days × revenue per day) | |
| Productivity ramp | |
| Total per departure | |
| Annual cost: [leavers × total] — against a [amount] annual pay increase across [n] drivers |
Promise vs reality
| Recruiting says | Reality | Gap |
|---|---|---|
| Home time [promise] | [actual, and variance] | |
| Earnings [promise] | [actual take-home] | |
| Equipment [promise] | [actual age/condition] | |
| Miles [promise] | [actual] |
Interventions — ranked by drivers retained per pound
| Intervention | Addresses | Est. drivers retained | Cost | Priority |
|---|
First 90 days: day 1 [what] · week 1 [check-in, by whom] · day 30 [structured conversation] · day 60 [ ] · day 90 [ ] · assigned mentor: [role]
Stay interviews: [cadence, who runs them, what is asked, where answers go]
Quality Checks
- Turnover is segmented by tenure, not reported as one rate
- Concentration by dispatcher and by lane was checked
- The cost of turnover includes unseated truck days and the productivity ramp
- Pay is compared as actual take-home, not rate per mile
- Home-time reliability is measured as variance against promise
- Stay interviews are in place, not only exit interviews
- Interventions are ranked by retention per pound spent
- The first 90 days has a specific, owned plan
Anti-Patterns
- One turnover number. Hides three different problems with three different fixes.
- Believing the exit-interview reason. 'Better opportunity' is a polite closing statement, not a cause.
- Comparing rate per mile. Drivers compare take-home, and so should you.
- Auditing the home-time policy instead of the delivery. The variance is the complaint.
- Ignoring dispatcher concentration. Frequently the single largest and most fixable factor.
- Recruiting harder instead of retaining. Costs more per seated truck every time.
- Overselling at recruitment. Every exaggeration becomes a 60-day departure.
Example Trigger Phrases
- "Why are our drivers leaving?"
- "Build a driver retention plan"
- "What does turnover actually cost us per driver?"
- "Most of our leavers go within 90 days — what do we fix?"
- "Design a driver onboarding programme"
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/driver-retention-plan of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Driver Retention Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Driver Retention Plan this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Technical Analysttradermonty/claude-trading-skills | 3k | 4 repos | ~4.6k | Automated safety check: Pass | MIT | |
| Theme Detectortradermonty/claude-trading-skills | 3k | 2 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Creating Financial ModelsChen-zexi/open-ptc-agent | 729 | 3 repos | ~1.3k | Automated safety check: Pass | MIT | |
| Stock APIzhangxiangliang/stock-api | 2k | — | ~507 | Automated safety check: Pass | MIT | |
| Itr Walakaranb192/itr-wala | 871 | — | ~3.6k | Automated safety check: Pass | MIT |
Similar skills
Theme Detector
tradermonty/claude-trading-skills
Detect and analyze trending market themes across sectors. An agent skill from tradermonty/claude-trading-skills.
Creating Financial Models
Chen-zexi/open-ptc-agent
This skill provides an advanced financial modeling suite with DCF analysis, sensitivity testing, Monte Carlo simulations, and scenario planning for investment decisions
Stock API
zhangxiangliang/stock-api
Fetch real-time stock quotes, K-line (candlestick) history, and search symbols for China A-shares, Hong Kong, and US markets.
Itr Wala
karanb192/itr-wala
File Indian income tax returns (ITR) for FY 2025-26 / AY 2026-27.
Tushare Data
zillionare/zillionare
面向中文自然语言的 Tushare 数据研究技能。用于把“看看这只股票最近怎么样”“帮我查财报趋势”“最近哪个板块最强”“北向资金在买什么”“给我导出一份行情数据”这类请求，转成可执行的数据获取、清洗、对比、筛选、导出与简要分析流程。适用于 A 股、指数、ETF/基金、财务、估值、资金流、公告新闻、板块概念与宏观数据等研究场景。
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Related
Categories
Questions about Driver Retention Plan
What does Driver Retention Plan do?
Reduce driver turnover by fixing what actually makes drivers leave — the pay comparison that is real, the home-time reliability, the dispatch relationship, and the first ninety days where most…. Driver Retention Plan is an agent skill from mohitagw15856/pm-claude-skills. Reduce driver turnover by fixing what actually makes drivers leave — the pay comparison that is real, the home-time reliability, the dispatch relationship, and the first ninety days where most departures are decided.
When should I use Driver Retention Plan?
Driver Retention Plan fits situations like: asked to improve driver retention; reduce turnover; understand why drivers are leaving; design a driver onboarding.
How do I install Driver Retention Plan in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a claude-code`. Or copy the skill folder (skills/driver-retention-plan in mohitagw15856/pm-claude-skills) into .claude/skills/driver-retention-plan in your project. Claude Code loads it when a task matches its description.
How do I install Driver Retention Plan in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a codex`. Or copy the skill folder (skills/driver-retention-plan in mohitagw15856/pm-claude-skills) into .agents/skills/driver-retention-plan in your project. Codex loads it when a task matches its description.
Can I use Driver Retention Plan in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill driver-retention-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/driver-retention-plan, .gemini/skills/driver-retention-plan, .github/skills/driver-retention-plan and .opencode/skills/driver-retention-plan in your project.
What does Driver Retention Plan need to run?
SKILL.md names no scripts, command-line tools or credentials: Driver Retention Plan is instructions for the agent only.
Does Driver Retention Plan access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Driver Retention Plan safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Driver Retention Plan use?
Driver Retention Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Driver Retention Plan use?
About 1.5k tokens (SKILL.md is roughly 6.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Driver Retention Plan?
Skills that share tags, products or a category with Driver Retention Plan: Technical Analyst (tradermonty/claude-trading-skills, 3k stars), Theme Detector (tradermonty/claude-trading-skills, 3k stars), Creating Financial Models (Chen-zexi/open-ptc-agent, 729 stars) and Stock API (zhangxiangliang/stock-api, 2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Driver Retention Plan?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.