Sentry Hello World

Name: Sentry Hello World
Author: micsapp

ASecurity

Execute capture your first error with Sentry and verify it appears in the dashboard. Use when testing Sentry integration or verifying error capture works. Trigger with phrases like "test sentry", "sentry hello world", "verify sentry", "first sentry error".

4 stars
0 votes
0 copies
3 views
Added September 10, 2026

devopsjavascriptpythonjavabashnodetesting

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 10, 2026

npx -y skills add micsapp/micstec-skills --skill sentry-hello-world --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sentry Hello World?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sentry Hello World

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/micsapp-sentry-hello-world/badge)](https://www.skillsdirectory.com/skills/micsapp-sentry-hello-world)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: sentry-hello-world
description: |
  Execute capture your first error with Sentry and verify it appears in the dashboard.
  Use when testing Sentry integration or verifying error capture works.
  Trigger with phrases like "test sentry", "sentry hello world",
  "verify sentry", "first sentry error".
allowed-tools: Read, Write, Edit, Bash(node:*), Bash(python:*), Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Sentry Hello World

## Prerequisites
- Sentry SDK installed and initialized
- Valid DSN configured
- Network access to Sentry servers

## Instructions

Sentry error capture verification is the first test you should run after installing and configuring the Sentry SDK. Sending a controlled test event confirms that your DSN is correctly configured, that network requests to Sentry's ingestion endpoint are not being blocked by a firewall or proxy, and that the SDK is capturing the metadata you expect (release version, environment tag, user context). Catching misconfiguration at this stage prevents silent monitoring gaps in production.

1. Open https://sentry.io
2. Navigate to your project
3. Check Issues tab for the test error
4. Verify event details are correct — confirm the environment is labeled correctly (not accidentally tagged as `production` when testing), check that the release version appears in the event, and verify that any user context you attached is visible in the event detail view.

See `${CLAUDE_SKILL_DIR}/references/implementation.md` for a detailed implementation guide covering SDK initialization, environment tagging, and user context attachment.

## Output
- Test error visible in Sentry dashboard within seconds of being captured
- Event contains a full stack trace pointing to the correct line in your source
- User context, release tag, and environment label attached to the event
- Confirmation that the integration is working correctly before deploying to production

## Error Handling

See `${CLAUDE_SKILL_DIR}/references/errors.md` for comprehensive error handling.

## Examples

See `${CLAUDE_SKILL_DIR}/references/examples.md` for detailed examples.

## Resources
- [Sentry Error Capture](https://docs.sentry.io/platforms/javascript/usage/)
- [Sentry Context](https://docs.sentry.io/platforms/javascript/enriching-events/context/)

## Overview

Execute capture your first error with Sentry and verify it appears in the dashboard.