4,002 件 ・ 関連度順
概要と使いどころ
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 when a carrier owner, CFO, or controller asks how to build an annual budget, monthly P&L model, cash flow forecast, scenario plan, or break-even analysis for a trucking operation. Covers revenue modeling, cost structures, capital planning, and the discipline of tracking actuals vs budget.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about cargo securement requirements under 49 CFR 393 Subpart I — Working Load Limit (WLL), tiedown counts, tiedown types, commodity-specific securement rules (lumber, metal coils, paper rolls, concrete pipe, intermodal containers, vehicles, large boulders, dressed lumber, building materials), CVSA out-of-service criteria, and how to calculate aggregate WLL. Cite 49 CFR 393.100-136.
日本語の概要は準備中です。原文の説明を表示しています。
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 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 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 accident claims management — first-notice-of-loss procedures, working with insurance adjusters, claim severity classification, subrogation, claim closure timelines, and how to influence claim outcomes. Different from accident-investigation-playbook (which covers facts); this covers the insurance + claim side.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when FMCSA conducts an off-site investigation (less formal than CR). Covers the document-request approach and how to respond efficiently.
日本語の概要は準備中です。原文の説明を表示しています。
No-loss protocol for changing an existing mandate's output contract. Use when changing what an agent or mandate emits or how it is typed: binding a kind, declaring output_kind, kind-backfill batches, provision reconciliation, or any make-this-contract-honest sweep. NOT for creating a new agent (use create-agent).
日本語の概要は準備中です。原文の説明を表示しています。
The quick interview that captures a Domain's or major Feature's minimal (go-live) and final vision verbatim into its VISION.md. Use when a node shows VISION MISSING, a registry domain is ratified without a vision, gap analysis lacks a go-live bar, or on /domain-vision-interview <domain>.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze an idea, proposal, change, claim, or decision from facts through problem, value, mechanism, consequences, evidence, alternatives, and action. Use when the user asks what something is for, why it matters, whether it is worth doing, what impact it has, or how to decide. Do not use for simple factual lookup or straightforward execution.
日本語の概要は準備中です。原文の説明を表示しています。
Error handling patterns and best practices for OneKey. Use when implementing try/catch blocks, handling async errors, showing error messages, or managing error states in UI. Triggers on error, try, catch, exception, throw, fail, failure, error handling, error boundary, useAsyncCall, toast, fallback, error state.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic amplification mode that reveals blind spots, untapped opportunities, and hidden leverage points in any business strategy, entrepreneurship idea, or creative content project. Cuts through noise to show what others miss.
日本語の概要は準備中です。原文の説明を表示しています。
Describes the NemoClaw plugin and blueprint architecture and how they orchestrate the OpenClaw sandbox. Use when looking up architecture, plugin structure, or blueprint design. Trigger keywords - nemoclaw architecture, nemoclaw plugin blueprint structure, nemoclaw cli commands, nemoclaw command reference, nemoclaw network policy, sandbox egress control operator approval, nemoclaw troubleshooting, nemoclaw debug sandbox issues.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and optimize tweets for maximum reach using Twitter's open-source algorithm insights. Rewrite and edit user tweets to improve engagement and visibility based on how the recommendation system ranks content.
日本語の概要は準備中です。原文の説明を表示しています。
Tracks complex, multi-session work using the Beads issue tracker and dependency graphs, and provides persistent memory that survives conversation compaction. Use when work spans multiple sessions, has complex dependencies, or needs persistent context across compaction cycles. Trigger with phrases like "create task for", "what's ready to work on", "show task", "track this work", "what's blocking", or "update status".
日本語の概要は準備中です。原文の説明を表示しています。
Write strategy-oriented Product Requirements Documents (PRDs) for AI product managers. Use when: (1) drafting a new PRD or strategy doc, (2) structuring a feature proposal with strategy rationale, (3) writing requirement docs that emphasize "why" over "how", (4) turning raw product ideas into structured requirement documents. NOT for: purely technical specs, engineering tickets, or UI copy.
日本語の概要は準備中です。原文の説明を表示しています。
UX and interaction design — UI, interface, wireframe, mockup, prototype, user experience, user journey, usability, accessibility audit, onboarding flow. The "how users think and move through it" domain.
日本語の概要は準備中です。原文の説明を表示しています。
Tear down a company on request — "do a teardown of", "break down this company", "analyze this competitor's business". Fixed-template output: business model, how they make money, positioning, and where they are exposed.
日本語の概要は準備中です。原文の説明を表示しています。
Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.
日本語の概要は準備中です。原文の説明を表示しています。
.NET unit test fundamentals and FIRST principles specialized skill. Used when creating unit tests, understanding testing basics, learning 3A Pattern, and mastering testing best practices. Covers FIRST principles, AAA Pattern, Fact/Theory, testing pyramid, etc. Keywords: unit test, unit test, unit testing, test fundamentals, testing fundamentals, FIRST principle, FIRST principle, 3A pattern, AAA pattern, Arrange Act Assert, Fact, Theory, InlineData, how to write tests, testing best practices, create unit test
日本語の概要は準備中です。原文の説明を表示しています。
Decides how to test .NET code. Unit vs integration vs E2E decision tree, test doubles.
日本語の概要は準備中です。原文の説明を表示しています。
Test naming conventions and best practices specialized skill. Used when naming test methods, improving test readability, and establishing naming standards. Covers three-part naming method, Chinese naming recommendations, test class naming, etc. Keywords: test naming, test naming, naming conventions, naming conventions, three-part naming, three-part naming, method_scenario_expected, method_scenario_expected, how to name tests, test readability, naming best practices, test report, test documentation
日本語の概要は準備中です。原文の説明を表示しています。
xUnit test project creation and setup specialized skill. Used when creating test projects, setting up project structure, configuring NuGet packages, and organizing test folders. Covers csproj setup, package management, project structure, xunit.runner.json configuration, etc. Keywords: xunit project, xunit setup, create test project, test project setup, create test project, project structure, project structure, folder structure, xunit package, nuget packages, testing packages, how to create test project, xunit configuration
日本語の概要は準備中です。原文の説明を表示しています。