CtrlK
BlogDocsLog inGet started
Tessl Logo

sentry

Inspect Sentry issues, summarize production errors, and pull health data via the Sentry API (read-only). Use when user says "check Sentry", "what errors in production?", "summarize Sentry issues", "recent crashes", or "production error report". Requires SENTRY_AUTH_TOKEN. Do NOT use for setting up Sentry SDK, configuring alerts, or non-Sentry error monitoring.

68

Quality

82%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides solid, actionable guidance with concrete executable commands for Sentry API read-only operations. Its main weaknesses are moderate verbosity (repeated defaults, inline token setup instructions, redundant API endpoint listing alongside the script abstraction) and missing validation/error-handling steps in the workflow. The progressive disclosure is adequate but would benefit from splitting reference material into separate files and confirming the bundled script exists.

Suggestions

Add explicit validation steps after token setup (e.g., 'Run `python3 "$SENTRY_API" list-issues --org ... --limit 1` to verify authentication works') and error-handling guidance for common failures (invalid token, network errors, empty results).

Move the raw API endpoint listing and token creation instructions into separate reference files (e.g., API_REFERENCE.md, SETUP.md) and link to them from the main skill to reduce inline verbosity.

Remove the duplicated `{your-org}`/`{your-project}` default mentions — state once at the top that these are configurable defaults, then use them without re-explaining.

DimensionReasoningScore

Conciseness

Generally efficient but includes some unnecessary content like explaining how to create a Sentry auth token (step-by-step instructions for token creation are somewhat verbose), and the placeholder defaults like `{your-org}`/`{your-project}` are repeated multiple times. The 'API requirements' section listing raw endpoints duplicates what the script already abstracts.

2 / 3

Actionability

Provides fully executable bash commands with clear flags and parameters for each core task. The commands are copy-paste ready (modulo placeholder substitution), cover the main use cases (list issues, resolve short IDs, issue detail, events), and include concrete examples with expected output descriptions.

3 / 3

Workflow Clarity

The tasks are clearly sequenced and numbered, and there's a logical flow from listing issues to resolving short IDs to getting details. However, there are no explicit validation checkpoints or error-handling feedback loops — e.g., no guidance on what to do if the API returns errors, if the token is invalid, or if the script fails. The skill also lacks a clear 'verify your setup works' step after token configuration.

2 / 3

Progressive Disclosure

The content references `scripts/sentry_api.py` as a bundled script but no bundle files are provided, making it impossible to verify the reference. The SKILL.md itself is moderately well-structured with sections, but some content (like the full API endpoint listing and the detailed token creation steps) could be split into separate reference files. There are no links to additional documentation files.

2 / 3

Total

9

/

12

Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, natural trigger terms users would actually say, explicit 'Use when' and 'Do NOT use' clauses, and clear boundaries that distinguish it from related skills. The inclusion of the prerequisite (SENTRY_AUTH_TOKEN) and negative scope boundaries makes it exceptionally well-crafted.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Inspect Sentry issues', 'summarize production errors', 'pull health data via the Sentry API (read-only)'. Also specifies what it does NOT do, adding further clarity.

3 / 3

Completeness

Clearly answers both 'what' (inspect issues, summarize errors, pull health data) and 'when' (explicit 'Use when' clause with multiple trigger phrases). Also includes negative boundaries ('Do NOT use for...'), which further strengthens completeness.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'check Sentry', 'what errors in production?', 'summarize Sentry issues', 'recent crashes', 'production error report'. These are realistic phrases a user would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche: Sentry-specific, read-only API access, and explicit exclusions (not for SDK setup, alert configuration, or non-Sentry monitoring). Very unlikely to conflict with other skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tech-leads-club/agent-skills
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.