一键在 Manus 中运行任何 Skill

platform-tracing-configure

星标639

分支223

更新时间2026年6月26日 15:23

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

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

forcedotcom

forcedotcom/sf-skills

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

文件资源管理器

2 个文件

SKILL.md

readonly

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","minApiVersion":"68.0","relatedSkills":"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.

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

同仓库更多 Skills

同仓库

dx-code-analyzer-configure

forcedotcom/sf-skills

Set up, configure, and troubleshoot Salesforce Code Analyzer for any project. Handles installation, prerequisite checks, diagnosing broken setups, creating and editing code-analyzer.yml overrides, engine-specific settings, ignore patterns, severity overrides, and CI/CD pipeline setup. TRIGGER when: user says 'set up code analyzer', 'configure code analyzer', 'install code analyzer', 'code analyzer not working', 'fix my setup', 'scan failing', 'check my setup', 'enable/disable engine', 'exclude files', 'change severity', 'set up GitHub Actions', 'set up CI/CD', 'add to pipeline', 'pipeline fail', 'update my workflow', 'quality gate', 'fail on violations', 'scan changed files only', 'add SARIF', 'code-analyzer.yml', 'ESLint config', 'increase SFGE memory', or reports errors running Code Analyzer. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), fix violations, explain rules, create custom rules (use dx-code-analyzer-custom-rule-create), or suppress violations.

2026-07-03678

dx-code-analyzer-custom-rule-create

forcedotcom/sf-skills

Create custom Code Analyzer rules for Regex (pattern matching), PMD (XPath/AST for Apex and metadata XML), and ESLint (LWC/JavaScript/TypeScript). Use when users want to enforce coding standards, ban patterns, detect hardcoded values, govern metadata, or add rules not in the built-in set. TRIGGER when: user says 'create a rule', 'ban System.debug', 'enforce naming convention', 'detect hardcoded IDs', 'custom rule', 'xpath rule', 'regex rule', 'add a PMD rule', 'enforce a policy', 'create a check for', 'flag this pattern', 'make a rule that catches', 'metadata rule', 'check permissions', 'enforce API version', 'eslint rule', 'lwc rule', 'override rule threshold', 'customize complexity', or describes a pattern to enforce. DO NOT TRIGGER when: user wants to run a scan (use dx-code-analyzer-run), configure engines (use dx-code-analyzer-configure), or explain existing rules (use dx-code-analyzer-run).

2026-07-03678

dx-code-analyzer-run

forcedotcom/sf-skills

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 vulnerable libraries', 'AppExchange review', 'lint my LWC', 'static analysis', 'code quality', 'show security violations', 'what is this rule', 'explain ApexCRUDViolation', 'filter results', or mentions engines/file types (.cls, .trigger, .js, .flow-meta.xml). Use this skill for scanning, exploring results, and listing rules. DO NOT TRIGGER when: user asks only about installation/configuration (use dx-code-analyzer-configure), or wants to create a custom rule (use dx-code-analyzer-custom-rule-create).

2026-07-03678

mobile-platform-native-capabilities-integrate

forcedotcom/sf-skills

Build a Salesforce LWC that uses native mobile device capabilities — barcode scanner, biometrics, location, NFC, calendar, contacts, document scanner, geofencing, AR space capture, app review, and payments. Use this skill when the user asks for an LWC that scans a barcode, captures a photo of a document, reads location or geofences, prompts for biometrics, reads/writes the device calendar or contacts, taps NFC, takes a payment, prompts for an app review, or scans an AR space. Also triggers on "lightning/mobileCapabilities", "mobile capability", "Nimbus", "device capability". Do not use for mobile offline / Komaci priming reviews (use `mobile-platform-offline-validate`) or for picking generic Lightning base components (use `design-systems-slds-apply`).

2026-07-03678

platform-custom-field-generate

forcedotcom/sf-skills

Use this skill when users need to create, generate, or validate Salesforce Custom Field metadata. Trigger when users mention custom fields, field types, Roll-up Summary fields, Master-Detail relationships, Lookup relationships, formula fields, picklists, dependent (controlling) picklists, referencing a value set from a field, or scoping/limiting picklist values for a specific record type. Also use when users encounter field deployment errors, especially around Roll-up Summary format, Master-Detail constraints, formula issues, or a record type that won't deploy without a business process. Use this skill for custom field metadata work, field generation, and field troubleshooting. DO NOT TRIGGER for creating or customizing the value set itself — defining a new GlobalValueSet, or modifying a StandardValueSet catalog like Industry or Lead Source — use platform-value-set-generate instead; this skill covers the field that references a value set, not the value set definition.

2026-07-03678

platform-value-set-generate

forcedotcom/sf-skills

Use this skill when users need to create, generate, or validate a Salesforce global value set or customize a standard value set. Trigger when users mention a global value set, GlobalValueSet, standard value set, StandardValueSet, a reusable picklist, a picklist value set shared across fields, or customizing standard picklists like Industry, Lead Source, or Opportunity Stage. Also use when users hit deployment errors adding values to a standard picklist, referencing a value set from a custom field, or working with .globalValueSet-meta.xml or .standardValueSet-meta.xml files. DO NOT TRIGGER for an inline one-off picklist on a single field with no reuse, or for general custom field metadata work that does not involve a GlobalValueSet or StandardValueSet — use platform-custom-field-generate instead.

2026-07-03678

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","minApiVersion":"68.0","relatedSkills":"platform-tracing-agentforce-configure"}

Platform Tracing — Configure

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