agentforce-d360-analyze

Reconstructs Agentforce sessions from Salesforce DataArt Cloud artifacts via fetch-assemble-render pipeline.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill agentforce-d360-analyze
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agentforce-d360-analyze
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/agentforce-d360-analyze
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill agentforce-d360-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It reconstructs a single Agentforce session from Salesforce Data Cloud so you can see what happened, in order, without manually chasing raw audit rows.

Core Features & Use Cases

  • Traces sessions by Agent Session UUID or MessagingSession id.
  • Discovers sessions by time, agent, channel, outcome, or conversation text when you do not have an id.
  • Renders a full session summary with interactions, steps, generations, gateway requests, feedback, and tags.
  • Example use case: investigate an escalated Messaging conversation, confirm the LLM calls that ran, and review the exact transcript and timing.

Quick Start

Ask the skill to trace session 019dface-0000-7000-8000-000000000002 in your org and generate the full Data Cloud session summary.

Frequently Asked Questions about agentforce-d360-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace an Agentforce session in Salesforce Data Cloud?

Trace an Agentforce session in Salesforce Data Cloud by querying materialized DMOs with a 24-query pipeline that resolves sessions by UUID or MessagingSession id and renders a full chronological summary. The skill reconstructs interactions, steps, and gateway requests without manual audit row searches.

Can I discover Agentforce sessions without a specific session ID?

Discover Agentforce sessions without an ID by searching with time windows, agent names, channel types, outcomes, or conversation text. The skill resolves matching records across Messaging, Builder, and Voice workflows using timestamp-window fallback logic to locate the relevant session.

What do I need to reconstruct Agentforce session behavior from Data Cloud?

Reconstructing Agentforce session behavior requires the Salesforce sf CLI and materialized Data Cloud DMOs. The environment must support the 24-query fetch-assemble-render pipeline to successfully resolve, validate, and trace sessions across Messaging, Builder, and Voice workflows.

Does this session tracing approach work with Agentforce Voice and Builder workflows?

Session tracing works with Agentforce Voice and Builder workflows alongside Messaging channels. The pipeline applies resolution and validation logic across all three workflow types, reconstructing generations, LLM gateway requests, feedback, and tags into a unified chronological session summary.

What is the best way to audit LLM gateway requests during an Agentforce conversation?

Auditing LLM gateway requests during an Agentforce conversation is best handled by reconstructing the session from Data Cloud artifacts. The skill fetches and assembles gateway requests, generations, and interaction transcripts into an ordered summary for direct review of exact timing and LLM calls.

Why does Agentforce session tracing require a timestamp-window fallback?

Agentforce session tracing requires a timestamp-window fallback to resolve sessions when direct UUID or MessagingSession id matching fails. This validation mechanism discovers and reconstructs the correct chronological session behavior by querying materialized Data Cloud DMOs within relevant time ranges.