Name: cell-architecture
Rating: 69.6 (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

83%

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

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.

An exceptionally lean and actionable reference-plus-migration guide that assumes Claude's competence, gives concrete code and commands, and sequences risky operations with explicit safety checkpoints and CI validation.

Dimension	Reasoning	Score
Conciseness	Dense, domain-specific operational detail throughout with no padding or explanation of concepts Claude already knows (no 'what is Kafka/RPC'); even the long migration list is irreducible reference material where every token earns its place.	3 / 3
Actionability	Provides copy-paste-ready commands (devservices up --mode cell-routing, bin/send-cell-test-event.py), executable code (org.locality.to_url(...)), exact regex patterns (^api/0/_admin/cells/(?P<cell_id>[^/]+)/), and named methods in the resolution table.	3 / 3
Workflow Clarity	Multi-step processes are clearly sequenced with safety checkpoints: the two-phase deploy pattern (Phase 1 backward-compatible -> Phase 2 cleanup), the deprecation flow (search callers -> add header -> remove), and test_urls.py CI enforcement acting as a validation gate.	3 / 3
Progressive Disclosure	Single-file skill with no bundle directories, organized into clear sections with anchor navigation ([Paths Into a Cell](#paths-into-a-cell)) and well-signaled prose cross-references to sibling skills (hybrid-cloud-rpc, hybrid-cloud-outboxes); content is coherently sectioned with no deep reference nesting.	3 / 3
	Total	12 / 12 Passed

Description

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

A dense, highly specific description that conveys concrete capabilities and a clear niche, but it omits an explicit 'when to use' trigger clause, which caps its completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when ...' clause enumerating natural trigger phrases (e.g. cell routing, cross-cell queries, region-to-cell migration, Synapse routing) to raise completeness and trigger-term quality.

List common user phrasings alongside the technical terms so the trigger terms read as things a user would naturally say, not only internal jargon.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — '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', 'region -> cell rename including what not to rename' — covering architecture, routing, querying, and migration.	3 / 3
Completeness	The 'what' is thorough, but there is no 'Use when...' clause or equivalent explicit trigger guidance telling Claude when to invoke this skill, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Domain keywords like 'cell architecture', 'Synapse API routing', 'cross-cell', 'control silo' are natural for a Sentry engineer, but there is no explicit trigger clause and common variations are not enumerated, so it sits below the full-coverage anchor.	2 / 3
Distinctiveness Conflict Risk	Narrowly scoped to Sentry's cell architecture with distinctive triggers (URL_NAME_TO_ACTION, Synapse, control silo gateway), making it unlikely to fire for an unrelated skill.	3 / 3
	Total	10 / 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/cell-architecture/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.