CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A well-structured, actionable skill body that balances concise inline templates and test patterns with appropriately offloaded detailed references. Workflows are clearly sequenced with a routing table and a verification checklist.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: it assumes Claude's competence, avoids explaining outbox-pattern basics beyond a single orienting sentence, and every section delivers actionable value rather than padding.

3 / 3

Actionability

Provides complete, copy-paste-ready Python templates for both model mixins plus executable test snippets and concrete utility usage like outbox_runner() and outbox_context(flush=False).

3 / 3

Workflow Clarity

A numbered Step 1 routing table sequences the multi-step process clearly, and Step 9 provides an explicit pre-flight verification checklist as a feedback checkpoint before PR submission.

3 / 3

Progressive Disclosure

SKILL.md serves as a concise overview with four well-signaled one-level-deep references (category-and-scope.md, signal-receivers.md, backfill.md, debugging.md), all of which exist as real files in the references bundle.

3 / 3

Total

12

/

12

Passed

Description

100%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 highly specific, trigger-rich description that clearly communicates both capability and invocation criteria in third person. It avoids fluff and establishes a distinct niche unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions including model mixins, category registration, signal receivers, testing, backfill, and debugging workflows, plus named types like ReplicatedCellModel and OutboxCategory.

3 / 3

Completeness

Explicitly answers both what it does ('Guide for creating and maintaining outbox-based eventually consistent operations') and when to use it via a clear 'Use when asked to...' clause with many concrete triggers.

3 / 3

Trigger Term Quality

Provides extensive natural trigger phrases users would say such as 'add outbox', 'debug stuck outboxes', 'data not replicating', and 'outbox not processing', covering a wide range of phrasings.

3 / 3

Distinctiveness Conflict Risk

Targets a clear Sentry-specific niche with distinctive triggers like ReplicatedCellModel, OutboxCategory, and outbox_runner, making conflict with other skills very unlikely.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
getsentry/sentry
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.