4,631 件 ・ 関連度順
概要と使いどころ
Use this skill when the user asks how to build + manage direct shipper relationships — moving from spot market to dedicated lanes, customer scoring + credit assessment, contract terms, dedicated capacity agreements, KPI reporting, and how to handle customer disputes. Reference standard customer-carrier contract terms.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about CMV vehicle inspections under 49 CFR 396 — DVIRs (Driver Vehicle Inspection Reports), pre-trip inspections, post-trip inspections, periodic inspections, annual inspections, who can perform inspections, OOS criteria, and what makes a "no defect" DVIR valid. Cite 49 CFR 396.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about trucking rate negotiation — cost-plus pricing, market rate benchmarking via DAT/Truckstop, fuel surcharge math, how to negotiate with brokers/shippers, when to walk away, contract pricing vs spot rates. Reference DAT Rate Analytics + freight market reports.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks how to build, measure, or improve safety culture in a motor carrier — leading vs lagging safety indicators, blame-free reporting, near-miss programs, safety committee structure, monthly safety meetings, ATA Safety Management Program guidance, and how to evaluate cultural maturity. Reference ATA SMP + DOT safety culture research.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about International Fuel Tax Agreement (IFTA) compliance — quarterly returns, jurisdiction reporting, fuel + miles reconciliation, IFTA-100/101 forms, base jurisdiction selection, IFTA license + decals, recordkeeping requirements, common IFTA audit findings, or how to handle non-IFTA jurisdictions. Cite IFTA Articles of Agreement.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about the FMCSA Drug & Alcohol Clearinghouse — full vs limited query, pre-employment vs annual query, query credit purchasing, who has access (employers, drivers, MROs, SAPs, state licensing agencies), reporting violations to the Clearinghouse, the "prohibited" status workflow, consent forms, or how to register/use the clearinghouse.fmcsa.dot.gov portal. Cite 49 CFR 382.701-727.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when an inspection report identifies the wrong driver. Covers how to file a DataQ challenge for driver ID errors, evidence requirements, and reversal rates.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about onboarding a new CDL driver — pre-hire process, day-zero requirements, application + DQF setup, road test, drug & alcohol pre-employment, Clearinghouse Full query, MVR initial pull, PSP report, ELDT verification, sequence of activities + timing, and what NOT to do (handing keys before testing complete). Cite 49 CFR 391, 382.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a carrier asks about fuel-card vendor selection (Comdata, EFS, WEX, RTS, Pilot Flying J, Love's Connect), discount levels, fraud control, driver authorization PINs, IFTA reporting features, cash advance, money codes, or how the card fits into payroll/settlement workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to use the Pre-Employment Screening Program (PSP) for evaluating driver applicants. Covers what PSP shows, cost, and how to interpret reports.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to investigate a crash effectively. Covers preservation of evidence, witness statements, dashcam review, and reporting timeline.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end Coval audio-quality testing workflow. Launches one run per audio-robustness scenario against the same voice agent + test set + metrics, polls for completion, and produces the multi-run report URL grouped by Persona. Use when a user wants to follow the Testing Across Audio Qualities cookbook (https://docs.coval.dev/guides/testing-across-audio-qualities) without doing each step by hand.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end Coval adversarial / red-team testing workflow. Builds one adversarial test set (12 core attack vectors plus legitimate controls, each with an expected-behavior checklist), creates a persistent "Adversarial User" persona and a Composite Evaluation metric that scores each scenario against its own expected behaviors, launches a multi-iteration run against the agent (voice or chat), polls for completion, builds a per-scenario pass/fail scorecard, and creates a saved report grouped by Test Case. Use when a user wants to follow the Adversarial & Red-Team Testing cookbook (https://docs.coval.dev/guides/adversarial-red-team-testing) without doing each step by hand. Triggers: "adversarial test set", "red team my agent", "jailbreak / prompt-injection testing", "test my agent against bad actors".
日本語の概要は準備中です。原文の説明を表示しています。
Pre-commitment attack on a plan by an agent that did not write it. Use when presenting a feature-deep-dive plan, assigning vision-to-fleet briefs, moving a register to build mode, ratifying a scope list, or coding a new contract or table. NOT for built work or DONE reports (use subagent-dispatch).
日本語の概要は準備中です。原文の説明を表示しています。
Scheduled patrol that finds real persistence and error bugs and fixes them. Use when running the system-error repair patrol automation, or when stuck rows, SLA breaches, the system_errors queue, or app_log ERROR rows need a repair rather than a report.
日本語の概要は準備中です。原文の説明を表示しています。
Run the full on-track check on a conversation, project, or keyword the owner names: find the sessions, extract exactly what he typed, dispatch independent judges who go to the live product as him and report what was missed, plan the remedy, and return one page — what he will see, what is missing, the plan. Use when told to check whether work is on track, to audit a project that has drifted, on 'run the on-track check on X', or when a long campaign is about to freeze, hand off, or claim done.
日本語の概要は準備中です。原文の説明を表示しています。
Continuous localhost UI iteration loop with Arman, through full surface certification. Use when he asks to fix, refine, review, or iterate on a page, route, panel, overlay, or other UI while he may inspect localhost. NOT for a report-only UI audit.
日本語の概要は準備中です。原文の説明を表示しています。
The re-measure and standing report of the canonical data model's live DB conformance. Use when asked 'where are we at' on DB drift or conformance, to update the drift numbers, when a drift-audit brief is re-issued, or on /drift-audit. NOT the per-table fix recipe (use matrx-frontend's db-canonicalize-table).
日本語の概要は準備中です。原文の説明を表示しています。
Toolkit for styling artifacts with curated themes (slides, docs, reports, HTML landing pages, and more). Use when you need consistent typography and color systems or want to generate a new theme on the fly.
日本語の概要は準備中です。原文の説明を表示しています。
Perform language and framework specific security best-practice reviews and suggest improvements. Use when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go), and not for general debugging or non-security tasks.
日本語の概要は準備中です。原文の説明を表示しています。
課題のレポート・小論文部分を，出題文・採点基準の要求を過不足なく満たす形で執筆する．「レポートを書いて」「この設問に答えて」など，課題文書の執筆を求められたときに使う（既存文書の推敲だけなら /refine:docs を使う）．
Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.
日本語の概要は準備中です。原文の説明を表示しています。
Run every Convex audit (authz, reviewer, advisor, insights) into one scored, deduped readiness report with an ordered fix plan — Lighthouse for your backend.
日本語の概要は準備中です。原文の説明を表示しています。