Platform Tracing Configure

Q: Why use Platform Tracing Configure on TypingMind?

Because you install it once and use it with any model. Platform Tracing Configure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

Q: How do I install Platform Tracing Configure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/platform-observability/skills/platform-tracing-configure. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Q: Which AI models can use Platform Tracing Configure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

Q: How many AI models can I use with Platform Tracing Configure?

As many as you like. As long as a model supports skills, you can use Platform Tracing Configure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Q: Is the Platform Tracing Configure AI skill free?

Yes. It is published on GitHub by forcedotcom under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

Q: What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

Q: How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

OrganizationPopular

forcedotcom

platform-tracing-configure

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).

Overview

Publisher	forcedotcom
Repository	`sf-skills`
Skill name	`platform-tracing-configure`
Stars	1.1K
Forks	351
Bundled files	1
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by forcedotcom on GitHub. Read the source before you install it.

Installation

Install the Platform Tracing Configure AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/platform-observability/skills/platform-tracing-configure
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/platform-observability/skills/platform-tracing-configure

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/forcedotcom/sf-skills.git /tmp/sf-skills
mkdir -p .claude/skills
cp -r /tmp/sf-skills/plugins/builder/platform-observability/skills/platform-tracing-configure .claude/skills/platform-tracing-configure

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Platform Tracing Configure in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Platform Tracing Configure on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Platform Tracing Configure is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

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

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

assets/EventSettings-template.xml1 KB

Frequently asked questions

What does the Platform Tracing Configure AI skill do?

Why use Platform Tracing Configure on TypingMind?

Because you install it once and use it with any model. Platform Tracing Configure is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Platform Tracing Configure in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/forcedotcom/sf-skills/tree/main/plugins/builder/platform-observability/skills/platform-tracing-configure. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Platform Tracing Configure?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Platform Tracing Configure?

As many as you like. As long as a model supports skills, you can use Platform Tracing Configure with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Platform Tracing Configure AI skill free?

Yes. It is published on GitHub by forcedotcom under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Mcp Oauth Remote Gateway

NousResearch

OrganizationPopular

Manual OAuth for remote MCP servers on headless gateways.

Serving Llms Vllm

vLLM: high-throughput LLM serving, OpenAI API, quantization.

Modal

Serverless GPU cloud for ML jobs and model APIs.

Huggingface Hub

HuggingFace hf CLI: search/download/upload models, datasets.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Platform Tracing — Configure

Scope

Prerequisites

Clarifying Questions

Required Inputs

Workflow

Rules / Constraints

Gotchas

Output Expectations

Cross-Skill Integration

Reference File Index

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now