Agent skill

Platform Tracing Configure

Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring.

Apache-2.0Auto-check passedSales & Support

Install Platform Tracing Configure

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-tracing-configure --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platform-tracing-configure .claude/skills/platform-tracing-configure && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "platform-tracing-configure" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure into .claude/skills/platform-tracing-configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-tracing-configure", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-tracing-configure --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platform-tracing-configure .agents/skills/platform-tracing-configure && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "platform-tracing-configure" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure into .agents/skills/platform-tracing-configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-tracing-configure", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-tracing-configure --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platform-tracing-configure .cursor/skills/platform-tracing-configure && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "platform-tracing-configure" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure into .cursor/skills/platform-tracing-configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-tracing-configure", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/platform-tracing-configure

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-tracing-configure --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platform-tracing-configure .gemini/skills/platform-tracing-configure && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "platform-tracing-configure" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure into .gemini/skills/platform-tracing-configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-tracing-configure", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-tracing-configure

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platform-tracing-configure .github/skills/platform-tracing-configure && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "platform-tracing-configure" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure into .github/skills/platform-tracing-configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-tracing-configure", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-tracing-configure --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platform-tracing-configure .opencode/skills/platform-tracing-configure && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "platform-tracing-configure" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-tracing-configure into .opencode/skills/platform-tracing-configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-tracing-configure", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: platform-tracing-configure
GitHub stars: 1.1k
Token cost: ~1.5k tokens
SKILL.md length: 555 words
Files: 2 (incl. assets)
Skills in repo: 251
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring.

Works in 2 steps: PlatformTracing org permission must be… → API version 68.0+ —…
Any EventSettings enablePlatformTracing metadata work
SKILL.md covers Scope, Prerequisites, Clarifying Questions and Required Inputs, plus 6 more sections
Reaches soap.sforce.com

What it does

Platform Tracing Configure is an agent skill from forcedotcom/sf-skills. Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring. Use this skill for any EventSettings enablePlatformTracing metadata work. TRIGGER when: user mentions Platform Tracing, TraceSpanEvent, enable tracing in Event Monitoring Settings, event monitoring tracing toggle, enablePlatformTracing, .settings-meta.xml for Event settings tracing, turn on trace span events, or stop publishing trace spans. DO NOT TRIGGER when: user wants Agentforce agent tracing…

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including assets.

It sits in Sales & Support. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

Any EventSettings enablePlatformTracing metadata work
: user mentions Platform Tracing
Enable tracing in Event Monitoring Settings
Event monitoring tracing toggle

Example prompts

“/platform-tracing-configure”

Workflow steps

2 steps, taken from the first numbered list in SKILL.md.

PlatformTracing org permission must be active — this permission gates the feature. It is provisioned (not settable via metadata). Without…
API version 68.0+ — enablePlatformTracing on EventSettings was introduced in Spring '25. Orgs or tooling on older API versions will not…

What it can do on your machine

Read from SKILL.md and the folder at commit e5164d9. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- soap.sforce.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Platform Tracing Configure loads about 1.5k tokens when it runs. Until then it costs about 200 tokens; SKILL.md has 555 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~200
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit e5164d9, republished under its Apache-2.0 licence (© forcedotcom). 555 words, ~1,456 tokens.

Download SKILL.mdSave it as .claude/skills/platform-tracing-configure/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: platform-tracing-configure
description: Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring. Use this skill for any EventSettings enablePlatformTracing metadata work. TRIGGER when: user mentions Platform Tracing, TraceSpanEvent, enable tracing in Event Monitoring Settings, event monitoring tracing toggle, enablePlatformTracing, .settings-meta.xml for Event settings tracing, turn on trace span events, or stop publishing trace spans. DO NOT TRIGGER when: user wants Agentforce agent tracing to Data Cloud (use platform-tracing-agentforce-configure), wants Event Log Files or ELF generation, wants Change Data Capture (use integration-eventing-cdc-configure), or wants ManagedEventSubscription (use integration-eventing-subscription-configure).
metadata.version: 1.0
metadata.domains: Platform
metadata.minApiVersion: 68.0
metadata.relatedSkills: integration-eventing-cdc-configure, integration-eventing-subscription-configure, platform-tracing-agentforce-configure

Platform Tracing — Configure

Generate EventSettings metadata to enable or disable the Platform Tracing toggle, which controls whether TraceSpanEvent is published at a sample rate. This modifies a single field (enablePlatformTracing) within the existing EventSettings metadata type.

Scope

In scope: Generating Event.settings-meta.xml with the enablePlatformTracing field to enable or disable TraceSpanEvent publishing.
Out of scope: Agentforce agent tracing to Data Cloud (use platform-tracing-agentforce-configure). Other EventSettings fields (enableDeleteMonitoringData, enableLoginForensics, etc.) owned by other teams. Event Log Files. Change Data Capture.

Prerequisites

Before generating, inform the user of these requirements:

PlatformTracing org permission must be active — this permission gates the feature. It is provisioned (not settable via metadata). Without it, the setting deploys but TraceSpanEvent is not published.
API version 68.0+ — enablePlatformTracing on EventSettings was introduced in Spring '25. Orgs or tooling on older API versions will not recognize the field. Update sfdx-project.json sourceApiVersion to 68.0 or higher if on an older tooling version.

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 Platform Tracing / TraceSpanEvent?)

No other clarification needed — this controls a single 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

Warn about prerequisites — inform the user that this feature requires the PlatformTracing org permission and API version 68.0+.
Read the template — load assets/EventSettings-template.xml.
Generate the settings file — replace {ENABLED} with true or false based on the user's desired state.
Place the file — output to settings/Event.settings-meta.xml in the project's source directory.

Show full SKILL.md (245 more words)Show less

Rules / Constraints

Constraint	Rationale
Only include `enablePlatformTracing` in generated metadata	Other fields in EventSettings are owned by other teams. Including them risks overwriting unrelated settings during deploy.
XML namespace must be `http://soap.sforce.com/2006/04/metadata`	Any other namespace causes deploy failure.
File must be named `Event.settings-meta.xml`	SFDX source format convention — the type name prefix for EventSettings is `Event`.
Requires `PlatformTracing` org permission	Without this permission, the setting deploys but has no effect on TraceSpanEvent publishing.
Requires API v68.0+	Older orgs/tooling reject the field entirely.

Gotchas

Issue	Resolution
Deploy succeeds but TraceSpanEvent not published	Org lacks the `PlatformTracing` permission. This is provisioned, not settable via metadata.
`enablePlatformTracing` field not recognized by org/tooling	Tooling is on API version < 68.0. Update `sfdx-project.json` `sourceApiVersion` to `68.0` or higher.
User confuses this with Agentforce tracing	Clarify: this publishes TraceSpanEvent for platform operations. For Agentforce agent spans to Data Cloud, use the `platform-tracing-agentforce-configure` skill.
User wants to configure all Event Monitoring settings	Only `enablePlatformTracing` is in scope. Other EventSettings fields are owned by other teams and not managed by this skill.

Output Expectations

Deliverables:

settings/Event.settings-meta.xml

Before delivering, verify:

XML namespace is exactly http://soap.sforce.com/2006/04/metadata
File is named Event.settings-meta.xml
Only enablePlatformTracing is present (no other EventSettings fields)
Project sourceApiVersion in sfdx-project.json is 68.0 or higher

Cross-Skill Integration

Need	Delegate to
Enable Agentforce agent tracing to Data Cloud	`platform-tracing-agentforce-configure` skill
Set up Change Data Capture	`integration-eventing-cdc-configure` skill
Configure ManagedEventSubscription	`integration-eventing-subscription-configure` skill

Reference File Index

File	When to read
`assets/EventSettings-template.xml`	Step 2 — template for generating the settings file

Files

SKILL.md and 1 other file (assets) in skills/platform-tracing-configure of forcedotcom/sf-skills.

SKILL.md
assets/EventSettings-template.xml

Open the folder on GitHubat commit e5164d9

Compare with similar skills

Platform Tracing Configure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Platform Tracing Configure compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Platform Tracing Configure this skillforcedotcom/sf-skills	1.1k	—	~1.5k	Automated safety check: Pass	Apache-2.0	yesterday
Services Extension Consumptionforcedotcom/salesforcedx-vscode	1k	—	~5k	Automated safety check: Pass	BSD-3-Clause	today
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib	154	—	~4.3k	Automated safety check: Pass	MIT	5 days ago
Sf DatacloudJaganpro/sf-skills	424	—	~2.7k	Automated safety check: Pass	MIT	5 mo ago
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib	154	—	~2k	Automated safety check: Pass	MIT	5 days ago
Core Extension APIforcedotcom/salesforcedx-vscode	1k	—	~842	Automated safety check: Pass	BSD-3-Clause	today

Similar skills

Services Extension Consumption
forcedotcom/salesforcedx-vscode
Consume the salesforcedx-vscode-services extension API. An agent skill from forcedotcom/salesforcedx-vscode.
1k GitHub stars~5k tokensUpdated today
Sales & SupportAuto-check passed
Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
154 GitHub stars~4.3k tokensUpdated 5 days ago
Sales & SupportAuto-check passed
Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
424 GitHub stars~2.7k tokensUpdated 5 mo ago
Sales & SupportAuto-check passed
Soql Lib Selector
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
154 GitHub stars~2k tokensUpdated 5 days ago
Sales & SupportAuto-check passed
Core Extension API
forcedotcom/salesforcedx-vscode
Public API exported by salesforcedx-vscode-core activate(). An agent skill from forcedotcom/salesforcedx-vscode.
1k GitHub stars~842 tokensUpdated today
Sales & SupportAuto-check passed
Dev Setup
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
125 GitHub stars~1.1k tokensUpdated today
Sales & SupportAuto-check passed

Questions about Platform Tracing Configure

What does Platform Tracing Configure do?

Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring. Platform Tracing Configure is an agent skill from forcedotcom/sf-skills. Generate EventSettings metadata to enable or disable Platform Tracing (TraceSpanEvent publishing) in Event Monitoring.

When should I use Platform Tracing Configure?

Platform Tracing Configure fits situations like: any EventSettings enablePlatformTracing metadata work; : user mentions Platform Tracing; enable tracing in Event Monitoring Settings; event monitoring tracing toggle.

How do I install Platform Tracing Configure in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a claude-code`. Or copy the skill folder (skills/platform-tracing-configure in forcedotcom/sf-skills) into .claude/skills/platform-tracing-configure in your project. Claude Code loads it when a task matches its description.

How do I install Platform Tracing Configure in Codex?

Run `npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a codex`. Or copy the skill folder (skills/platform-tracing-configure in forcedotcom/sf-skills) into .agents/skills/platform-tracing-configure in your project. Codex loads it when a task matches its description.

Can I use Platform Tracing Configure in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill platform-tracing-configure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-tracing-configure, .gemini/skills/platform-tracing-configure, .github/skills/platform-tracing-configure and .opencode/skills/platform-tracing-configure in your project.

What does Platform Tracing Configure need to run?

SKILL.md names no scripts, command-line tools or credentials: Platform Tracing Configure is instructions for the agent only.

Does Platform Tracing Configure access the network?

SKILL.md names 1 domain. In commands or code: soap.sforce.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Platform Tracing Configure safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Platform Tracing Configure use?

Platform Tracing Configure is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Platform Tracing Configure use?

About 1.5k tokens (SKILL.md is roughly 5.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Platform Tracing Configure?

Skills that share tags, products or a category with Platform Tracing Configure: Services Extension Consumption (forcedotcom/salesforcedx-vscode, 1k stars), Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars) and Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Platform Tracing Configure?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,060 GitHub stars. The repository holds 251 skills in this directory. The repository was last updated on October 7, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Platform Tracing Configure

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Platform Tracing — Configure

Scope

Prerequisites

Clarifying Questions

Required Inputs

Workflow

Rules / Constraints

Gotchas

Output Expectations

Cross-Skill Integration

Reference File Index

Files

Compare with similar skills

Similar skills

More from forcedotcom/sf-skills

Related

Questions about Platform Tracing Configure