2,100 件 ・ 関連度順
概要と使いどころ
Parallel read-only multi-agent root-cause investigation for bugs, regressions, crashes, flaky behavior, or unexplained failures. Use when the user asks to investigate a bug, find the root cause, trace a regression, understand why something broke, or wants a ranked diagnosis with the fastest proof path without making code edits.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new investigation ticket in Hot Sheet
日本語の概要は準備中です。原文の説明を表示しています。
Hunt for threats in AWS environments using Detective behavior graphs, entity investigation timelines, GuardDuty Bul:ing correlation, and automated entity profiling across IAM users, EC2 instances, and IP addresses.
日本語の概要は準備中です。原文の説明を表示しています。
Uses AWS Athena to query CloudTrail, VPC Flow Logs, S3 access logs, and ALB logs for forensic investigation. Covers CREATE TABLE DDL with partition projection, forensic SQL queries for Tespit etme unauthorized access, data exfiltration, lateral movement, and privilege escalation. Use investigating yaparken AWS security incidents or building cloud-native forensic workflows at scale.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate model specifications, requirements, and evaluation strategy. Use when researching a model before benchmarking: reading HuggingFace model cards, estimating VRAM requirements, selecting GPU providers, and determining evaluation approach. Triggers on "model research", "investigate model", "model info", "VRAM estimate", "which provider", "model card".
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous model validation and benchmarking. Investigates any ML model (LLM, image gen, TTS, time series, etc.), runs it on GPU cloud, evaluates quality and performance, and generates HTML reports. Use when user asks to verify, benchmark, evaluate, or test a model. Triggers on "verify model", "benchmark", "evaluate model", "test model", "run benchmark", "model evaluation", "モデルを検証", "ベンチマーク", "モデルを試して".
Kelly Financial Services Intel: App-in-Skill daily industry intelligence cockpit for financial services, investment advisory, and family offices (Busabase App-in-Skill). Use when the user asks about financial services, investment advisory, market explainers, client memos, family office,投顾,金融服务, or family-office scenes. Prepares news/source signals, buyer-intent interpretation, approved sales actions, and channel drafts for review before any external handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Build collaborative forensic incident timelines using Timesketch to ingest, normalize, and analyze multi-source event data for attack chain reconstruction and investigation documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence.
日本語の概要は準備中です。原文の説明を表示しています。
Explore a large codebase in parallel by launching multiple explore subagents that each investigate a different area simultaneously. Use when onboarding onto a new project, understanding architecture, or investigating a cross-cutting concern.
日本語の概要は準備中です。原文の説明を表示しています。
Investigates a session recording by gathering metadata, person profile, same-session events, and linked error tracking issues in one pass. Use when a user provides a recording or session ID and wants to understand what happened — who the user was, what they did, what errors occurred, and whether there are related error tracking issues. Replaces the manual chain of session-recording-get, persons-retrieve, execute-sql, and query-error-tracking-issues-list.
日本語の概要は準備中です。原文の説明を表示しています。
Investigates a single PostHog error tracking issue end-to-end. Use when the user provides an issue ID or pastes an issue URL (`/error_tracking/<id>`) and wants to understand the error — who it affects, what triggers it, when it started, whether it correlates with a release, browser, OS, or feature flag, and what the next step should be. Pulls aggregated metrics, sample exception events, segment breakdowns, linked replays, and synthesizes a hypothesis-grade summary in one pass.
日本語の概要は準備中です。原文の説明を表示しています。
Guides a user from "I want to watch recordings but don't know which ones" to a short, high-signal list of sessions worth watching. Use when the user asks which sessions or replays to watch, wants help finding interesting / useful recordings, says they don't know where to start in session replay, or wants to watch sessions about a goal (signup, pricing, onboarding, checkout, a feature, rageclicks, errors, mobile, a specific person) without naming exact filters. Turns a vague intent into a focused RecordingsQuery via `query-session-recordings-list`, then deep-links the best few and hands off to `investigating-replay`. Do NOT use when the user already has a recording/session ID (use investigating-replay) or wants the replay for a known error issue (use finding-replay-for-issue).
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end outbreak investigation from pathogen isolates to transmission networks. Orchestrates MLST typing, AMR surveillance, phylodynamic dating, and transmission inference with TransPhylo. Use when investigating disease outbreaks or tracking pathogen transmission chains.
日本語の概要は準備中です。原文の説明を表示しています。
Create a new investment thesis note with full analysis. Use when user says "create thesis", "new thesis", or "build a case for TICKER"
日本語の概要は準備中です。原文の説明を表示しています。
Pull an earnings call (or investor-event) transcript from Quartr (FMP fallback), extract qualitative signal (management commentary deltas, hedging shifts, Q&A tone), and produce a thesis-delta-first Research note. Use when user says "transcript", "pull earnings call", "transcript diff", or "ingest [TICKER] earnings".
日本語の概要は準備中です。原文の説明を表示しています。
Apply systematic root cause analysis and debugging methodologies to diagnose and fix bugs, test failures, and unexpected behavior. Use when encountering production issues, investigating test failures, diagnosing performance problems, tracing error sources through call stacks, analyzing logs and stack traces, reproducing inconsistent bugs, debugging race conditions, investigating memory leaks, or applying scientific method to problem-solving before proposing fixes.
日本語の概要は準備中です。原文の説明を表示しています。
Respond to production incidents systematically with triage, investigation, resolution, and post-mortem analysis to minimize downtime and prevent recurrence. Use when handling production outages, triaging incidents, investigating critical bugs, coordinating incident response, implementing hotfixes, conducting post-mortems, or establishing incident response procedures.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to debug, fix a bug, investigate an error, or do root cause analysis, and when users report errors, stack traces, unexpected behavior, or say something stopped working.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to develop the capability to investigate crashes internally. Covers what to look for, when to escalate to outside experts, and documentation standards.
日本語の概要は準備中です。原文の説明を表示しています。
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 the user asks how to investigate a CMV accident — what to do at the scene, the first 24 hours, evidence preservation, who to call, preventability determination, ELD data preservation, dash cam review, witness interviews, working with insurance + attorney, and how to build a learning culture from incidents. Reference 49 CFR 392.7 + insurance industry best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to investigate a crash effectively. Covers preservation of evidence, witness statements, dashcam review, and reporting timeline.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when FMCSA conducts an off-site investigation (less formal than CR). Covers the document-request approach and how to respond efficiently.
日本語の概要は準備中です。原文の説明を表示しています。