跳到主内容
智客 ZICQ

技能库 智客分类:设计创意 agentforce-d360-analyze

Agentforce D360 Analyze

数据云360°视图 单个Agentforce会话. TRIGGER在用户要求按会话编号跟踪、检查、总结或描述特定代理人会话时(代理会话UUID `019d.'或通讯会话id`0Mw.')。 还触发了会话发现——在用户还没有会话ID的情况下,按时间,代理,频道,结果,或对话文本进行查找/列表/搜索会话. 对设计-时间结构问题(代之以使用代理力-architecture-analysis)或运行时间(perf/lontency/SLO)需要数据云以外的平台遥测的问题,不要使用TRIGGER.

5117 安装量

官方网址:skills.sh

技能介绍

先看中文介绍;官方 description 原文单独保留,不改写 SKILL.md。

做什么

数据云360°视图 单个Agentforce会话. TRIGGER在用户要求按会话编号跟踪、检查、总结或描述特定代理人会话时(代理会话UUID `019d.'或通讯会话id`0Mw.')。 还触发了会话发现——在用户还没有会话ID的情况下,按时间,代理,频道,结果,或对话文本进行查找/列表/搜索会话. 对设计-时间结构问题(代之以使用代理力-architecture-analysis)或运行时间(perf/lontency/SLO)需要数据云以外的平台遥测的问题,不要使用TRIGGER.

何时用

官方 description 未单独写出 Use when。按规范,代理会在用户任务与这段 description 的关键词匹配时激活本技能。

代理如何加载

按 Agent Skills 渐进披露:启动时只加载 name 与 description(约 100 token);任务匹配后才读入整份 SKILL.md 正文;scripts/、references/、assets/ 仅在需要时再读。 本文件正文结构:agentforce-d360-analyze — Data Cloud 360° session view、If the user hasn't given enough to proceed、Session id forms — UUID or MessagingSession id、Resolving the script prefix、Session discovery (no id yet)、Pipeline — three stages。

文件分析

文件分析:除 SKILL.md 外,正文引用了 references/artifacts.md、references/dc_pipeline_contract.md、references/dc_dmo_fields.md,属于带资源的技能包,这些文件按需再读。

官方 description(原文)

Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud.

agentforce-d360-analyze — Data Cloud 360° session viewIf the user hasn't given enough to proceedSession id forms — UUID or MessagingSession idResolving the script prefixSession discovery (no id yet)Pipeline — three stagesInvocationOutput artifactsThe DC-only blind spot — read before committing to a root causeWhat DC IS good atPrerequisitesTypical prompts — what they map to

来源分类:skills.sh agent-skill

SKILL.md 与 Agent 调用

官方规范 ↗
name
agentforce-d360-analyze
description
Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud.
  1. 发现技能客户端向 Agent 提供名称与描述目录。
  2. 匹配与调用用户指定或任务匹配后,载入 SKILL.md 指令。
  3. 按需加载按步骤读取参考文档、使用脚本与素材。
指令中引用的文件 · 3
  • references/artifacts.md
  • references/dc_pipeline_contract.md
  • references/dc_dmo_fields.md

以下路径提取自原文;文件是否齐全请以来源仓库中的完整目录为准。

具体调用语法与可用工具以目标 Agent 客户端为准。 查看调用机制说明 ↗

安装这个技能

Skills CLI ↗

先选择目标 Agent 和安装范围,保留技能包的附属文件,安装后检查客户端能否发现该技能。

该技能引用了附属文件,请从来源获取完整目录;仅复制 SKILL.md 可能缺少依赖。

交给 Agent 安装

复制安装指令给支持 Agent Skills 的代理,确认其中的目标目录与客户端匹配。

把 Agent Skill「agentforce-d360-analyze」安装到我的项目:SKILL.md 原文与官方 description 见 https://zicq.com/zh/skills/skl-c1a90c2a04cdbdc0-%E7%89%B9%E5%B7%A5%E9%83%A8%E9%98%9F-D360-%E5%88%86%E6%9E%90.html
请存为 .cursor/skills/agentforce-d360-analyze/SKILL.md 或 .claude/skills/agentforce-d360-analyze/SKILL.md,frontmatter 的 name 与 description 保持原样,不要改写。
该技能还带 scripts/、references/、assets/ 等文件,请从 https://github.com/forcedotcom/sf-skills 取完整目录,不要只建一个 SKILL.md。

GitHub 完整包 ↗

终端安装 · Skills CLI

需要 Node.js 与 npx。先查看仓库技能列表,确认实际名称。

npx skills add 'https://github.com/forcedotcom/sf-skills' --list

npx skills add 'https://github.com/forcedotcom/sf-skills' --skill 'agentforce-d360-analyze'

CLI 会交互选择目标 Agent,默认安装到项目;用户级安装使用 -g。先通过查看命令核对仓库内容,再用 npx skills list 检查已安装技能。

阅读排版
--- name: agentforce-d360-analyze description: "Data Cloud 360° view of a single Agentforce session. TRIGGER when user asks to trace, inspect, summarize, or describe a specific Agentforce session by session id (Agent Session UUID `019d…` or MessagingSession id `0Mw…`). Also triggers on session discovery — find/list/search sessions by time, agent, channel, outcome, or conversation text — when the user has no session id yet. DO NOT TRIGGER for design-time architecture questions (use agentforce-architecture-analyze instead) or for runtime perf/latency/SLO questions that require platform telemetry beyond Data Cloud." metadata: version: "1.0" domains: ["Agentforce", "Data 360"] minApiVersion: "66.0" relatedSkills: - "agentforce-architecture-analyze" cliTools: - tool: ["python3"] semver: ">=3.10.0" - tool: ["sf"] semver: ">=2.0.0" --- # agentforce-d360-analyze — Data Cloud 360° session view Hierarchical 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. ## If the user hasn't given enough to proceed 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 `sf` CLI auth (the alias you configured with `sf org login`). > > Artifacts land in `~/.vibe/data/agentforce-d360-analyze//__//` (override per-script with `--data-dir `). ## Session id forms — UUID or MessagingSession id 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//__//` (default; overridable per-script with `--data-dir `) — the messaging id is a lookup key only, never a directory name. The dominant agent (first in `sorted(agents_observed)`) names the `__/` segment. ## Resolving the script prefix The default install puts the skill under the runtime's plugin root. If the skill was cloned somewhere else (e.g. directly from the `forcedotcom/sf-skills` repo into a custom path), set `PLUGIN_ROOT` to point at the runtime's skills directory. ```bash prefix="${SKILL_ROOT:-${PLUGIN_ROOT:-$HOME/.vibe/skills}/agentforce-d360-analyze}/scripts" ``` Every subsequent invocation in this doc uses `"$prefix/..."`. ## Session discovery (no id yet) 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. ```bash python3 "$prefix/discover_sessions.py" --org [filters...] ``` **Filters** (all optional except `--org`): `--since ` (default last 24h; accepts "last 2 hours", "today", ISO dates), `--agent `, `--channel `, `--outcome `, `--grep ` (conversation text), `--tz `, `--limit ` (default 20). **Output**: markdown table with `#`, `UUID`, `Start (UTC)`, `Agent`, `Channel`, `Duration`, `Outcome`. User replies with a number; proceed with that UUID. ## Pipeline — three stages ```text fetch_dc.py → 24 dc..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 --org ` chains all three by default. ### Invocation ```bash python3 "$prefix/fetch_dc.py" --session --org ``` 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 ` and `--cache-dir ` to override the default `~/.vibe/{data,cache}/agentforce-d360-analyze/` roots — pass these when the host runtime needs artifacts under a different distribution layout. ### Output artifacts Everything lands under `~/.vibe/data/agentforce-d360-analyze//__//` (default; override with `--data-dir `): ```text 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. ## The DC-only blind spot — read before committing to a root cause 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**: - Which **topics were eligible** for the classifier on a given turn (this lives in runtime planner telemetry, not DC). - Which **actions were declared** on a topic vs. which **survived rule expressions** and were actually offered to the LLM. - Why the LLM picked one topic/action over another (the full prompt + response text only lives in the planner runtime telemetry). 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. ### What DC IS good at - **What ran** — every step, every LLM call, every gateway request + response, in order, with timestamps and durations. Good for "walk me through the session". - **What the user saw** — full message transcript (user + agent), ordered. - **What the LLM produced** — generations, token counts, trust scores (toxicity, instruction adherence, content-category breakdown from `content_quality` + `content_category`). - **Tool invocations** — action calls, inputs, outputs, errors (from `gateway_request_metadata` + `gateway_records`). - **Feedback + flags** — user feedback, escalation markers, session-end type. - **Audit integrity** — the 1:1 invariant between GatewayRequest and GatewayResponse is checked; drift is flagged in `counts.audit_chain_1to1_ok`. ## Prerequisites | Tool | Required | |---|---| | `sf` CLI (authenticated against the target org) | yes — `sf org login web --alias ` | | Data Cloud enabled on the target org | yes — the STDM + GenAI DMOs must have materialized for the session | | Python 3.10+ | yes — pipeline scripts | ## Typical prompts — what they map to | User says | Skill does | |---|---| | *"Trace session `` in my-org"* | `fetch_dc.py --session --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 | ## What comes back to the user After the pipeline completes, the rendered `dc._session_summary.md` carries these top-level sections: 1. **Session identity** — UUID, start/end, duration, agent, channel, end type, participant counts 2. **Session bootstrap** — channel mode + bootstrap variables (`identity.mode`, `identity.bootstrap_variables`) 3. **ID reference** — full UUIDs for everything truncated in the hierarchical trace 4. **Transcript** — USER ↔ AGENT narrative per TURN interaction 5. **Complete hierarchical trace** — Interaction → Step → Generation → GatewayRequest, with `+start + duration = +end` math 6. **Per-turn summary** — one row per interaction 7. **Planner LLM calls (full prompts + responses)** — opt-in via `--show-prompts`; suppressed by default 8. **Visual analysis** — gantt + LLM-call overlay 9. **Session counts** — engineer-facing table of manifest counts 10. **Empties diagnostics** — one row per DMO with `rows == 0` and a populated `_unavailable_reason` 11. **Catalog (session-filtered)** — TagDefinitions / TagDefinitionAssociations / Tags filtered to agents observed in the session For 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. ## Caveats - **`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. - **Latency** — Generation and GatewayRequest carry single-write timestamps, not start/end pairs. The renderer does not compute "latencies" between them — that delta reflects DC's serialization order, not how long the LLM call took. - **Data Cloud materialization lag** — fresh sessions may show `interactions_not_materialized_yet` if STDM hasn't caught up. Re-run after a minute or two.

相关技能

设计创意

Automation Workflows

设计和实施自动化工作流程,以节省时间和规模化操作作为独家. 用于识别重复任务实现自动化,构建跨工具的工作流程,设置触发器和行动,或优化现有自动化. 包括自动化机会识别,工作流程设计,工具选择(Zapier,Make,n8n),测试,和维护. 触发"自动","自动","工作流程自动…

设计创意

Ui Ux Pro Max

UI/UX设计智能及建筑抛光接口实施指导. 当用户要求UI设计,UX流量,信息架构,视觉风格方向,设计系统/托盘,组件规格,副本/显微镜,可访问性,或生成/critique/refine前端UI(HTML/CSS/JS,React,Next.js,Vue,Svelte,Tailw…

设计创意

Frontend Design

创建美丽现代UI的专家前端设计指南. 在构建起落架页面,仪表板,或任何用户界面时使用.

设计创意

N8n Workflow Automation

设计和输出 n8n 工作流程 JSON 有强力触发器, idempotency, 错误处理, 记录, 重试, 以及 人入"一站"审查队列. 当您需要可审计的自动化时使用.