Data Cloud 360° view of a single Agentforce session — DC-only, zero
Splunk dependency. Pulls 24 STDM + GenAI DMOs via the Data Cloud Query
REST API, assembles a hierarchical session tree (Interaction → Step →
Generation → GatewayRequest), and renders a human-readable markdown
summary with transcript + per-turn topic/action invocations + LLM
generations + tool calls + audit chain.
Migrated as a standalone Apache-2.0 skill from an internal hub plugin —
self-contained, no sibling-skill or plugin dependencies.
What this skill answers:
- "Trace session <uuid>" / "Summarize what happened in <0Mw…>"
- "Find escalated sessions today on Messaging in <org>"
- Session discovery by time / agent / channel / outcome / conversation
text when the user has no session id
What it does NOT answer (use a different surface):
- Design-time architecture — use investigating-agentforce-architecture
- Runtime planner availability — DC alone can't tell you which
topic/action was eligible for the classifier on a given turn
Skill layout:
- 8 Python pipeline modules (fetch_dc, assemble_dc, render_dc,
discover_sessions, resolve_session, dc, storage, config)
- 4 _shared helpers (paths, fs_guard, sql, __init__) with skill-scoped
DATA_ROOT (~/.claude/data/investigating-agentforce-d360/)
- 26 SQL templates under assets/dc/
- 27 test files (367 tests + 18 subtests, 100% passing)
- 3 reference docs (artifacts.md, dc_dmo_fields.md,
dc_pipeline_contract.md)
- SKILL.md (sf-skills frontmatter, license: Apache-2.0,
metadata.version: "1.0")
- README.md (external-facing quick-start)
- tools/grant_allowlist.py (idempotent first-run permission grant)
- tools/archive_data_dir.sh (opt-in stop-hook tarballer)
Quality gates:
- pytest scripts/tests/: 367 passed + 18 subtests, 0 failures
- npm run validate:skills: 62 of 62 skill(s) checked, 0 errors
- Live end-to-end runs against 3 real Salesforce sessions exercising
both the full-tree and STDM-lag gateway-direct render branches
- 4 independent code-review rounds (correctness, security, markdown,
architecture-critic) — all findings addressed
Customer-data hygiene: no live tenant ids, no internal sprint markers,
no hub/sibling-skill references. Synthetic fixtures look obviously
synthetic (`019dface-…` UUIDs, `0MwTESTMSG…` MessagingSession ids,
`00DTESTORG…` org ids, `MyAgent` placeholder agent name).
Sibling skill: investigating-agentforce-architecture (PR #278) — same
migration pattern, design-time metadata; complementary scope.
chore: rename afv-library to sf-skills across all references
Update all in-repo references from afv-library to sf-skills in
README, CONTRIBUTING, scripts, and skill files to reflect the
upcoming GitHub repo rename from forcedotcom/afv-library to
forcedotcom/sf-skills.
fix: make sync-react-samples workflow manual-only
Remove the nightly cron schedule so the workflow only runs when
manually triggered via workflow_dispatch.
fix: use static branch name for sync-react-samples PR
Prevents the workflow from creating a new PR per version update by
using a fixed branch name so peter-evans/create-pull-request reuses
the same PR.
feat: replace agentforce-development skill with three specialized skills
Replace the monolithic agentforce-development skill with three focused skills:
- developing-agentforce: For creating and authoring Agentforce agents
- observing-agentforce: For monitoring and debugging agents
- testing-agentforce: For validating agent behavior
Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>
chore: sync React B2E (1.120.6) & B2X (1.120.6) samples with lockfiles and gitignore
Add package-lock.json generation for uiBundle directories and .gitignore
writing to the sync scripts so they persist across syncs.
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
* fix: trigger ui-bundle skill for React application prompts
Add React-specific trigger language to building-ui-bundle-app description
so prompts like "I want to build a react application" activate the
ui-bundle orchestrator even without existing project files.
* fix: correct stale related-skill reference
Rename generating-experience-react-site to generating-ui-bundle-site
in building-ui-bundle-app related-skills to match the actual skill name.
* fix: tighten skill descriptions to reduce false triggers
- generating-ui-bundle-metadata: remove generic triggers (metadata, new app,
meta XML, configuration), update command to sf template generate ui-bundle,
add --template reactbasic flag
- building-ui-bundle-app: reframe as orchestrator for multi-skill ui-bundle
work, distinguish from generating-lightning-app
* fix: improve ui-bundle skill descriptions to reduce false triggers and improve activation
- Add MUST activate + file-pattern triggers to all 9 ui-bundle skills
- Remove overly specific examples that waste context tokens
- Scope features skill to authentication and search only
- Add boundary language between orchestrator and frontend skills
- Update metadata skill to use sf template generate ui-bundle --template reactbasic
* fix: standardize uiBundles/*/src/ directory trigger across all ui-bundle skills
* fix: remove React references from skill descriptions for framework agnosticism
* fix: standardize uiBundles/*/src/ trigger in agentforce and data skills
* fix: add 'Use this skill when' trigger context to all ui-bundle skill descriptions
* fix: require mobile-responsive UI in building-ui-bundle-frontend skill
* fix(using-ui-bundle-salesforce-data): condense reference into skill
also adds, operation types, script section type and mix instructions as comments in the examples. it also adds a section to avoid the llm being eager to show progress on ui-scaffold
* fix: workaround llm being eager to scaffold ui
* fix: delete testing with sf cli
* fix: add summary table for workflow steps
---------
Co-authored-by: Hemant Singh Bisht <hsinghbisht@salesforce.com>
@W-21861732 fix: convert native mobile rental tenant app README from RTF to Markdown
The README was accidentally saved in RTF format, causing rendering
issues. Stripped RTF formatting and restored plain Markdown.
Co-authored-by: gbockus-sf <76090802+gbockus-sf@users.noreply.github.com>
