2.9만건 · 관련도순
Use this skill when the user asks how to design or improve a fleet safety scorecard — what KPIs to track, how to weight them, telematics signals vs document compliance vs roadside outcomes, monthly cadence, driver-facing vs admin-facing dashboards, gamification considerations, peer-comparison metrics, and how a scorecard ties to insurance premiums + retention. Reference SMS Methodology v3.20 for industry-standard weights.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about driver discipline — when to coach vs warn vs suspend vs terminate, progressive discipline frameworks, at-will employment in trucking, documenting violations, separating "willful violation" from "human error," and how to handle a driver who refuses corrective action. Reference state employment law + ATA SMP.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when a carrier's CSA peer group changes. Covers what triggers reassignment, how percentile changes affect alert status, and how to interpret the shift.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 what CSA data the public sees about your carrier and how that affects business. Covers SAFER, accessibility, and what's hidden vs visible.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about Environmental Health & Safety (EHS) for trucking — fuel spill response, hazmat release reporting, EPA + state environmental reporting, emergency contact information (CHEMTREC), environmental impairment liability insurance, and how to handle a CMV-related environmental incident. Cite 40 CFR + 49 CFR 174.6.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to investigate a crash effectively. Covers preservation of evidence, witness statements, dashcam review, and reporting timeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about the agricultural exemption from Hours of Service (HOS) rules under 49 CFR 395.1(k) — what qualifies as agricultural commodity, the 150-air-mile radius rule, state-declared planting/harvest seasons, livestock hauling specifics, and how to document operations under the exemption. Cite 49 CFR 395.1(k) and 49 USC 5117.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about Americans with Disabilities Act (ADA) accommodation for CDL drivers — interaction between ADA + FMCSA medical certification, when DOT-disqualifying conditions trigger ADA analysis, reasonable accommodation case examples, employer obligations, and how to handle a driver with a condition that may affect CDL status. Cite Title I ADA + 49 CFR 391.41.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to maintain your FMCSA operating authority. Covers renewal cycle, fees, and reinstatement after lapse.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to understand what's permissible when reviewing a driver applicant's social media. Covers privacy law, EEOC concerns, and best practices.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill for transporting logs. Covers § 393.116 specific rules, bunks, stakes, and tiedowns required.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about trucking terminology — bobtail vs deadhead vs loaded vs empty trailer — and the insurance, weight, and fuel-tax implications of each. Covers bobtail insurance (also called non-trucking liability), how to track bobtail miles for state taxes, and when "deadhead" affects driver pay.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill when the user asks about FCRA adverse action procedures — what to do when a background check (MVR, criminal, drug test) returns information that may lead to denying employment or terminating a CDL driver. Covers the 5-business-day pre-adverse-action notice, FCRA Summary of Rights, final adverse action notice, state-specific add-ons (CA, NY, etc.), and how to handle disputes. Cite 15 USC § 1681 (FCRA) and 49 CFR 391.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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 how FMCSA calculates the Crash Indicator BASIC. Covers what crashes count, severity weighting, time weighting, and the preventability program.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use this skill to understand when to update your USDOT number registration (MCS-150). Covers triggers, frequency, and consequences of late updates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
An innate exploratory drive that guarantees no graph node remains permanently invisible to an agent population. After a warm-up period (step > 3), each agent fires a coverage scan with probability |unseen_nodes| / |all_nodes|. When triggered, the agent teleports directly to the globally unseen node with the highest belief uncertainty, works it, and returns control to the normal action-selection loop. Probability is self-annealing: it starts near 1.0 when almost everything is unseen and decays toward 0.0 as coverage saturates, requiring no manual schedule. The mechanism is "innate" (hard-coded into the agent step loop) as distinct from the "adaptive" EFE path, which requires local neighbors and learned precision weights. Together they form a two-layer exploration architecture: adaptive for locally-guided foraging, innate for topological completeness.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for sensemaking, frame revision, anomaly handling, questioning strategy, and ambiguity diagnosis with the Data/Frame model before action is chosen. NOT for deterministic classification, settled execution planning, or situations where the frame is already stable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expo managed workflow expert for EAS Build, Submit, Update, config plugins, and custom dev clients. Activate on: Expo project, EAS Build, EAS Update, config plugin, expo-dev-client, Expo Router, Expo SDK 52, app.json configuration. NOT for: bare React Native (use react-native-architect), native module authoring (use react-native-architect), Flutter (use flutter-bloc-state-manager).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs, reconciles, and reviews an end-to-end Drydock program for safely staging agent runtimes: immutable worktree provenance, disposable VM containment, typed effect brokerage, global body accounting, resurrection, subscription-capacity economics, context compaction, operator control, evidence, and promotion. Use when several Drydock contracts must compose into one architecture, implementation hypertree, diagram set, or release plan. NOT for launching Port Daddy, running an untrusted subject, replacing focused containment/resurrection/capacity audits, or treating a design packet as runtime authority.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.