forcedotcom/sf-skills

platform-tracing-agentforce-configure

Generate AgentforcePlatformTracingSettings metadata to enable or disable Agentforce agent execution trace spans flowing to Data Cloud.

Ver código fuente

Cómo usar

  1. Copia el comando y revisa el paquete antes de instalarlo en tu entorno de agente.
  2. Consulta las herramientas, credenciales y entornos necesarios en el documento original.
  3. Describe las entradas y el resultado deseado; contrasta la salida con las fuentes.
npx skills add https://github.com/forcedotcom/sf-skills --skill platform-tracing-agentforce-configure

Antes de empezar

  • La instalación no incluye suscripción al modelo, cuota API ni permisos sobre tus archivos.
  • Las estrellas e instalaciones reflejan actividad, no una prueba independiente de calidad o seguridad.
Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

Platform Tracing — Agentforce Configure

Generate AgentforcePlatformTracingSettings metadata to enable or disable forwarding of Agentforce agent execution trace spans to Data Cloud's ingestion pipeline. This is a singleton Settings type with one boolean field introduced in API v68.0 (Spring '25).

Scope

  • In scope: Generating AgentforcePlatformTracing.settings-meta.xml to enable or disable Agentforce agent tracing.
  • Out of scope: Platform Tracing for TraceSpanEvent (use platform-tracing-configure). Event Log Files. Change Data Capture. Org permission provisioning. Data Cloud provisioning.

Prerequisites

Before generating, inform the user of these requirements. The skill cannot check org state, but deploying without these prerequisites means the setting has no effect:

  1. Data Cloud must be provisioned in the org — trace spans are forwarded to Data Cloud's ingestion pipeline. Without Data Cloud, there is no destination for the spans.
  2. `PlatformObservability` org permission must be active — this permission gates the feature. It is provisioned (not settable via metadata).
  3. API version 68.0+ — the AgentforcePlatformTracingSettings type was introduced in Spring '25. Orgs on older API versions will not recognize it.

If the user reports the setting isn't working after deploy, the most likely cause is a missing prerequisite above.


Clarifying Questions

Before generating, confirm with the user if not already clear:

  • Enable or disable? (Which state do you want for Agentforce agent tracing?)

No other clarification needed — this is a singleton type with one boolean field.


Required Inputs

Gather or infer before proceeding:

  • Desired state: true (enable) or false (disable)

Defaults unless specified:

  • If user says "enable" or "turn on": set to true
  • If user says "disable" or "turn off": set to false

If the user provides a clear request, generate immediately without unnecessary back-and-forth.


Workflow

  1. Warn about prerequisites — inform the user that this feature requires Data Cloud and the PlatformObservability org permission.
  1. Read the template — load assets/AgentforcePlatformTracing-template.xml.
  1. Generate the settings file — replace {ENABLED} with true or false based on the user's desired state.
  1. Place the file — output to settings/AgentforcePlatformTracing.settings-meta.xml in the project's source directory.

Rules / Constraints

ConstraintRationale
Singleton — only one file per org, one boolean fieldThe metadata type has exactly one instance. Deploying the file sets the org-wide preference.
XML namespace must be http://soap.sforce.com/2006/04/metadataAny other namespace causes deploy failure.
File must be named AgentforcePlatformTracing.settings-meta.xmlSFDX source format convention for this Settings type.
Only include enableAgentforcePlatformTracing fieldNo other fields exist on this type.
Requires API v68.0+Older orgs reject the metadata type entirely.

Gotchas

IssueResolution
Deploy succeeds but tracing doesn't activateOrg lacks PlatformObservability permission or Data Cloud is not provisioned. These are provisioned, not settable via metadata.
AgentforcePlatformTracingSettings type not recognizedOrg or tooling is on API version < 68.0. Update sfdx-project.json sourceApiVersion.
User confuses this with Platform Tracing (TraceSpanEvent)Clarify: this sends Agentforce agent execution spans to Data Cloud. For TraceSpanEvent publishing, use the platform-tracing-configure skill.

Output Expectations

Deliverables:

  • settings/AgentforcePlatformTracing.settings-meta.xml

Before delivering, verify:

  • [ ] XML namespace is exactly http://soap.sforce.com/2006/04/metadata
  • [ ] File is named AgentforcePlatformTracing.settings-meta.xml
  • [ ] Only enableAgentforcePlatformTracing is present (no extra fields)

Cross-Skill Integration

NeedDelegate to
Enable TraceSpanEvent publishing (Platform Tracing)platform-tracing-configure skill
Query or analyze existing Agentforce agent trace data in Data Cloudagentforce-observe skill
Set up Change Data Captureintegration-eventing-cdc-configure skill
Configure ManagedEventSubscriptionintegration-eventing-subscription-configure skill

Reference File Index

FileWhen to read
assets/AgentforcePlatformTracing-template.xmlStep 2 — template for generating the settings file

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
forcedotcom
Comunidad

platform-custom-application-generate

Use this skill when users need to create or configure tab-based Salesforce Custom Applications with navigation, branding, and action overrides. Trigger when users mention custom apps, application metadata, app navigation, or organizing tabs into applications. Use when users want to create app containers for tabs and pages. Do NOT use when the goal is hosting a React UI bundle in the App Launcher — use experience-ui-bundle-custom-app-generate for that case.

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct
forcedotcom
Comunidad

platform-custom-field-generate

Use when users create, generate, or validate Salesforce Custom Field metadata. Trigger on custom fields, field types, Roll-Up Summary, Master-Detail/Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping picklist values per record type; also field deployment errors, including a record type that won't deploy without a business process. DO NOT TRIGGER for creating/customizing the value set itself — a new GlobalValueSet o

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct
forcedotcom
Comunidad

platform-custom-metadata-type-generate

Use to create, generate, or validate Salesforce Custom Metadata Type metadata — the mdt object, fields, and deployable records. Trigger on custom metadata types, CMDT, mdt objects, .md-meta.xml files, or cross-org reference/config data; also admin-maintained mapping/lookup/crosswalk tables (config that changes without a deploy belongs in a CMDT, never hardcoded in Apex/Flow), and CMDT deploy errors. DO NOT TRIGGER for Custom Settings (use platform-custom-setting-generate), business-record object

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct
forcedotcom
Comunidad

platform-custom-report-type-generate

Use to create, generate, or validate Salesforce Custom Report Type metadata. Trigger on custom report types, CRTs, cross-object reports, report builder data sources, exposing fields for reporting across related objects, inner vs outer joins in reports, report type categories, or deployment errors for .reportType-meta.xml files. Do NOT trigger for running, editing, or filtering existing reports; creating report folders, dashboards, or list views; or non-authoring reporting questions.

instalaciones
1
GitHub Stars
1,1 mil
Actualizado
23 oct