1.3천건 · 관련도순
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier asks which KPIs to track, how to build a fleet dashboard, what targets to set, cadence for reviewing metrics (daily / weekly / monthly / quarterly), and how to operationalize data into actions. Covers safety, operations, financial, driver, and customer KPIs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a dispatcher, operations manager, or owner asks how to plan loads to minimize empty (deadhead) miles, sequence freight efficiently, balance regional capacity, design dedicated loops, or build a load-pairing strategy across customers. Covers loaded-ratio math, lane balance, region-pair pricing, and software-supported optimization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier (asset-based, brokerage, or 3PL) asks how to respond to a shipper RFP / RFQ — bid packaging, lane analysis, rate strategy, SOPs/SOWs, qualifications response, insurance compliance, EDI requirements, and how to win competitive bids without leaving margin on the table.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about trucking dispatch software — McLeod, TMW (Trimble), Tailwind, Truckbase, AscendTMS — vs load boards — DAT, Truckstop, 123Loadboard, Convoy, Uber Freight. Covers the workflow (find load, book, dispatch, run, settle), how dispatch software integrates with ELDs + accounting + customer EDI, and what small fleets vs larger fleets typically use.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about CMV operation types — Dedicated, OTR (Over-the-Road), Regional, Local, and the differences in driver lifestyle, pay, equipment, home time, hours, and customer mix. Reference industry segmentation conventions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a manager, dispatcher, or safety director needs to have a coaching conversation with a driver — about a safety event (harsh brake, hard turn, distraction), an HOS violation, a customer complaint, a missed delivery, repeated minor incidents, or to deliver positive recognition. Covers conversation structure, language, documentation, and escalation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks how to market a trucking company — sales channels, prospecting, website + brand, industry directories (D&B Hoovers, ZoomInfo), referral programs, content marketing, and ROI of different acquisition channels. Reference industry sales practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks how to manage a trucking carrier's public reputation — handling a major accident in the news, social media + Glassdoor + Indeed reviews, customer disputes that escalate, employee disputes, regulator perception, and how to communicate during a crisis. Reference industry PR + crisis communication practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about buying or selling a trucking company — valuation drivers (revenue, fleet age, CSA scores, customer concentration), asset purchase vs stock purchase, FMCSA authority transfer, due diligence checklist, common deal structures (cash, earnout, seller-financed), and what changes operationally after acquisition. Reference 49 CFR 365.401 (authority transfer).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a carrier asks about disaster recovery (DR) and business continuity planning (BCP) — cyber incident, natural disaster, terminal loss, key-person departure, financial liquidity event, major customer loss, insurance crisis, or fuel supply disruption. Covers risk assessment, continuity strategy, communication plans, and recovery time objectives.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to explain to customers/sales prospects why FMCSA CSA scores are not available in real-time. Covers the SAFER refresh cycle and what 'real-time' actually means for CSA data.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about cybersecurity for a trucking carrier — protecting ELD data, customer information, financial systems, EDI integrations, fleet telematics, ransomware risk, vendor / shipper data sharing, incident response, and FMCSA cyber-recommendations. Reference NIST + CISA cybersecurity frameworks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Operationalizing an expungement website — user intake flows, document generation pipelines, court filing integrations, payment processing, state-by-state workflow variations, customer support for sensitive populations, and the handoff between automated systems and human legal review. Activate on 'expungement operations', 'legal tech SaaS', 'court filing integration', 'document automation pipeline', 'expungement business', 'legal service workflow', 'multi-state legal operations'. NOT for expungement law itself (use national-expungement-expert), web design (use legal-tech-web-design), or legal document drafting (use recovery-app-legal-terms).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Own whether a multi-document product-architecture binder is internally consistent, complete against its stated customer/contingency/architecture coverage, and honest about which older product ambitions it has absorbed, superseded, deferred, contradicted, orphaned, or rejected. Use when running a binder Architect of Record pass, before an implementation chain cites a binder chapter as ready, when a proof-gate owner is missing, or when reconciling the binder against the older ambition corpus (website, plans, examples, ADRs). NOT for auditing a single Claude Skill bundle's structure or frontmatter (use skill-hygiene), rendering a single-PM accept/reject verdict on one finished deliverable (use port-daddy-user-surrogate-pm-review), or sequencing/stewarding a roadmap's sidequests once a gap or operator decision has been surfaced (use legible-roadmap-with-sidequests).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
End-to-end Coval accent testing workflow. Creates one persona per accent (each using a distinct accent voice and mirroring your Standard Customer behavior), launches one run per accent against the same voice agent + test set + metrics, polls for completion, builds a per-persona comparison table from the results, and creates the saved multi-run report (grouped by Persona) via the public API. Use when a user wants to follow the Testing Across Accents cookbook (https://docs.coval.dev/guides/testing-across-accents) without doing each step by hand.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Migrate configuration from Bluejay voice AI testing platform to Coval. Use when customer says "migrate from bluejay", "bluejay migration", "import bluejay config", or needs to transfer agents, simulations, metrics, and schedules from Bluejay to Coval.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Connect a customer agent to Coval and complete a small first evaluation with inspected voice or chat results. Use when no usable evaluation exists yet; reuse existing recordings and resources when available.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Improve Coval trace quality after basic ingestion works. Use when traces are sparse, missing useful STT/LLM/TTS/tool spans, missing attributes needed for Coval built-in metrics, or when a customer wants maximum debugging and observability value from agent traces.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automatically creates user-facing changelogs from git commits by analyzing history, categorizing changes, and transforming technical entries into customer-friendly release notes. Use when preparing release notes from commit logs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Draft professional emails for various contexts including business, technical, and customer communication. Use when the user needs help writing emails or composing professional messages.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when managing post-purchase experience, building customer loyalty, or increasing repeat purchases
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.