← Search

OTel Expo Style (OpenTelemetry for Expo)
Developer tools 🧪 Install ran in our test sandbox · Nov 11, 2026 📌 Pinned version: commit 87299d1
Install test only, on the date shown. This does not guarantee the code is safe.
⚙ Needs: an Expo / React Native project; a Superlog account…

OTel Expo Style (OpenTelemetry for Expo)

OpenTelemetry bootstrap for Expo/React Native — runtime guards, init ordering, public ingest token, mobile exporters

At a glance
What
OpenTelemetry bootstrap for Expo/React Native — runtime guards, init ordering, public ingest token, mobile exporters
Cost
Free
Needs
an Expo / React Native project; a Superlog account; your public ingest token (write-only by design — safe to ship in the app, spans only with no read access; pass it via the secure vault or env vars, never hardcode it in chat)
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

OTel Expo Style (OpenTelemetry for Expo) is a free Muse skill that teaches OpenTelemetry bootstrap for Expo and React Native apps, with runtime guards, correct init ordering, a public ingest token, and mobile exporters. It initializes OTel only in supported branches, orders init before Sentry, and adds automatic fetch and XHR instrumentation plus product-action spans.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 87299d1

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: an Expo / React Native project; a Superlog account; your public ingest token (write-only by design — safe to ship in the app, spans only with no read access; pass it via the secure vault or env vars, never hardcode it in chat) Install "OTel Expo Style (OpenTelemetry for Expo)" for me. Give my agent the OpenTelemetry integration style for Expo/React Native — bootstrap guards, init ordering, public ingest token usage, mobile-compatible exporters, fetch/XHR instrumentation and product-action spans Repository: https://raw.githubusercontent.com/superloglabs/skills/87299d19c4398edcb1b76d0beba36786760e3e3b/otel-expo-style/SKILL.md Pinned version: install the code at commit 87299d19c4398edcb1b76d0beba36786760e3e3b exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the superloglabs-skills-otel-expo-style skill from the repository into a temporary folder 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "superloglabs-skills-otel-expo-style". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. create a Superlog account, save my public ingest token in the secure vault). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
Based on the install prompt we scanned, this skill does not run commands, make third-party network calls, install packages, write files, or ask for API keys.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 87299d1 · 2026-10-13
🧪 Install ran in our test sandbox · Nov 11, 2026
👁 Observed during the install test · Nov 11, 2026 : no network contact
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
87299d1 · 2026-10-13
Sandbox install test
Install ran in our test sandbox · Nov 11, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : No commands, network calls, packages, file writes or API keys detected.

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.