CtrlK
BlogDocsLog inGet started
Tessl Logo

django-pro

Master Django 5.x with async views, DRF, Celery, and Django Channels. Build scalable web applications with proper architecture, testing, and deployment.

44

Quality

46%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/django-pro/SKILL.md

The canonical home for this skill is django-pro in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

31%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 verbose persona/capability manifesto that assumes Claude needs to be told basic Django concepts, with no executable code or commands and a broken reference to a missing playbook. It is organized into sections but lacks progressive disclosure and concrete guidance.

Suggestions

Replace the long capability/knowledge-base lists with concise, actionable guidance and move detailed material into real reference files under references/ (the current resources/implementation-playbook.md link is broken).

Add concrete, copy-paste-ready code examples for the most common tasks (e.g. async view, DRF serializer, Celery task, prefetch_related query) instead of describing them abstractly.

Tighten the workflow with explicit validation checkpoints (e.g. run migrations, run pytest-django, check django-silk profile) rather than a generic 8-step response approach.

DimensionReasoningScore

Conciseness

The body is a long, padded persona document that restates Django concepts Claude already knows ('Django signals and their proper usage patterns', 'Django's security middleware and best practices') across lengthy capability and knowledge-base lists, with several unnecessary sections.

2 / 5

Actionability

Guidance is almost entirely abstract — capability lists, behavioral traits, and generic instructions like 'Apply relevant best practices and validate outcomes' — with no concrete code, commands, or executable examples; the only reference (resources/implementation-playbook.md) does not exist.

2 / 5

Workflow Clarity

The 'Response Approach' lists a reasonable 8-step sequence (analyze, suggest, provide code, test, consider performance, etc.) but the steps are abstract with no validation checkpoints or feedback loops.

3 / 5

Progressive Disclosure

All capability content is inlined monolithically in SKILL.md rather than split into reference files, and the single reference to resources/implementation-playbook.md is a dead link to a nonexistent file with no references/ or resources/ bundle present.

2 / 5

Total

9

/

20

Passed

Description

61%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 clearly names the Django 5.x niche and several concrete technologies, but lacks an explicit 'Use when...' trigger clause, which caps its completeness. It is specific and distinct but reads more as a capability headline than trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Django 5.x projects, DRF APIs, Celery tasks, Channels/WebSockets, or Django ORM performance issues.'

Replace the abstract 'Master Django' lead with concrete actions the skill performs (e.g. 'Designs, debugs, and optimizes Django 5.x codebases').

Include natural synonyms/file cues users say (e.g. 'Django REST Framework', '.py', 'models.py', 'views.py') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Names the Django 5.x domain and several concrete subareas ('async views, DRF, Celery, and Django Channels') plus actions ('Build scalable web applications with proper architecture, testing, and deployment'), but the actions are relatively high-level and 'Master Django' is abstract, so coverage is solid rather than comprehensive.

3 / 5

Completeness

Provides a clear 'what' (master Django 5.x, build scalable web apps) but no explicit 'Use when...' trigger clause; per the judging guidelines a missing 'when' caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms users actually say — 'Django', 'DRF', 'Celery', 'Django Channels', 'async views' — giving good keyword coverage, though common synonyms like 'REST API' or 'web framework' are missing.

4 / 5

Distinctiveness Conflict Risk

The Django 5.x niche with named ecosystem tools (DRF, Celery, Channels) is mostly distinct with minimal conflict risk, though there is minor overlap with a generic Python/web-application skill.

4 / 5

Total

14

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.