AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Telemetry

skill-v0idos-performance-deity-telemetry · by v0idOS

Add production observability to a function. Wraps it in an OpenTelemetry or Sentry trace span, injects execution metadata, and proposes a concrete alert rule with threshold and severity.

No reviews yet
0 installs
29 views
0.0% view→install

Install

$ agentstack add skill-v0idos-performance-deity-telemetry

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-v0idos-performance-deity-telemetry)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
4mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Telemetry? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Execute all three phases in order.

Phase 1 — Trace Wrap

Wrap the critical-path function in a trace span:

OpenTelemetry:

tracer.startActiveSpan('operation.name', (span) => {
  // ... function body
  span.end();
});

Sentry:

const transaction = Sentry.startTransaction({ name: 'operation.name' });
// ... function body
transaction.finish();

Datadog:

tracer.trace('operation.name', () => {
  // ... function body
});

Phase 2 — Attribute Injection

Inside the span, attach:

  • Execution time (start and stop timer)
  • Query tags: user_id, tenant_id, endpoint
  • Input and output payload sizes in bytes

Phase 3 — Alert Rule

Propose an alert rule with all four fields specified:

| Field | Value | |---|---| | Metric | (e.g. trace.operation.duration) | | Threshold | (e.g. > 200ms) | | Evaluation window | (e.g. last 5 minutes) | | Severity | (e.g. P2 / warning) |

Examples:

  • Datadog: avg(last_5m):avg:trace.operation.duration{env:prod} > 0.200 → P2
  • Prometheus: histogram_quantile(0.99, rate(http_request_duration_seconds_bucket[5m])) > 0.2 → warning

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.