'replay' 검색 결과

Replay a recorded CARLA simulation in full or over a selected time range. Change playback speed, follow a particular vehicle, restore recorded weather, or regenerate sensor data to examine the run again.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Watching a recorded simulation again
• Following a vehicle in slow motion
• Reviewing a selected time range at double speed

Investigate API requests that fail to replay because of client-generated signatures or anti-bot tokens. Start with captured traffic, identify the blocking inputs or signing function, and validate a reproducible request for further security testing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigate signature errors in replayed API requests
• Trace signing functions and their inputs
• Validate a reproduced signer against browser output

Analyze a custom protocol in a CTF sandbox and reproduce an accepted exchange. Recover message boundaries, checksums, and session state, then build a small replay program that preserves the required message order.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recover message boundaries in an unknown protocol
• Reconstruct handshake steps and session state
• Build a replay program for a captured exchange

From a Tutti checkout, run, audit, freshly replay, publish, or diagnose Session Replay cassettes that are driven by case-repository scenario scripts (CDP), not by interactive UI recording. Use for real-Provider capture while a scenario.mjs executes, cassette transport or semantic-state mismatches, fresh replay qualification, AgentGUI replay evidence, and product-side support for a new Agent Target beyond local:codex / local:claude-code. Do not use to author Case metadata or scenario scripts (case repository write-replay-case), or for executionKind "ui" Cases.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Analyze Sentry session replays to surface UX patterns, pain points, and user journeys for a given product area. Use when asked to "show me how users use", "day in the life", "UX research", "replay research", "how do customers use", "what's the user experience like for", "watch replays of", "analyze replays for", "user behavior on", or "replay UX audit" for any Sentry product surface.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

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).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Test interface behavior in a real browser and save actions, checks, and screenshots in a replayable RVF session file. Use recorded sessions to repeat tests, investigate CI failures, and compare screenshots against an earlier baseline.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking user flows in a real browser
• Recording a baseline before interface changes
• Comparing screenshots with a previous test run

Add privacy-aware session recording and replay to React applications using the Temps SDK. Captures user interactions for playback while respecting privacy through input masking, element blocking, and GDPR-compliant consent flows. Use when the user wants to: (1) Add session recording to their app, (2) Implement session replay functionality, (3) Record user sessions for debugging, (4) Add privacy-compliant screen recording, (5) Debug user issues with visual replay, (6) Implement rrweb-based recording, (7) Set up GDPR-compliant session capture. Triggers: "session recording", "session replay", "record sessions", "user replay", "screen recording", "rrweb", "session capture".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validate RuField CSI or ultrasonic recording replay and its fusion boundary. Use for captured CSI JSONL, BatVu ultrasonic replay, replay adapter integration, or replay regression diagnosis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Debugs why session recordings aren't appearing in the local dev environment. Use when a developer reports that local replay ingestion isn't working, recordings aren't showing up despite /s calls, or the replay pipeline seems broken after hogli start. Covers the full local pipeline: SDK capture, Caddy proxy, capture-replay (Rust), Kafka, ingestion-sessionreplay (Node), recording-api (Node), SeaweedFS, and common failure modes like orphaned processes, stuck phrocs workers, and trigger misconfiguration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Replays a CARLA .log recorded by the recorder — the whole run or a time window, at any speed, following a chosen actor, optionally regenerating sensors and restoring weather. Use when the user asks to "replay the recording", "play back the run", "watch it again in slow motion / at 2x", "follow vehicle N during replay", or "replay onto a different map".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Replay recorded browser actions on the original or an alternative URL to check UI changes or reproduce bugs. When a page element cannot be found, the skill searches for a similar target and records how many steps succeeded.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking UI flows after a deployment
• Reproducing a bug from a recorded session
• Preparing repeated runs for screenshot comparison

Compare two recorded browser sessions at matching step IDs using screenshots and accessibility snapshots, which describe page elements. Report the first difference and overall similarity to check interface changes or verify replayed sessions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Checking visual regressions after interface changes
• Verifying a replay against its original session
• Comparing A/B variants of a form workflow

Operate NVIDIA Nsight Graphics from the command line to capture application frames and GPU activity. Summarize performance traces, analyze existing capture files through ngfx-replay, and check installed versions and compatibility before starting an investigation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check installed Nsight Graphics versions and compatibility
• Capture frames from a graphics application
• Summarize GPU activity and investigate performance bottlenecks

Assess Bluetooth Low Energy devices by capturing wireless traffic, inspecting available data services, and checking pairing security. Identify signs of interception, reused commands, and data access that lacks authentication.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess BLE security on IoT devices
• Check whether devices accept replayed commands
• Investigate suspicious pairing and device impersonation

Inspect CARLA driving simulation logs without replaying them. Get recording details, find collisions by participant category, and identify vehicles that barely moved, with times and object IDs to locate moments worth reviewing.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a recording's map, duration, frames, and participants
• Find collisions between vehicles and pedestrians
• Identify vehicles that remained stuck

Record a running CARLA simulation to a .log file for later replay or inspection. Capture object creation, movement, and traffic-light states, optionally include controls and velocities, and verify that the recording contains simulation frames.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Recording thirty seconds of simulated traffic
• Saving a scenario while it runs
• Capturing vehicle velocities and controls

Assess LoRaWAN and sub-GHz wireless devices by capturing signals, examining packet formats, and checking key reuse and replay weaknesses, where recorded messages are resent. It covers IoT networks, fixed-code remotes, and proprietary radio protocols.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing LoRaWAN keys and frame counters
• Testing fixed-code remotes for replay weaknesses
• Analyzing proprietary wireless packet formats

Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures. Use this skill when you need to reproduce a bug, capture execution traces for debugging, instrument code to record program behavior, generate replay scripts for bug reproduction, diagnose hard-to-reproduce failures, or perform deterministic replay of program execution. Triggers when users ask to instrument code for tracing, capture execution traces, reproduce bugs, generate replay scripts, or enable deterministic debugging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Instruments programs to record execution information for deterministic replay debugging. Use when debugging hard-to-reproduce bugs (race conditions, timing issues, intermittent failures, heisenbugs), reproducing production failures, or analyzing complex execution sequences. Records non-deterministic events (I/O, threading, randomness, time) to enable exact replay of program executions. Supports Python, JavaScript, Java, and C/C++ with both custom instrumentation and existing replay tools.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for custom binary or text protocol recovery, handshake reconstruction, framing, sequence control, checksums, stateful replay, and accepted-session reproduction. Use when the user asks to decode an unknown protocol, recover custom framing, build a replay harness, satisfy sequence or checksum rules, replay a captured session, or prove the smallest message order that reaches an accepted branch. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Time-travel debugging for DAG executions. Inspect agent state at any node, replay decisions with modified inputs, compare execution traces side-by-side, and identify where reasoning diverged. Inspired by LangGraph Studio's state-editing model and Temporal's event history. Activate on "debug DAG", "replay execution", "time travel debug", "inspect node state", "what went wrong at step", "compare runs", "execution diff". NOT for live monitoring (use dag-runtime + websocket-streaming), failure analysis (use dag-ops), or general code debugging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Detects and responds to OAuth token theft and replay attacks in cloud environments, focusing on Microsoft Entra ID (Azure AD) token protection, conditional access policies, and sign-in anomaly detection. Covers access token theft, refresh token replay, Primary Refresh Token (PRT) abuse, and pass-the-cookie attacks. Activates for requests involving OAuth token theft detection, token replay prevention, Azure AD conditional access token protection, or cloud identity attack investigation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

tespit etme (s) and responds to OAuth token theft and replay attacks in cloud environments, focusing on Microsoft Entra ID (Azure AD) token protection, conditional access policies, and sign-in anomaly Tespit. Covers access token theft, refresh token replay, Primary Refresh Token (PRT) abuse, and pass-the-cookie attacks. Activates for requests involving OAuth token theft Tespit, token replay prevention, Azure AD conditional access token protection, or cloud identity attack investigation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.