Name: django-startup-time
Rating: 76.8 (1 reviews)
Author: PostHog

django-startup-time

Keep heavy imports off the django.setup() path that every process (web, celery, temporal, migrate, shell, CI) pays for. Use when touching AppConfig.ready(), wiring signal receivers, editing the lazy API router (posthog/api/rest_router.py or its __init__.py shim), deferring a heavy import, when the startup-import-budget guard fails, or when merging master into a long-lived branch that made the router lazy.

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

93%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 body is a tight, actionable trigger-and-checklist that defers detail to one external doc and concentrates on defaults and pre-commit traps. It is lean and well-structured, with only the workflow-clarity dimension slightly below the top because it is a checklist rather than a linear numbered workflow with explicit per-step feedback loops.

Suggestions

Consider numbering the pre-commit traps as an explicit step sequence (e.g., measure → reproduce → fix → re-measure) so the validation feedback loops read as a linear workflow rather than a flat checklist, which would push workflow_clarity to 5.

Add one short representative "measure it" command block (e.g., the exact `importtime`/`tuna` invocation) so the measuring guidance is copy-paste ready rather than tool-name-only.

Make the single external-doc reference visually distinct (e.g., a dedicated 'Full background' bullet) so the one-level-deep pointer is unmissable at a glance.

Dimension	Reasoning	Score
Conciseness	Lean and efficient with no conceptual padding — it assumes Claude knows Django and imports, and explicitly defers detail to an external doc ("One line each — the doc has the full write-up"), so every token earns its place per the top anchor.	5 / 5
Actionability	Provides concrete, actionable guidance with specific file paths (posthog/api/rest_router.py, models/__init__.py), directives (# noqa: PLC0415, PEP 562 __getattr__), and commands (gc.disable(), dmypy stop, importtime + tuna, grimp), which per the scoring notes is fully actionable for an instruction-only skill.	5 / 5
Workflow Clarity	A well-structured "Defaults when adding backend code" section plus an explicit "Traps to check before you commit" checklist with validation checkpoints ("re-measure after wiring", "re-capture with gc.disable()") fits the clear-sequence-with-minor-gaps anchor rather than the fully-linear-workflow anchor.	4 / 5
Progressive Disclosure	A clear overview that delegates detail to a single well-signaled one-level-deep reference ("That doc is the single source of detail; this skill is the trigger and the checklist"), with well-organized section headers, matching the top anchor.	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.

The description is exemplary: it concisely names the capability, lists the processes it affects, and provides an explicit, multi-trigger "Use when" clause tied to specific code paths. It is highly specific, complete, and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions on a clearly named domain — "Keep heavy imports off the django.setup() path", "wiring signal receivers", "editing the lazy API router", "deferring a heavy import", "merging master" — matching the comprehensive-coverage anchor.	5 / 5
Completeness	Explicitly states what ("Keep heavy imports off the django.setup() path that every process pays for") and when (an explicit "Use when" clause with concrete trigger scenarios), matching the anchor that requires both with concrete trigger phrases.	5 / 5
Trigger Term Quality	The "Use when" clause enumerates natural trigger phrases a developer would say — "AppConfig.ready()", "signal receivers", "startup-import-budget guard fails", "merging master into a long-lived branch" — with comprehensive synonym-like coverage, fitting the top anchor.	5 / 5
Distinctiveness Conflict Risk	A clear niche tied to specific files and guards (posthog/api/rest_router.py, startup-import-budget guard) with distinct triggers and minimal overlap risk, matching the top anchor.	5 / 5
	Total	20 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: PostHog/posthog
Path: .agents/skills/django-startup-time/SKILL.md
Commit: 06292db

Reviewed: 23 minutes 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.