hybrid-cloud-outboxes

Guide for creating and maintaining outbox-based eventually consistent operations in Sentry. Most commonly used for cross-silo data replication, but applicable anywhere eventual consistency is needed — including single-silo deferred side effects, audit logging, and event fanout. Use when asked to "add outbox", "add outbox replication", "replicate model to control silo", "replicate model to cell", "add outbox category", "write outbox signal receiver", "debug stuck outboxes", "outbox not processing", "data not replicating", "test outbox", "migrate model to use outboxes", "backfill outbox data", "outbox coalescing", "ReplicatedCellModel", "ReplicatedControlModel", "OutboxCategory", "OutboxScope", or "outbox_runner". Covers model mixins, category registration, signal receivers, testing, backfill, and debugging workflows.

Quality

96%

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

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

A well-structured, highly actionable skill body with executable templates, a clear multi-step workflow, validation checkpoints, and appropriate progressive disclosure into real reference files. The only minor weakness is slight over-explanation in the opening paragraphs.

Suggestions

Tighten the two introductory paragraphs (lines 19-21): the transactional-outbox pattern restatement can be condensed since Claude already knows the pattern; lead with the Sentry-specific CellOutbox/ControlOutbox distinction instead.

Consider moving the full 2.2/2.3 mixin templates into a reference file (e.g. references/model-templates.md) and keeping only a minimal skeleton inline, to further reduce the SKILL.md token footprint while preserving copy-paste access.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence (no explanations of transactions, RPC, or signal dispatch), but the two introductory paragraphs restate the outbox pattern and use cases with some prose that could be tightened without losing clarity.	4 / 5
Actionability	Copy-paste-ready Python templates for both mixin types, executable test utilities (outbox_runner, outbox_context), decision tables, and concrete code blocks covering the common add/replicate/test/debug cases.	5 / 5
Workflow Clarity	A clear nine-step sequence with a routing table in Step 1, an explicit pre-flight validation checklist in Step 9, test patterns in Step 7, and a symptom/cause/investigation debug table for error recovery — validation is present so the batch-operation cap does not apply.	5 / 5
Progressive Disclosure	SKILL.md is an overview that defers detail to four real, one-level-deep reference files (category-and-scope.md, signal-receivers.md, backfill.md, debugging.md), each clearly signaled with 'Load references/X.md for ...' and covering a distinct concern.	5 / 5
	Total	19 / 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.

A strong, third-person description that clearly states what the skill does, when to use it, and lists comprehensive trigger phrases. It is concise despite its length because every phrase is a distinct, natural trigger term.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'model mixins, category registration, signal receivers, testing, backfill, and debugging workflows' plus cross-silo replication, audit logging, and event fanout — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both what ('creating and maintaining outbox-based eventually consistent operations in Sentry') and when via a concrete 'Use when asked to "add outbox"...' clause with many trigger phrases.	5 / 5
Trigger Term Quality	Extensive natural trigger phrases users would actually say ('add outbox', 'debug stuck outboxes', 'outbox not processing', 'data not replicating', 'test outbox', 'backfill outbox data') plus class-name synonyms like 'ReplicatedCellModel' and 'outbox_runner', covering variations and identifiers.	5 / 5
Distinctiveness Conflict Risk	Sentry-specific niche with distinctive triggers (ReplicatedCellModel, OutboxCategory, OutboxScope, outbox_runner, outbox coalescing) that are unlikely to fire for any other skill.	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/hybrid-cloud-outboxes/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.