django-models

Design Django ORM models for Sentry following architectural conventions for silos, replication, relocation, and foreign keys. Use when adding a new Django model, designing a model for a feature, deciding where data should live, picking a foreign key type, or refactoring an existing model's silo placement. Trigger on "add a Django model", "create a model", "design a model for X", "new database table", "store this data in the DB", "I need to track Y", "model for [feature]". Not for Pydantic models, dataclasses, ML models, or Protobuf — this is specifically for Django ORM models in the Sentry codebase.

Quality

93%

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

86%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 dense, highly actionable conventions doc with a copy-paste skeleton and a clear decide-then-build-then-handoff workflow, appropriately deferring depth to sibling skills. Slight conciseness and inline-validation gaps keep it just short of a perfect content score.

Suggestions

Tighten the discursive rationale passages — e.g., the 'wrong way / right way' silo framing and the FlexibleForeignKey vs HybridCloudForeignKey naming paragraph — into tighter rules to lift conciseness toward the top anchor.

Add an inline validation checkpoint after the skeleton (e.g., a quick check that __relocation_scope__ is set and FK types match silo boundaries) before handing off to migration generation, to give the workflow an explicit verify step.

Dimension	Reasoning	Score
Conciseness	Almost all prose is Sentry-internal convention Claude does not already know (silo decorators, relocation scope, bounded fields, TOAST/varchar rationale), so it earns its place; a few passages (the wrong-way/right-way framing, the FlexibleForeignKey vs HybridCloudForeignKey naming comparison) are discursive and could be trimmed, fitting the 'efficient; minor over-explanation' anchor rather than 'every token earns its place'.	4 / 5
Actionability	Provides a complete copy-paste-ready model skeleton with real imports, decorator, fields, Meta constraints, and sane_repr, plus concrete field-type and FK rules with on_delete string forms and _id naming — fully executable guidance covering the common case.	5 / 5
Workflow Clarity	Sequences the work clearly — decide all four coupled decisions before writing fields, then a numbered 'After the model is designed' checklist with explicit handoffs — but checkpoints are skill-delegations rather than inline validation, and there is no validate->fix->retry feedback loop since execution is delegated to sibling skills.	4 / 5
Progressive Disclosure	No bundle files exist, so detail is correctly kept inline; the body is a well-structured overview that defers depth to one-level-deep, clearly signaled sibling skills (generate-migration, hybrid-cloud-outboxes, hybrid-cloud-rpc) with no nested file references, matching the clear-overview-with-one-level-deep-references anchor.	5 / 5
	Total	18 / 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 highly specific, well-triggered description that answers what, when, and what-not-to with concrete phrasings and a tight Sentry/Django niche. Every dimension lands at the top anchor; no suggestions needed.

Dimension	Reasoning	Score
Specificity	Enumerates the full design surface — silo placement, replication, relocation scope, and FK type selection — as concrete actions (design, add, refactor, pick, decide), matching the comprehensive-coverage anchor rather than the 'several actions with minor gaps' anchor.	5 / 5
Completeness	Explicitly answers what ('Design Django ORM models for Sentry following architectural conventions for silos, replication, relocation, and foreign keys') and when (a 'Use when...' clause plus concrete trigger phrases), with an added negative boundary, matching the anchor that requires both with concrete triggers.	5 / 5
Trigger Term Quality	A dedicated 'Trigger on' block lists natural user phrasings ('add a Django model', 'create a model', 'new database table', 'store this data in the DB', 'I need to track Y') with synonyms and a feature-name placeholder, giving comprehensive natural-term coverage.	5 / 5
Distinctiveness Conflict Risk	Narrows to 'Django ORM models in the Sentry codebase' and explicitly excludes Pydantic, dataclasses, ML, and Protobuf models, giving a clear niche with an active negative boundary that minimizes conflict with adjacent skills.	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/django-models/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.