error-tracking
Add Sentry Error Tracking
Application teams need consistent error visibility across services. This skill gives Claude, Codex, and Claude Code practical Sentry v8 patterns for capture, context, and performance monitoring.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "error-tracking" from https://skillstore.io/skills/diet103-error-tracking.md and its manifest at https://skillstore.io/api/skills/diet103-error-tracking/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "error-tracking". A route catches errors with only console logging.
Expected outcome:
The assistant adds Sentry exception capture, route tags, safe user context, and keeps the existing error response.
Using "error-tracking". A cron job exits after failures without telemetry.
Expected outcome:
The assistant adds early Sentry initialization, a cron span, captured fatal errors, and completion logging.
Using "error-tracking". A database query sometimes takes several seconds.
Expected outcome:
The assistant wraps the query in performance tracking and names the operation for Sentry analysis.
Security Audit
Medium RiskMost static findings are false positives caused by Markdown code fences, TypeScript relative imports, localhost test commands, and normal Sentry configuration examples. One semantic privacy risk remains because the skill strongly encourages broad Sentry telemetry with user and workflow identifiers.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (45)
🌐 Network access (7)
📁 Filesystem access (5)
🔑 Env variables (10)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/diet103-error-tracking/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/diet103-error-tracking?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/diet103-error-tracking?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/diet103-error-tracking/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/diet103-error-tracking.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
diet103. (2026). error-tracking security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/diet103-error-tracking/audits/8BibTeX citation
@techreport{diet103-diet103-error-tracking-2026,
author = {diet103},
title = {error-tracking security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/diet103-error-tracking/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "error-tracking security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "diet103"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/diet103-error-tracking/audits/8"
identifiers:
- type: other
value: "skillstore:diet103-error-tracking:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Instrument New API Controllers
Add consistent Sentry capture and response handling when creating new Express controllers or routes.
Monitor Background Jobs
Add Sentry initialization, spans, and fatal error capture to cron jobs and workers.
Review Observability Coverage
Check services for missing Sentry setup, weak error context, and untracked slow database operations.
Try These Prompts
Use this skill to add Sentry error capture to this controller method. Keep existing behavior and avoid sensitive data in context.
Use this skill to instrument this cron job with Sentry initialization, a cron span, captured exceptions, and safe shutdown behavior.
Use this skill to wrap these database calls with performance tracking and clear operation names. Include safe context only.
Use this skill to review this service for Sentry gaps across controllers, workflows, cron jobs, and database operations. Return prioritized changes.
Best Practices
- Redact request bodies, tokens, emails, and secrets before sending error context to Sentry.
- Use stable operation names and tags so teams can group related errors and spans.
- Test error paths in local or approved test environments before production rollout.
Avoid
- Do not send raw request payloads or credentials as Sentry context.
- Do not rely on console errors when the service needs monitored failure reporting.
- Do not add performance spans without clear names, owners, and sampling expectations.