CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

django-pro

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

Quality

50%

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-claude/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

17%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 persona prompt, not a usable skill: it catalogs capabilities and traits at length but provides zero executable guidance, no validation checkpoints, and its single pointer to detail targets a nonexistent file. It needs to be rebuilt around concrete code, commands, and real reference files.

Suggestions

Replace the capability/trait/knowledge catalogs with concrete, executable guidance: example model/serializer/view code, migration commands, pytest-django test snippets, and Celery/Channels setup commands.

Fix the broken reference — either create 'resources/implementation-playbook.md' with the detailed patterns or remove the pointer; move the capability and integration catalogs into that reference file.

Turn the 'Response Approach' into a real workflow with validation checkpoints (e.g., run migrations check, run test suite, verify with DRF test client) instead of abstract step labels.

DimensionReasoningScore

Conciseness

Roughly 170 lines are spent enumerating capabilities, behavioral traits, and a knowledge base that largely restate what a competent model already knows about Django, and the Purpose section repeats the persona sentence verbatim — noticeably verbose with several padded sections, though it never lapses into extended concept explanations.

2 / 5

Actionability

There is no code, command, or concrete step anywhere in the body; instructions like 'Clarify goals, constraints, and required inputs. Apply relevant best practices and validate outcomes.' are entirely abstract, describing rather than instructing.

1 / 5

Workflow Clarity

The 'Response Approach' section provides a rough 8-step sequence ('Analyze requirements' → 'Suggest Django-idiomatic solutions' → 'Provide production-ready code'), but the steps are abstract labels with no validation checkpoints or error-recovery guidance, matching 'rough sequence present but many gaps; validation absent'.

2 / 5

Progressive Disclosure

The only reference, 'resources/implementation-playbook.md', does not exist in the bundle (no references/, scripts/, assets/, or resources/ directories), and a large inline catalog of capabilities and integrations is exactly the content that belongs in separate files — minimal structure with inlined content and a broken reference.

2 / 5

Total

7

/

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.

A reasonably specific, domain-focused description with good trigger keywords, but it lacks any 'Use when...' trigger clause and leans on broad verbs ('Master', 'Build') with mild buzzword padding ('proper architecture'). Adding explicit trigger guidance would lift it from adequate to strong.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working on Django projects, DRF APIs, Celery tasks, or Django Channels websockets.'

Replace vague verbs and filler ('Master', 'proper architecture') with concrete actions like 'Design models and migrations, optimize ORM queries, configure DRF serializers and JWT auth'.

Include natural user phrasings such as 'ORM', 'queryset', 'migrations', and 'REST API' to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain and specific technologies ('async views, DRF, Celery, and Django Channels'), but the actual verbs are broad ('Master', 'Build') and 'proper architecture, testing, and deployment' is generic, matching the 'names domain and concrete actions but not comprehensive' anchor rather than the fully concrete action list of level 4.

3 / 5

Completeness

The 'what' is clearly stated (build scalable web applications with Django 5.x, DRF, Celery, Channels), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Terms like 'Django 5.x', 'DRF', 'Celery', 'Django Channels', and 'async views' are natural phrases users say, giving good coverage, but common variations users would actually utter ('ORM', 'queryset', 'migrations', 'REST API') are missing, which fits the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Django/DRF/Celery/Channels is a clear niche with distinct triggers, but the generic second sentence 'Build scalable web applications with proper architecture, testing, and deployment' overlaps with general web-development skills, matching 'mostly distinct; minor overlap risk'.

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.

Validation — 15 / 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

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/django-pro/SKILL.md

Revision

64adc55

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill