sentry

Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry CLI; perform read-only queries using the `sentry` command.

2.93x

Quality

92%

Does it follow best practices?

Impact

91%

2.93x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

85%

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

The body is highly actionable with executable CLI commands and clear task sequencing, well-organized into a single navigable file. It is mostly concise but carries minor redundancy between issue-detail sections and the repeated defaults section.

Suggestions

Merge the near-duplicate '2) Resolve an issue short ID to issue detail' and '3) Issue detail' sections into one entry, since both call 'sentry issue view {ABC-123}'.

Trim the 'Inputs and defaults' section or cross-reference it from Quick start to avoid restating the org/project detection and default time-range/environment/limit values twice.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with concrete commands and no concept explanations, but contains redundancy: issue sections #2 and #3 are near-duplicate commands, and 'Inputs and defaults' repeats Quick-start information, so it is not fully lean.	2 / 3
Actionability	Provides fully executable sentry CLI commands with concrete flags and copy-paste-ready examples (e.g., 'sentry issue list --query ... --period 24h --limit 20 --json'), matching the score-3 anchor.	3 / 3
Workflow Clarity	Tasks are numbered 1-7 in a clear sequence with prerequisites, defaults, and a fallback section; operations are read-only so the destructive/batch validation cap does not apply, satisfying the score-3 anchor for clear sequencing.	3 / 3
Progressive Disclosure	Single well-organized SKILL.md with clear sections (Quick start, Core tasks, Fallback, Inputs, Output rules) and no nested references, matching the score-3 anchor for clear organization with one-level-deep (here zero-level) navigation.	3 / 3
	Total	11 / 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.

The description is concise, specific, and clearly answers both what the skill does and when to use it with natural trigger terms. It occupies a distinct niche and is unlikely to trigger for the wrong skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('inspect Sentry issues or events', 'summarize recent production errors', 'pull basic Sentry health data', 'perform read-only queries') matching the score-3 anchor for specific concrete actions.	3 / 3
Completeness	Explicitly states what (read-only Sentry queries via the sentry CLI) and when ('Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data'), satisfying the score-3 anchor for both what and when with explicit triggers.	3 / 3
Trigger Term Quality	Uses natural phrases a user would say ('inspect Sentry issues or events', 'summarize recent production errors', 'pull basic Sentry health data') with good coverage, matching the score-3 anchor.	3 / 3
Distinctiveness Conflict Risk	Clear Sentry read-only observability niche with distinct Sentry-specific triggers, unlikely to conflict with other skills, matching the score-3 anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: openai/skills
Commit: 49f948f

Reviewed: 19 days ago

Table of Contents

Discovery Implementation Validation

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.