Name: django-migrations
Rating: 78.4 (1 reviews)
Author: PostHog

django-migrations

Django migration patterns and safety workflow for PostHog. Use when creating, adjusting, or reviewing Django/Postgres migrations, including non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState. Also use for any deletion or removal of a model, table, column, product, or app — including deleting migration files or retiring a feature — even when no migration is written.

Quality

98%

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

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

The content is a lean, highly actionable runbook with a clearly sequenced workflow and explicit validation feedback loops for destructive migration operations. Its only weakness is progressive disclosure: with no bundle files, a large amount of operational detail is inlined in SKILL.md rather than split into referenced files.

Suggestions

Extract the hot-table and cross-language NOT NULL hazard sections into separate reference files (e.g. references/hot-tables.md, references/cross-language-not-null.md) and link to them from SKILL.md to reduce inlined bulk.

Add a brief 'Quick reference' summary at the top mapping each risky pattern to its helper class and CI guard so Claude can scan before reading the detail.

Move the per-command verification snippets (sqlmigrate / --dry-run checks) into a short consolidated validation checklist section for faster lookup.

Dimension	Reasoning	Score
Conciseness	The body is dense and high-signal with no padding explaining what Django or migrations are; it assumes Claude's competence and every section (CI guard names, incident-causing specifics, exact commands) earns its tokens.	5 / 5
Actionability	Provides copy-paste-ready commands (`DEBUG=1 ./manage.py makemigrations`, `sqlmigrate`, `rebase_migration`), concrete code (the `db_default=` field, `RunSQL` example), named helper classes, and named CI/allowlist files covering the common risky cases.	5 / 5
Workflow Clarity	The numbered Workflow (Classify → Generate → Apply safety rules → Validate) is explicitly sequenced with validation checkpoints (sqlmigrate, tests, linear-sequence confirmation) and feedback loops (re-verify no stray `DROP DEFAULT`, `makemigrations --dry-run` state-drift check) for destructive operations.	5 / 5
Progressive Disclosure	Clear section headers and well-signaled one-level references to repo docs at the top, but substantial inlined operational detail (hot table hazard, cross-language NOT NULL hazard) that a bundle could split into separate reference files; no bundle files exist to offload it.	4 / 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.

The description is exemplary: it states concrete capabilities, provides explicit and comprehensive 'Use when...' trigger guidance, and carves out a distinct niche with boundary clarity. It avoids vagueness and over-claiming throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'non-blocking index/constraint changes, multi-phase schema changes, data backfills, migration conflict rebasing, and product model moves that require SeparateDatabaseAndState' — with comprehensive coverage rather than generic phrasing.	5 / 5
Completeness	Explicitly answers both what ('Django migration patterns and safety workflow for PostHog') and when (concrete 'Use when...' and 'Also use for...' trigger clauses), matching the top anchor.	5 / 5
Trigger Term Quality	'Use when creating, adjusting, or reviewing Django/Postgres migrations' plus 'deleting migration files', 'retiring a feature', and 'deletion or removal of a model, table, column, product, or app' covers natural trigger phrases and synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to PostHog Django/Postgres migrations with distinct deletion/retirement triggers, giving a clear niche with minimal overlap 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: PostHog/posthog
Path: .agents/skills/django-migrations/SKILL.md
Commit: 6fca5f8

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.