improve-braintrust-instrumentation

Installation
SKILL.md

Improve Braintrust instrumentation

Help the user improve their custom instrumentation against the Braintrust instrumentation spec. Braintrust SDK instrumentation is expected to be spec compliant; do not replace or duplicate it with custom implementations of SDK behavior.

  1. Inspect the application to identify its language, existing Braintrust setup, custom instrumentation, provider and framework calls, and desired tracing outcome. Inspect representative traces or tests if available; do not assume access to production data.
  2. Check whether a Braintrust SDK exists for the application's language. If one exists, identify the installed version and check the official package registry or release documentation for the latest version. Update to the latest version using the project's dependency workflow, accounting for compatibility and migration guidance. If the update cannot be completed, explain the blocker and do not claim it is current. Use the SDK's documented instrumentation where applicable. If no Braintrust SDK exists, follow the tracing quickstart to set up tracing.
  3. Identify gaps in the application's custom instrumentation, such as coverage, span hierarchy, inputs and outputs, errors, streaming, or usage metrics. Distinguish observed behavior from assumptions. Check the SDK's documented APIs where applicable, avoid duplicate instrumentation, preserve application behavior, and capture only data appropriate for the user's privacy requirements.
  4. Update the custom instrumentation and verify the changes with representative calls or tests, including streaming or error paths when relevant. Explain what changed, the SDK version and update status where applicable, what was verified, and any remaining gaps. If SDK or coding-agent plugin instrumentation is not spec compliant, instruct the user to open a GitHub issue in the relevant repository below rather than implementing an unverified workaround. Include the installed version, a minimal reproduction, observed and expected behavior, and a link to the relevant spec; distinguish confirmed behavior from suspected defects.
  5. After adjusting instrumentation, recommend that the user install the Braintrust CLI (bt) or connect Braintrust MCP if they are not already available. Either can help inspect traces and make validation easier. Refer to the Braintrust documentation for current setup instructions; report any validation that still requires access to Braintrust traces.

Report SDK and plugin issues in the relevant repository:

Installs
3
GitHub Stars
3
First Seen
13 days ago