agentforce-d360-analyze

Reconstructs Agentforce session traces from Salesforce Data Cloud DMOs into hierarchical summaries.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/padjei/SF_Build --skill agentforce-d360-analyze-padjei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentforce-d360-analyze
Source: https://github.com/padjei/SF_Build/tree/main/.claude/skills/agentforce-d360-analyze
Command: npx skills add https://github.com/padjei/SF_Build --skill agentforce-d360-analyze-padjei

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Debugging an Agentforce agent session requires manually querying dozens of Data Cloud DMOs and stitching together interactions, steps, LLM generations, and gateway requests by hand. This Skill automates that entire reconstruction, turning a raw session id into a readable end-to-end trace. ## Core Features & Use Cases - 24-DMO fetch waterfall: Pulls STDM and GenAI audit DMOs from the Data Cloud Query REST API in 5 dependency-ordered waves using the sf CLI for authentication. - Hierarchical session tree: Joins Session → Interaction → Step → Generation → GatewayRequest into a single JSON source of truth, with declared-binding and timestamp-window fallback logic for orphan gateway calls. - Rendered markdown summary: Produces an up-to-11-section human-readable report covering transcript, per-turn trace, token counts, trust scores, feedback, and empty-DMO diagnostics. - Session discovery: Finds sessions by time range, agent, channel, outcome, or conversation text when no session id is known, and resolves MessagingSession ids (0Mw…) to Agent Session UUIDs. - Use Case: A user says "trace session 019dface-... in my-org" — the Skill runs fetch → assemble → render and returns a full walkthrough of what the agent did on every turn. ## Quick Start Ask the assistant to trace a specific Agentforce session by providing its session UUID or MessagingSession id along with your sf CLI org alias.

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 Data Cloud?▼

Provide the Agent Session UUID (019d…) or a MessagingSession id (0Mw…) plus your sf CLI org alias. The skill runs a three-stage pipeline — fetch_dc.py, assemble_dc.py, render_dc.py — that queries 24 DMOs and produces a hierarchical JSON tree and markdown summary.

How do I find an Agentforce session without a session id?▼

Run discover_sessions.py with filters like --since, --agent, --channel, --outcome, or --grep for conversation text. It prints a numbered picker of matching sessions; you pick one and the pipeline proceeds with that UUID.

Can this skill explain why an agent chose a specific topic or action?▼

No. Data Cloud shows what happened — steps, generations, gateway calls — but not which topics were eligible or which actions survived rule expressions. Those availability questions require runtime planner telemetry outside this skill's Data Cloud surface.

What are the prerequisites for querying Agentforce session data?▼

You need the sf CLI authenticated against the target org, Data Cloud enabled so STDM and GenAI DMOs have materialized for the session, and Python 3.10 or later to run the pipeline scripts.

Why does a fresh session show no interactions in Data Cloud?▼

STDM Interaction, Step, and Message DMOs can take hours to days to materialize, while Gateway DMOs appear within minutes. The manifest classifies this as interactions_not_materialized_yet; re-run after the data catches up.