Terminal
Terminal/Skill
Reconstructs one Agentforce session from Data Cloud records, showing its turns and actions, and helps find a session by time, agent or text.
By Salesforce
Works with
npx skills add forcedotcom/sf-skills --skill agentforce-d360-analyzeHierarchical session reconstruction from Data Cloud STDM + GenAI DMOs for one Agentforce session. Three stages — fetch → assemble → render. Typical wall-clock: ~10–30s for a ~15-turn session.
The pipeline is DC-only: it reads runtime audit rows that Data Cloud has materialized. It is not a runtime-availability tool — see "DC-only blind spot" below for what this skill cannot answer.
When invoked with no session id AND no discovery criteria, print this block verbatim — do not paraphrase, do not pre-run any script. Trigger condition: the input is empty OR contains no session-id shape (neither a UUID nor a 0Mw… messaging id) AND no discovery expression (no time phrase / --agent / --channel / --outcome / --grep / verbs like "find" / "list").
Which session should I pull from Data Cloud, and in which org?
I need:
- Session id — either an Agent Session UUID (
019db7f6-…) or a MessagingSession id (0Mw…, 15/18 chars).
- No session id? — Tell me what you remember and I'll find it: how recent (e.g. "last 2 hours", "today", a date), which agent, which channel (Messaging / Builder / Voice), how it ended (escalated, user ended, transferred, timed out), or a phrase from the conversation. I'll show matching sessions as a numbered list — you pick one, I pull it.
- Org alias — for
sfCLI auth (the alias you configured withsf org login).Artifacts land in
~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<session_id>/(override per-script with--data-dir <path>).
Both forms are accepted on --session:
| Form | Example | Resolution |
|---|---|---|
| Agent Session UUID | 019dface-0000-7000-8000-000000000002 | Pass-through |
MessagingSession id (0Mw prefix) | 0MwTESTMSG12345AAA | Resolved via resolve_session.py — live DC lookup on first fetch, disk-first thereafter |
Multi-match is real. One MessagingSession id can map to multiple Agent Session UUIDs. On multi-match the resolver prints every candidate and exits non-zero; the user re-invokes with a specific UUID.
Artifacts always land under ~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<session_id>/ (default; overridable per-script with --data-dir <path>) — the messaging id is a lookup key only, never a directory name. The dominant agent (first in sorted(agents_observed)) names the <agent>__<ver>/ segment.
<SKILL_DIR> = the absolute path to this skill's own directory (the folder holding this
SKILL.md); resolve it from the skill path in context and substitute it below. Runtimes
install skills in different places (~/.claude/skills/, ~/.vibe/skills/, a plugin cache, a
project .claude/skills/), so the block also probes the known install roots at runtime and
uses the first that actually contains this skill's scripts. An exported SKILL_ROOT wins.
_skill=agentforce-d360-analyze
for _c in "${SKILL_ROOT:-}" "<SKILL_DIR>" \
"${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/skills/$_skill}" \
"${VIBES_SKILLS_DIR:+$VIBES_SKILLS_DIR/$_skill}" \
"$HOME/.claude/skills/$_skill" "$PWD/.claude/skills/$_skill" \
"${PLUGIN_ROOT:-$HOME/.vibe/skills}/$_skill"; do
[ -n "$_c" ] || continue
# Some stagers (ADK eval) nest the bundled files under <skill>/artifacts/.
for _r in "$_c" "$_c/artifacts"; do
[ -f "$_r/scripts/fetch_dc.py" ] && { SKILL_ROOT="$_r"; break 2; }
done
done
[ -f "${SKILL_ROOT:-}/scripts/fetch_dc.py" ] || { echo "$_skill: scripts not found — set SKILL_ROOT to this skill's directory" >&2; exit 1; }
prefix="$SKILL_ROOT/scripts"
Every subsequent invocation in this doc uses "$prefix/...".
When the user doesn't have a session id, run discover_sessions.py against the STDM session DMO. Prints a numbered picker; user picks one; proceed with the chosen UUID.
python3 "$prefix/discover_sessions.py" [--org <alias>] [filters...]
--org is optional. "My org", "our org", or no alias at all means the sf CLI default target org — omit --org and the script uses sf config get target-org. Pass --org <alias> only when the user names an alias. If no default is set the script exits with "no --org given and no default target org set"; relay its sf config set target-org <alias> hint and ask the user for an alias.
Filters (all optional): --since <expr> (default last 24h; accepts "last 2 hours", "today", ISO dates), --agent <api-name>, --channel <Messaging|Builder|Voice>, --outcome <USER_ENDED|ESCALATED|TRANSFERRED|TIMEOUT|NOT_SET>, --grep <substring> (conversation text), --tz <IANA>, --limit <N> (default 20).
Output: markdown table with #, UUID, Start (UTC), Agent, Channel, Duration, Outcome. User replies with a number; proceed with that UUID.
fetch_dc.py → 24 dc.<name>.json + dc._session_manifest.json (DC Query REST waterfall, 5 waves)
assemble_dc.py → dc._session_tree.json (pure in-memory hierarchical join)
render_dc.py → dc._session_summary.md (human summary, multi-section)
Each stage is independently runnable. fetch_dc.py --session <sid> [--org <alias>] chains all three by default.
python3 "$prefix/fetch_dc.py" --session <session-id-or-messaging-id> [--org <alias>]
--org is optional here too: without it (the user said "my org" or named no alias) the CLI default target org is used. With no default set, fetch_dc.py reports DC_ACCESS_DENIED with reason no_org (exit 10 when headless) — ask the user for an alias and re-run with --org <alias>.
Flags: --verbose for per-DMO row counts; --no-assemble / --no-render to stop early. All entry scripts (fetch_dc.py, assemble_dc.py, render_dc.py, resolve_session.py, discover_sessions.py) accept --data-dir <path> and --cache-dir <path> to override the default ~/.vibe/{data,cache}/agentforce-d360-analyze/ roots — pass these when the host runtime needs artifacts under a different distribution layout.
Everything lands under ~/.vibe/data/agentforce-d360-analyze/<org_id15>/<agent>__<ver>/<session_id>/ (default; override with --data-dir <path>):
dc.sessions.json dc.steps.json dc.gateway_requests.json
dc.interactions.json dc.messages.json dc.gateway_responses.json
dc.participants.json dc.generations.json dc.gateway_request_llm.json
dc.content_quality.json dc.content_category.json dc.gateway_request_metadata.json
dc.tags.json dc.tag_definitions.json dc.gateway_request_tags.json
dc.tag_associations.json dc.tag_definition_associations.json
dc.feedback.json dc.feedback_details.json dc.gateway_records.json
dc.moments.json dc.moment_interactions.json
dc.telemetry_spans.json dc.app_generation.json
dc._session_manifest.json (per-DMO row counts + empties)
dc._session_tree.json (hierarchical join — session → interactions → steps → messages → generations → gateway)
dc._session_summary.md (rendered human summary)
Zero-row queries are recorded in the manifest with status: empty; no file is written. assemble_dc tolerates missing files. See references/artifacts.md for the full read order.
DC alone answers what happened — steps that ran, generations that fired, gateway requests that were logged. It does NOT answer what could have happened but didn't:
If the user's question is about why a particular topic or action was or wasn't used, DC-only is almost never sufficient. Tell the user: "Availability questions need the runtime planner trace for that turn — which is outside this skill's Data Cloud surface. Check the platform telemetry that mirrors the planner's logged decisions." Don't fabricate a root cause from runtime-only evidence.
content_quality + content_category).gateway_request_metadata + gateway_records).counts.audit_chain_1to1_ok.| Tool | Required |
|---|---|
sf CLI (authenticated against the target org) | yes — sf org login web --alias <alias>, and the CLI must provide sf org auth show-access-token (startup preflight enforces this) |
| Data Cloud enabled on the target org | yes — the STDM + GenAI DMOs must have materialized for the session |
| Python 3.10+ | yes — pipeline scripts |
| User says | Skill does |
|---|---|
"Trace session <uuid> in my-org" | fetch_dc.py --session <uuid> --org my-org → assemble → render |
"Summarize what happened in 0Mw…" | Resolve 0Mw… → UUID, then full DC pipeline |
| "Find escalated sessions today in my-org on Messaging" | Run discover_sessions.py --since today --outcome ESCALATED --channel Messaging, print picker, user picks, then DC pipeline |
| "Walk me through this session" | Same as trace — read the rendered summary top to bottom |
After the pipeline completes, the rendered dc._session_summary.md carries these top-level sections:
identity.mode, identity.bootstrap_variables)+start + duration = +end math--show-prompts; suppressed by defaultrows == 0 and a populated _unavailable_reasonFor deep-dive, open dc._session_tree.json — the single source of truth the summary was rendered from. See references/dc_pipeline_contract.md for the full pipeline contract and references/dc_dmo_fields.md for per-DMO field reference.
gateway_requests_dropped_by_stdm — when DC reports zero gateway_requests rows but runtime telemetry would show LLM calls did fire, this skill cannot definitively distinguish "STDM exporter dropped writes" from "logging genuinely disabled at the source". The session is reported as planner_ran_no_gateway_logs; the operator can check platform telemetry to disambiguate. See references/dc_pipeline_contract.md §2.8.interactions_not_materialized_yet if STDM hasn't caught up. Re-run after a minute or two.