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.
75
92%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that thoroughly covers what the skill does, when to use it, and includes an extensive list of natural trigger terms spanning both conversational phrases and technical identifiers. It is highly specific to the Sentry outbox pattern, making it clearly distinguishable from other skills. The description is well-structured, uses third person voice, and balances comprehensiveness with clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: creating/maintaining outbox-based operations, cross-silo data replication, single-silo deferred side effects, audit logging, event fanout. Also enumerates specific workflows: model mixins, category registration, signal receivers, testing, backfill, and debugging workflows. | 3 / 3 |
Completeness | Clearly answers both 'what' (guide for creating/maintaining outbox-based eventually consistent operations, covering model mixins, category registration, signal receivers, testing, backfill, debugging) and 'when' (explicit 'Use when asked to...' clause with extensive trigger phrases). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including both user-intent phrases ('add outbox', 'debug stuck outboxes', 'data not replicating', 'test outbox') and technical identifiers ('ReplicatedCellModel', 'ReplicatedControlModel', 'OutboxCategory', 'OutboxScope', 'outbox_runner'). Covers a wide range of variations a user might naturally say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific Sentry infrastructure pattern (outbox-based eventual consistency) with domain-specific terminology like 'OutboxCategory', 'ReplicatedCellModel', 'control silo', and 'outbox_runner'. Extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality, comprehensive skill that provides excellent actionable guidance for a complex domain (outbox-based eventual consistency). Its strengths are the decision-routing table, executable code templates, thorough test examples, and well-structured progressive disclosure to reference files. The only weakness is moderate verbosity — some inline comments and docstrings explain things Claude already knows, and the overall length could be trimmed by 10-15% without losing clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured and avoids explaining basic concepts, but it's quite long (~400 lines). Some sections like the Critical Constraints could be tightened, and the full code templates include comments explaining things Claude would know (e.g., what idempotent means, what a manager does). The payload_for_update docstring and some inline comments are unnecessary padding. | 2 / 3 |
Actionability | Excellent actionability throughout. Full executable code templates for both ReplicatedCellModel and ReplicatedControlModel, complete test examples with imports, concrete debugging tables, and specific utility function usage. The code is copy-paste ready with real Sentry imports and patterns. | 3 / 3 |
Workflow Clarity | Outstanding workflow clarity with a decision table (Step 1) routing users to the right step, clearly sequenced multi-step processes (Steps 2-8), explicit validation via the pre-flight checklist (Step 9), and a debugging table with symptom-cause-investigation columns. The migration workflow (Step 5) correctly sequences non-breaking code changes before backfill. | 3 / 3 |
Progressive Disclosure | Excellent progressive disclosure with the main SKILL.md providing actionable overviews and templates, while deferring detailed content to well-signaled references (references/category-and-scope.md, references/signal-receivers.md, references/backfill.md, references/debugging.md) and the hybrid-cloud-test-gen skill. References are one level deep and clearly signaled with 'Load' directives. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- getsentry/sentry
- Commit
552fb5c
- Reviewed
Table of Contents
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.