CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

django-perf-review

Django performance code review. Use when asked to "review Django performance", "find N+1 queries", "optimize Django", "check queryset performance", "database performance", "Django ORM issues", or audit Django code for performance problems.

Quality

88%

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

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

Highly actionable content: concrete problem/solution code for every rule, explicit validation gates and checklists, a defined output format, and useful false-positive guidance. The only improvements are minor — slight redundancy between the per-category checklists and the general validation section, and the option to split detailed priority sections into reference files.

DimensionReasoningScore

Conciseness

The body is dense and assumes Django competence — no padding explaining what the ORM or N+1 means — with only minor trims available (the per-category validation checklists partly repeat the 'Validation Requirements' section). Not level 5 because of that redundancy; well above the 'several unnecessary explanations' level 2.

4 / 5

Actionability

Every rule comes with executable PROBLEM/SOLUTION code pairs (select_related, annotate with Count, iterator(chunk_size=1000), bulk_create, queryset.update, Meta.indexes) plus a copy-paste-ready output template with a worked finding example. Coverage of the common Django performance cases is complete.

5 / 5

Workflow Clarity

The review process is explicitly sequenced (Research first, Validate before reporting, Zero findings acceptable) with per-category validation checklists, a five-step validation gate, and a pre-submit sanity check — explicit checkpoints and feedback loops ('If you cannot validate all steps, do not report').

5 / 5

Progressive Disclosure

No bundle files exist or are referenced, and the single file is well-organized (priority overview table, clear per-priority sections, false-positive guidance). At roughly 400 lines, the per-priority rule details could arguably be split into reference files, a minor organization gap that keeps it below the top anchor.

4 / 5

Total

18

/

20

Passed

Description

86%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 strong description with an explicit 'Use when' clause and comprehensive, natural trigger phrases covering synonyms. The only gaps are a thin 'what' (a single action rather than several concrete capabilities) and one somewhat generic trigger ('database performance') that slightly raises overlap risk.

DimensionReasoningScore

Specificity

The 'what' is a single concrete action — 'Django performance code review' — which names the domain plus one action but does not list several specific actions (e.g., finding N+1 queries, auditing querysets, checking indexes), matching the 'domain and 1-2 concrete actions' anchor. It is clearly above the generic-action level 2 anchor.

3 / 5

Completeness

It explicitly answers 'what' ('Django performance code review') and 'when' with a 'Use when asked to...' clause containing concrete trigger phrases, exactly matching the top anchor. Not level 4 because the 'when' is fully explicit, not merely adequate.

5 / 5

Trigger Term Quality

Seven natural quoted trigger phrases — 'review Django performance', 'find N+1 queries', 'optimize Django', 'check queryset performance', 'database performance', 'Django ORM issues', 'audit Django code' — comprehensively cover user phrasings with synonym verbs (review/find/optimize/check/audit). File extensions do not apply to this domain, so nothing meaningful is missing.

5 / 5

Distinctiveness Conflict Risk

The Django-performance niche is mostly distinct with Django-specific triggers, but the generic phrase 'database performance' could overlap with non-Django database skills, giving minor overlap risk. It does not fit level 5's 'minimal conflict risk' because of that broad trigger.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

BigSimmo/Communication

Path

.agents/skills/django-perf-review/SKILL.md

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.