Use this skill to maintain a compliant DOT accident register. Covers § 390.15 requirements, what's recorded, retention period.
日本語の概要は準備中です。原文の説明を表示しています。
1,580 件 ・ 関連度順
概要と使いどころ
Use this skill to maintain a compliant DOT accident register. Covers § 390.15 requirements, what's recorded, retention period.
日本語の概要は準備中です。原文の説明を表示しています。
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 to determine if your carrier should check sex offender registries when hiring drivers. Covers legal requirements, EEOC considerations, and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for transporting heavy machinery (construction, agricultural, industrial). Covers § 393.130 rules, lashing requirements, and platform compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks about FMCSA's Crash Preventability Determination Program (CPDP) — how to dispute that a crash was non-preventable, eligible crash types, evidence requirements, how preventability findings affect SMS scoring + safety ratings, the difference between "preventability" and "fault," and the National Crash Preventability Program. Cite FMCSA CPDP guidance.
日本語の概要は準備中です。原文の説明を表示しています。
Build a compact Coval test set from product requirements, observed conversation failures or a coverage gap. Design realistic scenarios with separate expected behaviors, provenance and controlled voice/persona variation.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
Use when starting creative work (features, components, functionality, or behavior changes) to clarify user intent, requirements, and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Turn vague Acceptance Criteria into measurable checks and test assertions
日本語の概要は準備中です。原文の説明を表示しています。
Parse and validate project specifications. Use when loading YAML/JSON specs, validating spec structure, extracting requirements, or converting between spec formats.
日本語の概要は準備中です。原文の説明を表示しています。
[02] META. Create new skills when existing ones don't cover the task. Analyze unique requirements, build framework (Frame → Research → Plan → Execute), integrate risks, and declare new skill. Use when facing novel problems that existing skills can't address.
日本語の概要は準備中です。原文の説明を表示しています。
Python testing strategies using pytest, TDD methodology, fixtures, mocking, parametrization, and coverage requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
日本語の概要は準備中です。原文の説明を表示しています。
Clarify requirements before implementing. Use when serious doubts arise.
日本語の概要は準備中です。原文の説明を表示しています。
A meta-skill that understands task requirements, dynamically selects appropriate skills, tracks successful skill combinations using agent-memory-mcp, and prevents skill overuse for simple tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Lists the hardware, software, and container runtime requirements for running NemoClaw. Use when verifying prerequisites before installation. Trigger keywords - nemoclaw prerequisites, nemoclaw supported platforms, nemoclaw hardware software, nemoclaw quickstart, install nemoclaw openclaw sandbox, nemoclaw windows wsl2 setup, nemoclaw install windows docker desktop.
日本語の概要は準備中です。原文の説明を表示しています。
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
日本語の概要は準備中です。原文の説明を表示しています。
GGUF format and llama.cpp quantization for efficient CPU/GPU inference. Use when deploying models on consumer hardware, Apple Silicon, or when needing flexible quantization from 2-8 bit without GPU requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user requests to generate, create, or write professional research reports including but not limited to market analysis, consumer insights, brand analysis, financial analysis, industry research, competitive intelligence, investment due diligence, or any consulting-grade analytical report. This skill operates in two phases — (1) generating a structured analysis framework with chapter skeleton, data query requirements, and analysis logic, and (2) after data collection by other skills, producing the final consulting-grade report with structured narratives, embedded charts, and strategic insights.
日本語の概要は準備中です。原文の説明を表示しています。
The PRIMARY development workflow for the Archon project (remote-coding-agent). Use this skill instead of any PRP skills when working on Archon code. Routes to 10 specialized cookbooks based on what the user is trying to do: RESEARCH — "how does the orchestrator work?", "where is session state defined?", "trace the workflow execution flow", "what is IWorkflowStore?" INVESTIGATE — "should we use Drizzle or Prisma?", "what's the best way to add WebSockets?", "can we migrate to Turso?", "how do other projects handle rate limiting?" PRD — "write a PRD for dark mode", "spec out the notification feature", "product requirements for webhook retry" PLAN — "plan the auth refactor", "design the caching layer", "create an implementation plan for #42" IMPLEMENT — "implement the plan", "execute .claude/archon/plans/auth.plan.md", "build the feature from the plan", "code this up" REVIEW — "review PR #123", "review my changes", "code review the diff" DEBUG — "debug the failing test", "why is streaming broken?", "root cause analysis on the timeout issue" COMMIT — "commit these changes", "commit the auth refactor" PR — "create a PR", "open a pull request for this branch" ISSUE — "report this to gh", "create a gh issue", "log it in github", "file a bug for this", "create a feature request" This skill triggers on ANY development task: researching, investigating, planning, building, reviewing, debugging, committing, or shipping code. NOT for: Running Archon CLI workflows in worktrees (use /archon instead).
日本語の概要は準備中です。原文の説明を表示しています。
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
日本語の概要は準備中です。原文の説明を表示しています。
Use when you have a spec or requirements for a multi-step task, before touching code
日本語の概要は準備中です。原文の説明を表示しています。