554 件 ・ 関連度順
概要と使いどころ
Use when a carrier asks about the full pre-employment investigation process for new CDL drivers under 49 CFR 391.23, 391.25, 391.27, 382.413, and 391.21 — the complete file build required before a driver operates a CMV. Covers application, MVR, employment history, drug/alcohol history, PSP, Clearinghouse, road test, and documentation requirements.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when FMCSA conducts an off-site investigation (less formal than CR). Covers the document-request approach and how to respond efficiently.
日本語の概要は準備中です。原文の説明を表示しています。
[21] UNDERSTAND. Deep research workflow for this project using 150% scope (100% core + 50% boundary), evidence-based reasoning, and structured investigation notes. Use when the task requires investigation, root-cause analysis, or mapping unknown areas. Always maintain a research log file that captures findings, hypotheses, and next branches; use web.run when external verification is needed.
日本語の概要は準備中です。原文の説明を表示しています。
status:needs-investigation な issue を並列調査し、結果をコメントして status:investigated に更新する
Leverages Splunk Enterprise Security and SPL (Search Processing Language) to investigate security incidents through log correlation, timeline reconstruction, and anomaly detection. Covers Windows event logs, firewall logs, proxy logs, and authentication data analysis. Activates for requests involving Splunk investigation, SPL queries, SIEM log analysis, security event correlation, or log-based incident investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Parses and analyzes the Windows Amcache.hve registry hive to extract evidence of program execution, application installation, and driver loading for digital forensics investigations. Uses Eric Zimmerman's AmcacheParser and Timeline Explorer for artifact extraction, SHA-1 hash correlation with threat intel, and timeline reconstruction. Activates for requests involving Amcache forensics, program execution evidence, Windows artifact analysis, or application compatibility cache investigation.
日本語の概要は準備中です。原文の説明を表示しています。
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data for attack chain reconstruction and investigation documentation.
日本語の概要は準備中です。原文の説明を表示しています。
アイデアの整理、実装、不具合調査など、状況に合う関連スキルと使う順序を案内します。作業の規模や段階に応じて、次に進む手順を選ぶための相談役です。
製造現場の規格不適合について、対象品の隔離から原因分析、処置の検討、是正・予防措置の効果確認までを整理し、管理図の読み取りや仕入先品質の改善も支援します。
Claudeの初回編集やファイル作成をいったん止め、呼び出し元・データ構造・依頼内容の確認を促すフックを設定し、変更前の調査を組み込むスキル。
調査テーマを複数の問いに分け、ウェブ情報の検索と本文の読み込みを通じて、出典・確信度・情報不足を明記したレポートにまとめるスキル。
GitHubの公開ソフトウェアに不正な変更がないか、履歴やアーカイブを照合して調査します。削除された情報の回収を試み、侵害の手がかりと根拠付きの報告書をまとめます。
Follow the money via public records and sanctions data.
日本語の概要は準備中です。原文の説明を表示しています。
Design or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic debugging with root cause investigation. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing evidence-ranked hypotheses.
日本語の概要は準備中です。原文の説明を表示しています。
Conduct multi-round deep research on any GitHub Repo. Use when users request comprehensive analysis, timeline reconstruction, competitive analysis, or in-depth investigation of GitHub. Produces structured markdown reports with executive summaries, chronological timelines, metrics analysis, and Mermaid diagrams. Triggers on Github repository URL or open source projects.
日本語の概要は準備中です。原文の説明を表示しています。
Runs maximum-saturation research with a cooperating team, claim-graph gating, and a cited, QA'd deliverable. Use when the user explicitly asks for research or a deep investigation, including any 'ulw' research wording.
日本語の概要は準備中です。原文の説明を表示しています。
Handles git work: atomic commits, rebase, squash, blame, bisect, reflog, and history questions. Use whenever a task needs a commit or a git-history investigation; skip for ordinary code edits.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when an active or proposed trip needs planning, logistics, feasibility, entry or transit checks, itinerary work, or investigation of an airport process, immigration, ground transport, a transfer, or fast-track service, even for a narrow question with no booking intent. Route a bounded flight, hotel, restaurant, event, or other item ready for live availability or booking directly to Booking. Skip this skill for a stable travel fact alone or flight status.
日本語の概要は準備中です。原文の説明を表示しています。
Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.
日本語の概要は準備中です。原文の説明を表示しています。
Capability-based multi-tool matrix for video production. Agents pick providers (CLI-Anything harnesses, public CLIs, Python libs, native binaries, cloud APIs) per capability rather than marching through fixed stages, including storyboard planning, story/audio direction, source triage, internet video/music search/download, capture/generation, analysis, sound design, high-end caption design, NLE/render doctor investigation, review, and packaging.
日本語の概要は準備中です。原文の説明を表示しています。
Plans, executes, and documents validation, verification, and transfer of analytical procedures under the governing framework - ICH Q2(R2) and Q14, USP <1220>/<1225>/<1226>, ICH M10 bioanalytical, CLSI EP, or ISO/IEC 17025. Use for HPLC, LC-MS/MS, GC, CE, ICP-MS, dissolution, qNMR, qPCR, NIR, and ligand binding or cell-based assays whenever the question is whether a procedure is fit for its intended purpose. Triggers include "method validation", "analytical method validation", "AMV", "validation protocol", "acceptance criteria", "linearity", "reportable range", "accuracy and precision", "repeatability", "intermediate precision", "recovery", "LOD", "LOQ", "detection limit", "quantitation limit", "specificity", "robustness", "method transfer", "method comparison", "Deming", "Passing-Bablok", "Bland-Altman", "equivalence testing", "OOS investigation", "ICH Q2", "Q2(R2)", "Q14", "USP 1225", "ICH M10", "incurred sample reanalysis", "ISR", "CLSI EP", and any request to show that an assay works.
日本語の概要は準備中です。原文の説明を表示しています。
Use for authorized digital forensics including memory dumps, disk timelines, PCAP investigation, artifact triage, and IR evidence preservation.
日本語の概要は準備中です。原文の説明を表示しています。