Sentry Miniapp SDK
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
Agent skill
by jeremylongshore in jeremylongshore/tons-of-skills-marketplace
Set up performance monitoring and distributed tracing with Sentry.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-performance-tracing --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/sentry-performance-tracing .claude/skills/sentry-performance-tracing && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "sentry-performance-tracing" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracing into .claude/skills/sentry-performance-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-performance-tracing", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-performance-tracing --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/sentry-performance-tracing .agents/skills/sentry-performance-tracing && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "sentry-performance-tracing" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracing into .agents/skills/sentry-performance-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-performance-tracing", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-performance-tracing --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/sentry-performance-tracing .cursor/skills/sentry-performance-tracing && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "sentry-performance-tracing" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracing into .cursor/skills/sentry-performance-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-performance-tracing", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/sentry-performance-tracing--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-performance-tracing --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/sentry-performance-tracing .gemini/skills/sentry-performance-tracing && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "sentry-performance-tracing" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracing into .gemini/skills/sentry-performance-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-performance-tracing", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-performance-tracingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/sentry-performance-tracing .github/skills/sentry-performance-tracing && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "sentry-performance-tracing" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracing into .github/skills/sentry-performance-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-performance-tracing", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace sentry-performance-tracing --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/sentry-performance-tracing .opencode/skills/sentry-performance-tracing && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "sentry-performance-tracing" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/sentry-performance-tracing into .opencode/skills/sentry-performance-tracing/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "sentry-performance-tracing", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
sentry-performance-tracingSet up performance monitoring and distributed tracing with Sentry.
Sentry Performance Tracing is an agent skill from jeremylongshore/tons-of-skills-marketplace. Set up performance monitoring and distributed tracing with Sentry. Use when implementing performance tracking, tracing requests, or monitoring application performance. Trigger with phrases like "sentry performance", "sentry tracing", "sentry APM", "monitor performance sentry".
Its SKILL.md is about 4.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/best-practices.md`, `references/errors.md` and `references/examples.md`). Compatibility notes: Designed for Claude Code
It sits in DevOps & Cloud, covering Observability and Monitoring and alerting. It works with Sentry. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
3 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadWriteEditGrepBash(node:*)From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript and python).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
docs.sentry.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Sentry Performance Tracing loads about 4.1k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 779 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 779 words, ~4,093 tokens.
.claude/skills/sentry-performance-tracing/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.Sentry performance monitoring captures distributed traces across your application stack, measuring latency, identifying bottlenecks, and tracking Web Vitals. The v8 SDK uses a span-based API where Sentry.startSpan() replaces the deprecated startTransaction(). Auto-instrumentation covers HTTP, database queries, and framework routes out of the box. Manual spans let you measure business-critical operations. Combined with profiling (profilesSampleRate), you get function-level flamegraphs attached to traces.
@sentry/node >= 8.0.0 or sentry-sdk >= 2.0.0)tracesSampleRate > 0 set in Sentry.init() — performance data is not collected at zeroSet tracesSampleRate to control what percentage of requests generate traces. Use tracesSampler for dynamic, per-endpoint sampling. Add profilesSampleRate to attach function-level flamegraphs to sampled transactions.
TypeScript (@sentry/node):
import * as Sentry from '@sentry/node';
Sentry.init({
dsn: process.env.SENTRY_DSN,
tracesSampleRate: 0.2, // 20% of transactions in production
// Profiling — profiles 10% of sampled transactions
profilesSampleRate: 0.1,
// Dynamic sampling overrides tracesSampleRate when defined
tracesSampler: (samplingContext) => {
const { name, attributes } = samplingContext;
// Drop health checks entirely — no trace data
if (name === 'GET /health') return 0;
// Always trace payment flows
if (name?.includes('/api/payment')) return 1.0;
// Higher sampling for API routes
if (name?.startsWith('GET /api/') || name?.startsWith('POST /api/')) return 0.2;
// Default: 5% for everything else
return 0.05;
},
});Python (sentry-sdk):
import os
import sentry_sdk
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
traces_sample_rate=0.2, # 20% of transactions
profiles_sample_rate=0.1, # 10% of sampled transactions get profiled
# Dynamic sampling via traces_sampler (overrides traces_sample_rate)
traces_sampler=lambda ctx: (
0.0 if ctx.get("transaction_context", {}).get("name") == "GET /health"
else 1.0 if "/api/payment" in ctx.get("transaction_context", {}).get("name", "")
else 0.2
),
)Key decisions:
tracesSampleRate: 0.2 and adjust based on volume and budgettracesSampler takes priority when defined — tracesSampleRate becomes the fallbackprofilesSampleRate is relative to sampled transactions (0.1 means 10% of the 20% that are sampled)0 from tracesSampler to explicitly drop a transaction, not falseAuto-instrumentation covers HTTP and database calls, but business-critical operations need manual spans. The v8 API provides three span creation methods for different use cases.
Sentry.startSpan() — auto-ending spans (most common):
import * as Sentry from '@sentry/node';
const result = await Sentry.startSpan(
{
name: 'order.process',
op: 'task',
attributes: {
'order.id': orderId,
'order.items': items.length,
},
},
async (span) => {
// Nested spans automatically become children of the parent
const validated = await Sentry.startSpan(
{ name: 'order.validate', op: 'validation' },
async () => validateOrder(order)
);
const charged = await Sentry.startSpan(
{ name: 'payment.charge', op: 'http.client' },
async () => chargePayment(order.total)
);
// Set span status based on outcome
if (!charged.success) {
span.setStatus({ code: 2, message: 'payment_failed' });
}
// Add custom measurements visible in Performance dashboard
Sentry.setMeasurement('order.item_count', items.length, 'none');
Sentry.setMeasurement('order.total_cents', order.total, 'none');
return { validated, charged };
}
);
// Span automatically ends when callback resolves or rejectsSentry.startSpanManual() — for spans that cross callback boundaries:
Sentry.startSpanManual(
{ name: 'queue.process', op: 'queue.task' },
(span) => {
queue.on('message', async (msg) => {
try {
await processMessage(msg);
span.setStatus({ code: 1 }); // OK
} catch (error) {
span.setStatus({ code: 2, message: 'processing_failed' });
Sentry.captureException(error);
} finally {
span.end(); // REQUIRED — must call end() manually
}
});
}
);Sentry.startInactiveSpan() — background work without changing active context:
const span = Sentry.startInactiveSpan({
name: 'cache.warmup',
op: 'cache',
});
await warmCache(); // Other spans created here won't be children of this span
span.end();Span attributes and measurements:
await Sentry.startSpan(
{ name: 'search.query', op: 'db.query' },
async (span) => {
const start = Date.now();
const results = await searchIndex(query);
// Attributes — appear in span details, filterable in Sentry UI
span.setAttribute('search.query', query);
span.setAttribute('search.results_count', results.length);
span.setAttribute('search.index', indexName);
// Measurements — appear in Performance dashboard charts
Sentry.setMeasurement('search.duration_ms', Date.now() - start, 'millisecond');
Sentry.setMeasurement('search.result_count', results.length, 'none');
return results;
}
);Python equivalent:
import sentry_sdk
with sentry_sdk.start_span(op="task", name="process_order") as span:
span.set_data("order_id", order_id)
span.set_data("item_count", len(items))
with sentry_sdk.start_span(op="validation", name="validate_input"):
validate(input_data)
with sentry_sdk.start_span(op="http.client", name="charge_payment"):
result = charge(payment)
if not result.success:
span.set_status("internal_error")SDK v8 auto-instruments most I/O without configuration. For distributed tracing across services, Sentry propagates sentry-trace and baggage headers automatically on HTTP calls. Custom propagation is needed only for non-HTTP transports (message queues, gRPC, etc.).
Auto-instrumented integrations (Node.js v8):
| Integration | What it traces | Enabled by |
|---|---|---|
httpIntegration() | All outbound HTTP/HTTPS requests | Default |
expressIntegration() | Express route handlers and middleware | Default with Express |
fastifyIntegration() | Fastify routes | Default with Fastify |
graphqlIntegration() | GraphQL resolvers | Default with graphql |
mongoIntegration() | MongoDB queries | Default with mongodb driver |
postgresIntegration() | PostgreSQL queries (pg driver) | Default with pg |
mysqlIntegration() | MySQL queries | Default with mysql2 |
redisIntegration() | Redis commands | Default with ioredis/redis |
prismaIntegration() | Prisma ORM queries | Default with @prisma/client |
Express with custom middleware spans:
import express from 'express';
import * as Sentry from '@sentry/node';
const app = express();
// Sentry auto-instruments all Express routes
// Add custom spans for specific middleware:
app.use('/api', async (req, res, next) => {
await Sentry.startSpan(
{ name: 'middleware.auth', op: 'middleware' },
async () => {
req.user = await authenticateRequest(req);
}
);
next();
});
// Parameterized route names prevent cardinality explosion
// Sentry automatically uses '/api/users/:id' not '/api/users/12345'
app.get('/api/users/:id', async (req, res) => {
const user = await Sentry.startSpan(
{ name: 'db.getUser', op: 'db.query' },
() => db.users.findById(req.params.id)
);
res.json(user);
});
// Must be after all routes
Sentry.setupExpressErrorHandler(app);Django/Flask auto-instrumentation (Python):
import sentry_sdk
from sentry_sdk.integrations.django import DjangoIntegration
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
integrations=[DjangoIntegration()],
traces_sample_rate=0.2,
profiles_sample_rate=0.1,
)
# All Django views, middleware, and template rendering are traced automatically# Flask equivalent
from sentry_sdk.integrations.flask import FlaskIntegration
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
integrations=[FlaskIntegration()],
traces_sample_rate=0.2,
)# FastAPI equivalent
from sentry_sdk.integrations.fastapi import FastApiIntegration
from sentry_sdk.integrations.starlette import StarletteIntegration
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
integrations=[FastApiIntegration(), StarletteIntegration()],
traces_sample_rate=0.2,
)Distributed tracing — custom header propagation:
When Sentry cannot automatically propagate headers (non-HTTP transports, custom fetch wrappers), extract and inject manually:
// Service A: Extract trace headers from the active span
const activeSpan = Sentry.getActiveSpan();
const traceHeaders = {
'sentry-trace': Sentry.spanToTraceHeader(activeSpan),
'baggage': Sentry.spanToBaggageHeader(activeSpan),
};
// Pass headers to downstream service via HTTP, message queue, etc.
await fetch('https://service-b.internal/api/process', {
headers: { ...traceHeaders, 'Content-Type': 'application/json' },
body: JSON.stringify(payload),
});
// Service B: Sentry SDK automatically reads sentry-trace and baggage
// from incoming request headers and continues the same traceBrowser Web Vitals (@sentry/browser):
The browser SDK automatically captures Core Web Vitals when tracing is enabled:
These appear in the Web Vitals tab of your Sentry Performance dashboard. No additional configuration beyond tracesSampleRate > 0 in the browser SDK.
sentry-trace and baggage headers| Error | Cause | Solution |
|---|---|---|
| No transactions in Performance tab | tracesSampleRate is 0 or not set | Set tracesSampleRate > 0 in Sentry.init() or define tracesSampler |
| Spans not nested correctly | Child span created outside parent callback | Call Sentry.startSpan() inside the parent startSpan callback to establish parent-child |
| High cardinality warning in Sentry UI | Dynamic values in span/transaction names | Use parameterized names (/api/users/:id) not literal values (/api/users/12345) |
| Distributed trace broken between services | sentry-trace/baggage headers not forwarded | Verify both headers are propagated in inter-service HTTP calls |
startSpanManual span never ends | Missing span.end() call | Always call span.end() in a finally block |
| Profiling data missing | profilesSampleRate not set or @sentry/profiling-node not installed | Set profilesSampleRate > 0 and install the profiling package |
tracesSampler errors silently | Sampler function throws | Wrap sampler logic in try/catch, return a fallback rate |
| Performance data but no Web Vitals | Browser SDK not initialized or tracesSampleRate is 0 on client | Ensure @sentry/browser or @sentry/react is initialized with tracing |
import * as Sentry from '@sentry/node';
import express from 'express';
Sentry.init({
dsn: process.env.SENTRY_DSN,
tracesSampleRate: 0.2,
profilesSampleRate: 0.1,
});
const app = express();
app.post('/api/orders', async (req, res) => {
const order = await Sentry.startSpan(
{ name: 'order.create', op: 'task', attributes: { 'order.source': 'api' } },
async (span) => {
const validated = await Sentry.startSpan(
{ name: 'order.validate', op: 'validation' },
() => validateOrder(req.body)
);
const saved = await Sentry.startSpan(
{ name: 'order.save', op: 'db.query' },
() => db.orders.create(validated)
);
await Sentry.startSpan(
{ name: 'notification.send', op: 'http.client' },
() => notifyWarehouse(saved.id)
);
Sentry.setMeasurement('order.total_cents', saved.total, 'none');
return saved;
}
);
res.status(201).json(order);
});
Sentry.setupExpressErrorHandler(app);
app.listen(3000);import os
import sentry_sdk
from sentry_sdk.integrations.fastapi import FastApiIntegration
from sentry_sdk.integrations.starlette import StarletteIntegration
from fastapi import FastAPI
sentry_sdk.init(
dsn=os.environ["SENTRY_DSN"],
integrations=[FastApiIntegration(), StarletteIntegration()],
traces_sample_rate=0.2,
profiles_sample_rate=0.1,
)
app = FastAPI()
@app.post("/api/orders")
async def create_order(payload: OrderRequest):
with sentry_sdk.start_span(op="task", name="order.create") as span:
span.set_data("order_source", "api")
with sentry_sdk.start_span(op="validation", name="order.validate"):
validated = validate_order(payload)
with sentry_sdk.start_span(op="db.query", name="order.save"):
saved = await db.orders.create(validated)
with sentry_sdk.start_span(op="http.client", name="notification.send"):
await notify_warehouse(saved.id)
return {"id": saved.id, "status": "created"}Sentry.setMeasurement()) to track business KPIs alongside latencytracesSampler to selectively trace slow endpoints at higher rates while keeping fast endpoints lowSentry.captureException() inside a traced span automatically link to that trace in the Sentry UI© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 4 other files (references) in skills/.curated/sentry-performance-tracing of jeremylongshore/tons-of-skills-marketplace.
Open the folder on GitHubat commit cfae287
Sentry Performance Tracing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Sentry Performance Tracing this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Sentry Miniapp SDKlizhiyao/sentry-miniapp | 687 | — | ~5.4k | Automated safety check: Pass | MIT | |
| Axiom Dashboard Builderopenclaw/clawhub | 9.5k | — | ~4.9k | Automated safety check: Pass | MIT | |
| Happy Infra Metrics and Grafanaslopus/happy | 24k | — | ~2k | Automated safety check: Notes | MIT | |
| Axiom Cost Controlopenclaw/clawhub | 9.5k | — | ~1.7k | Automated safety check: Pass | MIT | |
| WizTelemetry Platform Servicekubesphere/kubesphere | 17k | — | ~1.8k | Automated safety check: Pass | Custom licence |
lizhiyao/sentry-miniapp
Full Sentry SDK setup for Mini Programs — error monitoring, tracing, offline cache, source maps.
openclaw/clawhub
Designs and deploys Axiom dashboards through the API, choosing chart types and writing APL or metrics queries, with templates and migration notes for Splunk and Grafana.
slopus/happy
Queries live Prometheus metrics and manages Grafana dashboards as code for Happy's infrastructure, using the grafanactl CLI and the Grafana datasource proxy API.
openclaw/clawhub
Finds unused data in Axiom by analyzing query patterns, then deploys a cost dashboard and ingest monitors to keep spend under the contract limit.
kubesphere/kubesphere
Installs and configures the WizTelemetry Platform Service extension for KubeSphere, the shared API server behind its observability extensions.
openclaw/clawhub
Explores and queries OpenTelemetry metrics in Axiom MetricsDB, listing datasets, metrics and tags first and picking the right aggregation for each metric's type.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Works with
Categories
Set up performance monitoring and distributed tracing with Sentry. Sentry Performance Tracing is an agent skill from jeremylongshore/tons-of-skills-marketplace. Set up performance monitoring and distributed tracing with Sentry.
Sentry Performance Tracing fits situations like: implementing performance tracking; tracing requests; monitoring application performance; with phrases like sentry performance.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a claude-code`. Or copy the skill folder (skills/.curated/sentry-performance-tracing in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/sentry-performance-tracing in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a codex`. Or copy the skill folder (skills/.curated/sentry-performance-tracing in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/sentry-performance-tracing in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill sentry-performance-tracing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/sentry-performance-tracing, .gemini/skills/sentry-performance-tracing, .github/skills/sentry-performance-tracing and .opencode/skills/sentry-performance-tracing in your project.
SKILL.md names no scripts, command-line tools or credentials: Sentry Performance Tracing is instructions for the agent only. Our summary lists: Python 3; Node.js. Its frontmatter pre-approves these tools: Read, Write, Edit, Grep, Bash(node:*). Compatibility (from SKILL.md): Designed for Claude Code.
SKILL.md names 1 domain. As links in the text: docs.sentry.io. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Sentry Performance Tracing is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 4.1k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.2k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Sentry Performance Tracing: Sentry Miniapp SDK (lizhiyao/sentry-miniapp, 687 stars), Axiom Dashboard Builder (openclaw/clawhub, 9.5k stars), Happy Infra Metrics and Grafana (slopus/happy, 24k stars) and Axiom Cost Control (openclaw/clawhub, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.