2.5万 件 ・ 関連度順
概要と使いどころ
Use this skill when the user asks how to pay CDL drivers — cents per mile (CPM), percentage of revenue, hourly, salary, sleeper-team rate, detention pay, driver-pay laws under FLSA (Fair Labor Standards Act), and how each model affects retention + recruitment. Cite FLSA + state wage laws.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when buying another carrier and inheriting their drivers' DQF library. Covers the legal transfer of DQ records, what new owner must verify, and gaps that commonly require remediation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when an owner-operator (single CDL driver, single operating authority) needs to comply with random testing. Covers consortium membership, pool size requirements, and self-employed driver rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about Driver Qualification Files (DQF) — what must be in a DQ file under 49 CFR 391, retention periods, what's required pre-hire vs ongoing, document expiration tracking, audit-readiness for driver files, common DQF deficiencies that auditors find, or how to handle missing documents on existing drivers. Always cite the specific subsection of 49 CFR 391.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to evaluate which DataQ challenges have winning evidence and which don't. Covers documented vs anecdotal evidence and the 8 high-success patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to track recent and upcoming SMS methodology changes from FMCSA. Covers proposed rule changes, comment periods, and implementation timelines.
日本語の概要は準備中です。原文の説明を表示しています。
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 about Electronic Logging Device (ELD) compliance under 49 CFR 395.20-38 — ELD mandate, AOBRD vs ELD transition, ELD exemptions, ELD malfunctions, 8-day paper backup, ELD certification on FMCSA registered list, data file integrity, edits + annotations, driver portability, and how to handle ELD failures at roadside. Cite 49 CFR 395.20-395.38.
日本語の概要は準備中です。原文の説明を表示しています。
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 how to interpret a DOT medical examiner's findings — what restrictions mean (corrective lenses, hearing aid, no insulin, etc.), what conditions trigger short-term vs 24-month certificates, vision/hearing thresholds, blood pressure categories, sleep apnea screening, when to seek an exemption program, and how to handle a downgrade or denial. Cite 49 CFR 391.41-49 and the FMCSA Medical Examiner Handbook.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks what emergency equipment a CMV must carry under 49 CFR 393.95 — reflectorized triangles, flares, fire extinguishers, spare fuses, exceptions for buses/passenger CMVs, where to mount/store equipment, and what roadside inspectors check. Cite 49 CFR 393.95 + 393.97.
日本語の概要は準備中です。原文の説明を表示しています。
Use when discussing the mobile apps drivers use day-to-day — load boards (DAT, Truckstop), route planners (Trucker Path, CoPilot Truck), expense and per diem apps (Per Diem Plus), parking apps (Park My Truck), maintenance / DVIR apps, and how these stack with the carrier's ELD app.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to understand the FMCSA cargo securement standards. Covers § 393.100-§ 393.136 general rules, tiedown requirements, working load limits.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about FMCSA Compliance Safety Accountability (CSA) program scoring — the seven BASIC categories, BASIC Severity Indicator (BSI), peer percentiles, intervention thresholds, how violations age out, SMS Methodology, ISS (Inspection Selection System), what "alert" status means, Safety Measurement System mechanics, or DataQ disputes. Cite SMS Methodology v3.20.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to understand why CSA BASIC alert thresholds differ across carrier types. Covers general freight (65th percentile), passenger/hazmat (60th), and the regulatory rationale.
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end form handling with react-hook-form, Zod schemas, validation patterns, error messaging, field arrays, and multi-step wizards. Use for complex forms, validation architecture, autosave, field dependencies. Activate on "form validation", "react-hook-form", "Zod", "form error", "multi-step form", "wizard". NOT for simple HTML forms, backend validation only, or non-React frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when running analytical SQL over Parquet/CSV/JSON without a warehouse, replacing pandas for data wrangling, joining S3 data in-place, building local data marts, or embedding OLAP into an app. Triggers: read_parquet/read_csv setup, partitioned dataset queries, hive partitioning, glob patterns for S3, COPY TO export, attach Postgres/MySQL, UDFs in Python/R, MotherDuck cloud sync, columnar performance vs row stores. NOT for OLTP workloads (concurrent writes), distributed analytics at petabyte scale (use Spark/Trino), or vector search (use pgvector/Lance).
日本語の概要は準備中です。原文の説明を表示しています。
Defensive counterpart to federated-harbor-redteam: closes the smells that red team opens against The Federated Harbor whitepaper. Federation-specific defenses for cross-harbor primitives — mechanization commitments, scope hedges, cross-paper dependency formalization, pre-emptive analogies (CT, Macaroons, atomic swaps), and defense-in-depth framing (refuses vs prices). Use during a versioned red-vs-white round; pairs with federated-harbor-redteam. NOT for ad-hoc code review, NOT for the Anchor or Bonded papers (use whitehat-defense).
日本語の概要は準備中です。原文の説明を表示しています。
Structure persuasive speeches and formal arguments in forensic, legal, policy, and competitive debate styles. Use when the user needs to prepare talks, opening or closing arguments, policy pitches, public explanations, debate speeches, or mentions 'forensic speech', 'formal argument', 'persuasive speech structure', 'debate speech', 'opening statement', 'closing argument'. Turns structured claims into audience-tuned persuasive delivery.
日本語の概要は準備中です。原文の説明を表示しています。
Drafting and iterating sections of The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor (local identity) and Bonded Commons (local coordination), extending coordination across machines and administrative domains. Use when authoring a section, rewriting a section after a redteam/whitehat round, or composing a new chapter. NOT for marketing copy, NOT for the other two papers, NOT for production threat response.
日本語の概要は準備中です。原文の説明を表示しています。
Audit whether a "current product focus receipt" (Decision/Now/Why-now/Evidence/Not-now/Cut-suspend/First-visible-proof/ Acceptance-gate/Kill-revisit-trigger/Owner/Review-date) and the work order it gates state a real, testable decision and a real agent launch — not planning-placeholder prose that sounds like an assignment but can't be proven. Use when deciding whether to launch an agent chain against a milestone or a stated "focus," when a work order lacks explicit input/output/owner/proof-gate, or when an acceptance gate would only prove a cached UI state instead of daemon truth. NOT for distinguishing roadmap items from energy-driven sidequests (legible-roadmap-with-sidequests), reviewing a PRD/prototype for product-completeness gaps like cold start or pricing (product-reality-reviewer), or accepting already-finished work against a personal acceptance bar (port-daddy-user-surrogate-pm-review).
日本語の概要は準備中です。原文の説明を表示しています。
Design dashboards for migrations and runtimes. Use for authority drift, verifier status, burn-down, runtime health, or pain panels. NOT for vanity analytics, ad hoc charts, or duplicate reporting.
日本語の概要は準備中です。原文の説明を表示しています。
Use when introducing a feature flag system, choosing between release flags / experiment flags / operational flags / kill switches / permission flags, designing percentage rollouts, building kill-switch + circuit-breaker patterns, structuring evaluation contexts (user IDs, plan tier, region), or building flag-cleanup discipline. Triggers: LaunchDarkly / GrowthBook / Unleash / Flagsmith / OpenFeature, percentage ramp, sticky bucketing, kill switch wired to alerting, "we still have flags from 2 years ago", flag debt, OpenFeature provider, evaluation context, default value on provider failure. NOT for A/B test statistical analysis (separate skill), traffic-split routing at the edge, build-time bundler defines, or environment-based config.
日本語の概要は準備中です。原文の説明を表示しています。
Analytical methods for decomposing expert performance into cognitive and physical task components
日本語の概要は準備中です。原文の説明を表示しています。