setup-dev

Set up and manage the Sentry development environment using devenv. Handles fresh setup, updating existing environments, starting dev services, and troubleshooting. Use when asked to "set up sentry", "setup dev environment", "get sentry running", "start dev server", "devenv setup", "devservices not working", "sentry won't start", or any development environment issue.

1.43x

Quality

100%

Does it follow best practices?

Impact

93%

1.43x

Average score across 3 eval scenarios

Securityby

High

Do not use without reviewing

Quality

Content

100%Weight 40%Scale 1-3

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

A well-structured, actionable setup guide: executable commands, branching workflow with validation checkpoints, and appropriate use of one external reference. It balances thoroughness against token efficiency for a legitimately complex process.

Dimension	Reasoning	Score
Conciseness	Command-dense and lean; assumes Claude's competence without lecturing on what Docker/devenv/Kafka are, and every prose line (timing expectations, user-relay quotes) earns its place for a genuinely complex 30-45 min process.	3 / 3
Actionability	Fully executable bash throughout with exact paths and flags (e.g. '.venv/bin/sentry upgrade --noinput', 'devenv bootstrap'), plus copy-paste-ready diagnostics — no pseudocode.	3 / 3
Workflow Clarity	Seven clearly sequenced steps with state-based branching in Step 1, explicit validation checkpoints (devenv doctor, version verify, direnv allow succeeds), and error-recovery feedback loops ('If devenv sync fails', troubleshooting decision tree).	3 / 3
Progressive Disclosure	SKILL.md is a guided overview that pushes the detailed OrbStack patch into a single well-signaled one-level-deep reference ('Read references/orbstack-fix.md for the exact pattern'), and that file exists and resolves the inline pointer.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

An exemplary description: concrete capabilities, abundant natural trigger phrases, explicit what-and-when guidance, and a clearly bounded niche. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'fresh setup, updating existing environments, starting dev services, and troubleshooting' — rather than vague language, matching the top anchor.	3 / 3
Completeness	Explicitly answers both what (set up/manage the Sentry dev environment via devenv) and when via an explicit 'Use when asked to...' clause with concrete triggers.	3 / 3
Trigger Term Quality	Provides a rich set of natural quoted phrases users would actually say ('set up sentry', 'get sentry running', 'start dev server', 'devservices not working', 'sentry won't start'), giving strong coverage.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear Sentry-devenv niche with distinct triggers tied to that specific toolchain, making conflict with other skills unlikely.	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: getsentry/sentry
Path: .agents/skills/setup-dev/SKILL.md
Commit: b4b3565

Reviewed: 2 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.