Investigate a named user's sessions, errors, stuck agent runs, and replay evidence. Correlate recorded events and navigation or click sequences to explain what happened, while distinguishing observed evidence from an unconfirmed cause.
Investigate a named user's session, error, stuck agent run, or replay evidence. Use for what a user did, why something failed for them, or what they typed.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use the first-party observability actions instead of generic SQL. These
read-only investigation tools remain available in Plan mode; run the query
instead of deferring it to execution mode. Load any that are not callable yet
with one tool-search call naming all of them.
list-session-recordings
with userId over a bounded recent window to find the relevant sessions. Do
not require hasErrors=true for this initial lookup: replay, network, and
stuck-run evidence can exist while the recording's JavaScript errorCount is
zero. Use hasErrors=true only when the user asks for recordings with
captured JavaScript errors or the recording metadata confirms the filter is
appropriate.list-error-issues with userId or sessionRecordingId to find a
grouped issue, then get-error-issue for stack, breadcrumbs, occurrences, and
linked recordings.create-session-replay-agent-link first and use its scoped diagnostics
endpoint for detailed error text, stacks, request metadata, and bounded 5xx
snippets; enumerate with kind/limit and fromMs/toMs or offset when
needed.get-session-replay-summary and get-session-replay-timeline for the
page-navigation and click sequence, and get-session-replay-events only for
additional bounded replay-event details.agent_chat_stuck_detected with query-agent-native-analytics.Report the matching evidence. Do not claim a root cause without a corroborating error, event, or replay signal.
When a connected MCP exposes behavioral analytics or session replay, use it for qualitative product questions: start with an aggregate or bounded customer cohort, inspect a documented-limit sample of sessions, then read event transcripts and request screenshots or accessibility evidence when available. Treat explicitly typed user text as the prompt; keep generated suggestions, agent responses, and UI labels separate. Report session and user counts, sample bounds, masking or redaction, replay and screenshot availability, and source gaps. Never claim a visual was inspected unless the tool returned it.
list-session-recordings filters scoped replays by date, app, duration,
signals, visitor type, and email domain. Use paginated: true for sorted pages
with a real total and app counts; the default returns an array.didEvents / didNotEvents filter by tracked
events and slow by speed. Get real names and session counts from
list-session-event-names, and event health from list-event-catalog. Both
read Analytics' own index, which covers sessions only from its coverage start.
Never query BigQuery for these views.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.