forcedotcom/sf-skills

platform-tracing-agentforce-configure

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

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/forcedotcom/sf-skills --skill platform-tracing-agentforce-configure

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

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

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
forcedotcom
Communauté

design-systems-slds-apply

Apply SLDS-compliant UI using the correct blueprints, styling hooks, utility classes, and icons. Use when building any UI that needs SLDS, choosing between Lightning Base Components and SLDS Blueprints, applying styling hooks for theming, using utility classes for layout and spacing, or selecting icons. Triggers include \"build a modal\", \"create a form\", \"data table\", \"SLDS styling\", \"style with hooks\", \"add an icon\".

Installations / 1h
1
GitHub Stars
1,2 k
Mis à jour
13 nov.
forcedotcom
Communauté

dx-code-analyzer-run

Run Salesforce Code Analyzer to scan code for security, performance, best practice, and code style violations. Supports all engines (PMD, ESLint, CPD, RetireJS, Flow, SFGE, ApexGuru), targets (files, folders, git diff), categories, and severities. Also handles post-scan exploration: filtering results by engine/severity/category/file, and explaining what rules mean. TRIGGER when: user says 'scan my code', 'check security issues', 'run PMD/ESLint', 'find duplicates', 'analyze Flows', 'check vulner

Installations / 1h
1
GitHub Stars
1,2 k
Mis à jour
13 nov.
forcedotcom
Communauté

experience-lwc-accessibility-jest-run

Use ALWAYS when running Sa11y accessibility Jest tests for an LWC — locally before pushing, producing the command(s), running one file vs a suite, selecting tests by naming convention, saving Sa11y-rendered HTML, or reproducing a Sa11y/A11yBug failure. Covers core (Bazel; bazel test // : ) and standalone npx jest (.accessibility.test.js, @sa11y/jest). REQUIRED for a run-plan.md, a failing a11y test's exit code, or SA11Y/A11yBug/core-Bazel test paths. DO NOT TRIGGER for functional Jest tests, a11

Installations / 1h
1
GitHub Stars
1,2 k
Mis à jour
13 nov.
forcedotcom
Communauté

experience-lwc-generate

Lightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc//.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use platform-apex-generate), Aura components, or Visualforce.

Installations / 1h
1
GitHub Stars
1,2 k
Mis à jour
13 nov.