setup-dev

Set up and manage the Sentry development environment using devenv. Handles fresh setup, updating existing environments, starting dev services, resetting the database, per-worktree environment setup (each worktree needs its own devenv sync/.venv), 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", "reset the database", "new worktree venv/devenv setup", or any development environment issue.

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

88%Weight 40%Scale 1-5

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

The body is a comprehensive, highly actionable walkthrough with real commands, time estimates, validation checkpoints, and a decision tree for error recovery. Its main weakness is mild verbosity and some inlined troubleshooting content that could be delegated to the existing reference file.

Suggestions

Trim conversational padding (e.g. 'It looks like a lot — that's normal', restatements of what a step does) so every line earns its context-window place.

Move the bulk of the troubleshooting decision tree and OrbStack socket-patch detail into references/orbstack-fix.md, keeping only a one-line pointer and the highest-frequency fixes inline in SKILL.md.

Consolidate the duplicated `install-devenv.sh` curl invocations into a single referenced snippet rather than repeating the full URL in Steps 3 and 5.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands, but includes some padding and restatement ('It looks like a lot — that's normal', repeated install-devenv curls, prose explaining basic intent) that could be trimmed; not quite lean enough for a 5.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — `devenv bootstrap`, `devservices up`, `.venv/bin/sentry upgrade --noinput`, `make reset-db` — with specific examples covering the common cases and exact grep/patch guidance for the OrbStack socket issue.	5 / 5
Workflow Clarity	A clear 7-step sequence with explicit validation checkpoints (verify devenv version, `docker info`, `direnv allow` after sync, confirm seeding), time estimates at each stage, and a troubleshooting decision tree that provides error-recovery feedback loops.	5 / 5
Progressive Disclosure	Well-structured with a clearly signaled one-level-deep reference (`Read references/orbstack-fix.md` for the exact pattern — verified to exist), but a sizable chunk of troubleshooting detail (the decision tree and OrbStack patch steps) is inlined in SKILL.md rather than split into the reference, leaving minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

100%Weight 40%Scale 1-5

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 strong across all dimensions: it states concrete capabilities, provides explicit and natural trigger phrases, covers both what and when, and carves out a distinct niche. It avoids verbosity while remaining comprehensive.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'fresh setup, updating existing environments, starting dev services, resetting the database, per-worktree environment setup ... and troubleshooting' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (the enumerated handling actions) and 'when' via a concrete 'Use when asked to ...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases quoted as users would say them — 'set up sentry', 'sentry won't start', 'devservices not working', 'reset the database' — including synonyms and variations.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Sentry devenv development environment) with distinct triggers; minimal risk of firing for unrelated skills.	5 / 5
	Total	20 / 20 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: b979444

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