span-file-export

Export spans to a local JSONL directory for AI consumption.

1.0k|453|Updated Jun 21, 2017
One-click install
npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill span-file-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: span-file-export
Source: https://github.com/forcedotcom/salesforcedx-vscode/tree/main/.claude/skills/span-file-export
Command: npx skills add https://github.com/forcedotcom/salesforcedx-vscode --skill span-file-export

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Local span export to a dedicated directory enables AI consumers to observe and debug extension behavior without manual tracing.

Core Features & Use Cases

  • Local span export directory at ~/.sf/vscode-spans with JSONL format, unified per-extension traces.
  • Choose between OTLP or File traces to route spans to human-facing dashboards or AI-friendly datasets.
  • Desktop and Web workflows: enable via settings or server, then generate and access spans for AI tooling.

Use cases include AI-assisted debugging, performance profiling, and automated verification of extension behavior.

Quick Start

Configure enableFileTraces on desktop and run the web extension to produce spans in the spans directory.

Frequently Asked Questions about span-file-export

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export spans to JSONL for AI consumption in VS Code?

To export spans to JSONL for AI consumption, configure enableFileTraces on desktop or run the web extension. This stores spans as one JSONL per line in a unified local directory at ~/.sf/vscode-spans.

Can I use OTLP traces for AI-assisted debugging of VS Code extensions?

Yes, you can select OTLP traces for AI-assisted debugging. Choosing OTLP routes spans to human-facing dashboards, while File traces generate AI-friendly JSONL datasets in a local directory.

What is the local directory path for storing extension span exports?

The local directory path for storing extension span exports is ~/.sf/vscode-spans. This directory contains unified per-extension traces formatted as JSONL files for AI tooling.

Does span export work with web extensions or only desktop VS Code?

Span export works with both desktop and web environments. You can enable file traces via settings on desktop or run the web extension server to generate and access spans for AI tooling.

When do I need local span export for observability workflows?

You need local span export for observability workflows when AI consumers must observe and debug extension behavior without manual tracing. It supports AI-assisted debugging, performance profiling, and automated verification.

What is the difference between OTLP and File traces for span export?

OTLP traces route spans to human-facing dashboards, whereas File traces route spans to a local JSONL directory. This generates AI-friendly datasets for automated debugging and observability workflows.