Name: cell-architecture
Rating: 64 (1 reviews)
Author: getsentry

cell-architecture

Reference and active migration guide for Sentry's cell architecture. Explains what cells and localities are and why they're different, how requests reach cells via Synapse API routing, ingestion routing, and the control silo gateway, and how to safely query cross-cell data without silently missing results. The migration section covers how to do migration work: draining the URL_NAME_TO_ACTION registry in test_urls.py to zero (with a recipe for each action type), rolling deploy safety and the two-phase pattern required by independent sentry/getsentry deploys, and the region -> cell rename including what not to rename (DB columns, AWS refs, uptime regions, billing address). Also documents known issues with proposed fixes: integration TeamLinkageView routing, Jira cross-cell fan-out, and relocation endpoint routing.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/cell-architecture/SKILL.md

Quality

Content

76%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.

An action-dense, well-structured internal reference that is highly actionable and concise for its domain, held back only by missing explicit validation checkpoints in its destructive migration workflows.

Suggestions

Add explicit validation/verification checkpoints to the rolling-deploy and rename workflows (e.g., 'verify old pods are drained before Phase 2 cleanup', 'confirm getsentry has deployed the new name before removing the alias').

Consider splitting the Active Migration section into a separate reference file once it grows, keeping SKILL.md as the stable architecture overview — the Status note already anticipates this.

Dimension	Reasoning	Score
Conciseness	Dense with Sentry-specific internal knowledge Claude does not already have (cell/locality model, Synapse routing, control-silo gateway), with most tokens earning their place; a few prose passages could be tightened but it is not padded.	4 / 5
Actionability	Provides copy-paste-ready commands (`devservices up --mode cell-routing`, `bin/send-cell-test-event.py`), executable code (`org.locality.to_url(...)`), specific file paths, and concrete per-action recipes for each URL_NAME_TO_ACTION entry — covering the common cases.	5 / 5
Workflow Clarity	The rolling-deploy two-phase pattern and TeamLinkageView fix give clear sequences, but destructive operations (schema changes, renames, deploys) lack explicit validation/verification checkpoints, which caps workflow_clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Well-organized into clearly headed sections with internal anchor links and clearly signaled cross-skill references (hybrid-cloud-rpc, hybrid-cloud-outboxes); no bundle files exist so all content is inline, and the temporary migration/known-issues sections are intentionally kept together and marked for removal.	4 / 5
	Total	16 / 20 Passed

Description

75%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.

A highly specific, distinctive description that thoroughly covers what the skill does, but it omits an explicit 'Use when...' trigger clause, which limits the completeness score.

Suggestions

Add an explicit 'Use when...' clause naming the natural triggers (e.g., 'Use when doing cell-architecture migration work, querying cross-cell data, or renaming region -> cell').

Include a few natural synonyms users might say (e.g., 'multi-cell', 'silo routing') alongside the technical jargon to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'draining the URL_NAME_TO_ACTION registry in test_urls.py to zero', 'rolling deploy safety and the two-phase pattern', 'region -> cell rename including what not to rename', and 'documents known issues with proposed fixes' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is described thoroughly and concretely, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Good keyword coverage of domain terms a Sentry engineer would naturally say ('cell architecture', 'cross-cell data', 'Synapse API routing', 'region -> cell rename'), though it leans technical and omits some natural synonyms/variations.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — Sentry's cell architecture migration — with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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/cell-architecture/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.