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. Use PROACTIVELY for Django development, ORM optimization, or complex Django patterns.

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/django-pro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%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 reads as a generic Django-expert persona padded with topic enumerations Claude already knows, offering little executable guidance. It needs concrete code/patterns, real validation checkpoints, and offloading of reference material to bundle files.

Suggestions

Cut the Knowledge Base and capability enumerations (concepts Claude already knows) and replace them with a few concrete, copy-paste patterns for the highest-value tasks (e.g., an N+1-fix queryset example, an async view example, a Celery task + test).

Add explicit validation checkpoints to the Response Approach (e.g., 'run pytest-django and confirm green before suggesting deployment'; 'verify migrations with `python manage.py makemigrations --check`').

Move detailed capability/reference material into `references/` files (e.g., `references/orm-optimization.md`, `references/deployment.md`) and link them one level deep from SKILL.md so the overview stays lean.

DimensionReasoningScore

Conciseness

The body is a long enumeration of well-known Django ecosystem facts ("Django signals and their proper usage patterns", "CORS, CSRF, and XSS protection", "select_related, prefetch_related") that Claude already knows, making most of the ~170 lines padded rather than additive.

2 / 5

Actionability

Guidance stays high-level ("Django ORM optimization with select_related, prefetch_related", "Provide production-ready code"); there is no executable code, no commands, and no concrete steps, only topical hints.

2 / 5

Workflow Clarity

The numbered Response Approach (analyze, suggest, implement, test, consider performance, document, migrate, deploy) gives a sequence, but validation is only abstractly mentioned ("validate outcomes") with no explicit checkpoints or feedback loops.

3 / 5

Progressive Disclosure

Sections are organized, but the skill is a single monolithic file with no bundle references; capability and knowledge-base lists that would belong in separate reference files are all inlined, and the skill exceeds the <50-line simple-skill exception.

3 / 5

Total

10

/

20

Passed

Description

87%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, well-scoped description that clearly states capabilities and explicit trigger guidance for a distinct Django niche. It could push specificity to 5 by replacing generic verbs ("Master", "Build") with discrete, named actions.

Suggestions

Replace generic verbs ("Master", "Build") with concrete, countable actions (e.g., "Design models", "Optimize querysets", "Configure Celery tasks", "Deploy with Gunicorn + Docker").

Add a few natural synonyms users say ("Django app", "Django REST API", "Django models") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain plus several concrete capability areas ("async views, DRF, Celery, and Django Channels", "architecture, testing, and deployment", "ORM optimization"), but the verbs "Master" and "Build" stay generic rather than enumerating discrete actions like the 5-anchor PDF example.

4 / 5

Completeness

Explicitly answers what ("Master Django 5.x...", "Build scalable web applications...") and when ("Use PROACTIVELY for Django development, ORM optimization, or complex Django patterns") with concrete trigger phrases, matching the 5-anchor pattern.

5 / 5

Trigger Term Quality

Covers natural terms a user would say ("Django development", "ORM optimization", "complex Django patterns") plus ecosystem names (DRF, Celery, Channels), but misses common synonyms like "Django app", "Django models", or "Django REST API".

4 / 5

Distinctiveness Conflict Risk

The Django 5.x / DRF / Celery / Channels niche is sharply scoped with distinct triggers, making conflict with other skills minimal.

5 / 5

Total

18

/

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
rmyndharis/antigravity-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.