본문으로 건너뛰기
cccskills
무료GitHub에 공개

car-tco

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 payment. Use when asked should I lease or buy a car, is it cheaper to keep my old car, what does this car really cost per month, or new vs used total cost. Produces the ranked scenario totals, per-month true cost, the assumption ledger, and the not-modeled list.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(3)

  • SKILL.md4.4 KB
  • references/worked-example.md4.1 KB
  • scripts/car_tco.py4.0 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Car TCO Skill

Cars are sold on monthly payments and owned on total cost — and the two rank options differently. Depreciation (the biggest cost of a new car) never appears on a statement; maintenance (the biggest fear about an old car) is usually smaller than a year of new-car depreciation. This skill compares buy-new, buy-used, lease-forever, and keep-current on the same total-cost basis over the same horizon.

What This Skill Produces

  • Ranked scenario totals — every requested scenario over the same horizon, cheapest first
  • True per-month cost — total ÷ months, the number to compare against the payment the dealer quotes
  • The assumption ledger — depreciation curve, maintenance ramp, insurance deltas, all labeled
  • The not-modeled list — financing interest, jurisdiction taxes, reliability luck

Required Inputs

Ask for these if not provided:

  • Which scenarios to compare — any of: new price, used-equivalent price, lease terms, current car's value + annual maintenance
  • Horizon — years they realistically keep cars (default 8, labeled); short horizons flatter leasing, long ones flatter buying
  • Miles per year and rough fuel/energy cost (defaults 12,000 mi / $0.14 per mile, labeled)

Programmatic Helper

python3 scripts/car_tco.py --new-price 38000 --used-price 24000 --lease-month 420 --keep-value 9000
python3 scripts/car_tco.py --new-price 38000 --keep-value 9000 --keep-maint 1800 --horizon 6 --json

Deterministic. Depreciation: 20% year one then 10%/yr for new, gentler for used/current. Maintenance ramps 8%/yr (used cars start further up the ramp). Leases re-lease at each term end with a fresh drive-off. Resale value is credited back — TCO is what you spent minus what you can recover.

Framework: The Payment Illusion Rules

  • Depreciation is the invisible line item — a new car's largest cost has no bill; it's the resale-value credit shrinking
  • "My old car needs $2,000 of work" is usually cheap — compare the repair to a year of the replacement's depreciation before calling it "not worth fixing"
  • Leasing buys flexibility, not savings — lease-forever means paying peak depreciation years forever; price that honestly and let people buy flexibility knowingly
  • Margins under ~10% are noise — the model's assumptions can't resolve differences that small; say "roughly a tie," not a winner
  • The horizon drives the ranking — always name it; the same inputs rank differently at 3 years vs 10

Output Format


Car TCO: [scenarios] over [N] years

The Ranking

[Script output: totals cheapest-first, per-month true cost]

Reading the Ranking

[Two sentences: how far apart the options really are, and which assumption could flip the order.]

What This Model Ignores

Financing interest (run the loan separately) · taxes and fees by jurisdiction · reliability variance (a lemon breaks any model) · the non-financials (safety features, the want).

Educational model, not financial advice — verify with a licensed professional before acting on it.


Quality Checks

  • All scenarios use the same horizon and mileage
  • Resale value is credited back in every ownership scenario
  • Per-month true cost appears next to the totals
  • Sub-10% margins are called ties, not winners
  • The disclaimer line appears in the artifact

Anti-Patterns

  • Do not rank on monthly payment — that's the illusion this skill exists to correct
  • Do not omit depreciation or resale from ownership scenarios
  • Do not treat maintenance fears as data — use the ramp, and compare repairs to replacement depreciation
  • Do not extrapolate one scenario's horizon onto another (a 3-year lease vs 8-year ownership is not a comparison)
  • Do not moralize the want — price the options honestly and let the user choose with open eyes

Example Trigger Phrases

  • "Should I lease?"
  • "Buy a car."
  • "Is it cheaper to keep my old car?"
  • "What does this car really cost per month?"

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 23일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고