CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

92%

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

85%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 highly token-efficient, action-dense checklist skill that delegates full detail to one external doc and uses a pre-commit traps list as validation checkpoints. Minor gaps: no inline copy-paste code and the primary reference is an out-of-bundle doc whose existence is unverified.

Suggestions

Add one tiny inline code snippet (e.g. the function-local import with `# noqa: PLC0415`) so the most common action is copy-paste ready.

Turn the traps list into a short numbered pre-commit workflow (measure -> wire -> re-measure -> check traps) to make sequencing and feedback loops explicit.

Either bundle docs/internal/django-startup-time.md or confirm it is reachable, since the body depends on it as the single source of detail.

DimensionReasoningScore

Conciseness

Lean and dense — every bullet carries specific guidance (file paths, pragma tags, thresholds like ≥100ms); assumes Claude's competence and never explains what Django or imports are.

5 / 5

Actionability

Concrete, executable directives (import function-locally with `# noqa: PLC0415`, shim via PEP 562 `__getattr__`, re-capture with `gc.disable()`) but it is mostly instruction/guidance with no copy-paste runnable code snippet, leaving minor gaps relative to fully copy-paste-ready examples.

4 / 5

Workflow Clarity

Sequencing is implicit via 'Defaults when adding' and a pre-commit 'Traps to check' checklist rather than numbered steps, but the traps list functions as explicit validation checkpoints; not a perfect 5 because there is no linear stepwise workflow with feedback loops.

4 / 5

Progressive Disclosure

Good one-level-deep structure: the body is a trigger/checklist pointing to a single source-of-detail doc (docs/internal/django-startup-time.md) and named guard files, with clear sections. Not a 5 only because detail is delegated to an external doc whose presence cannot be verified from the bundle.

4 / 5

Total

17

/

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 tightly written, third-person description that fully specifies what the skill does and when to use it, with concrete, natural trigger phrases and specific file references. It is concise despite its length and carries low conflict risk.

DimensionReasoningScore

Specificity

Names the domain (keeping heavy imports off django.setup()) and multiple concrete actions — deferring imports, wiring signal receivers, editing the lazy API router, reacting to a failing startup-import-budget guard — covering the work comprehensively.

5 / 5

Completeness

Explicitly answers 'what' ('Keep heavy imports off the django.setup() path') and 'when' via a full 'Use when...' clause enumerating concrete trigger situations including a failing guard.

5 / 5

Trigger Term Quality

Uses natural trigger phrases developers actually say ('wiring signal receivers', 'deferring a heavy import', 'the startup-import-budget guard fails', 'merging master into a long-lived branch') with concrete file paths as synonyms.

5 / 5

Distinctiveness Conflict Risk

A narrow, clearly-niched trigger set tied to Django startup-import budget and specific PostHog paths; minimal overlap risk with generic Django or import skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository
PostHog/posthog
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.