Skip to content
TrustedSkillsbeta
Back to all skills

Sentry Otel Exporter Setup

Checked
jaffrepaul·vlatest·devops

Automates OpenTelemetry exporter configuration for frontend applications using Sentry integration via jaffrepaul's skill.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add jaffrepaul/agent-skills --skill sentry-otel-exporter-setup -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

jaffrepaul

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Only contacts known or declared hosts: api.github.com, github.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    api.github.comsource hostgithub.comsource host
  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned jaffrepaul/agent-skills at 92aad81ff4.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 281 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill automates the setup of the Sentry OpenTelemetry exporter. It configures your application to send tracing data to Sentry, allowing you to monitor and debug performance issues. This includes configuring sampling rates and setting up distributed context propagation for improved observability.

When to use it

  • You want to integrate Sentry's monitoring capabilities into a frontend application.
  • Your team is already using Sentry for error tracking and wants to extend its usage to include tracing.
  • You need to quickly instrument your application with OpenTelemetry without manual configuration.
  • You are deploying an application that requires distributed tracing across multiple services.

Key capabilities

  • Automatic Sentry OpenTelemetry exporter setup
  • Sampling rate configuration
  • Distributed context propagation

Example prompts

  • "Configure the frontend to export traces to Sentry."
  • "Set up OpenTelemetry for Sentry with a 10% sampling rate."
  • "Instrument this application with Sentry tracing."

Tips & gotchas

  • Ensure you have a valid Sentry DSN (Data Source Name) available. This is required for the exporter to function correctly.