CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

django-best-practices

Django best practices baseadas em cookiecutter-django e produção real

Quality

64%

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 ./skills/backend/django/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 lean, well-organized conventions guide with mostly concrete, executable examples and strong protective rules around migrations. Its main weaknesses are broken or dangling code/references — the cache example won't run and both 'Referência obrigatória' files are absent from the bundle — and monolithic structure that should offload the SQL and cache snippet libraries to bundled reference files.

Suggestions

Fix the cache example so it is executable: define profile_data, guard User.objects.get with error handling, and use a real settings source for Redis connection parameters.

Either bundle the referenced snippet files (django-sql-snippets.py, redis-cache-snippet.py) under references/ and link them clearly, or remove the 'Referência obrigatória' pointers to the external cursor-multiagent-system that this skill does not ship.

Add an explicit migration-test feedback loop (run migrations in development → if failures occur, fix and re-run before proceeding) to raise workflow clarity for the destructive migration rules.

DimensionReasoningScore

Conciseness

The body is convention-first with terse rules and code examples, explaining almost nothing Claude already knows — e.g., the settings section jumps straight to a django-environ snippet and the models section shows code without tutorial prose. Only minor trimming is possible (the final checklist restates earlier rules, and the directory tree is long), so it sits between anchor 3 and the lean anchor 5, noticeably above the midpoint.

4 / 5

Actionability

Most sections give concrete code (env-based settings, custom user model, serializer, viewset), but key examples are incomplete or broken: the cache example calls cache.save(cache_key, profile_data, ...) with an undefined profile_data and nonstandard settings.REDIS_HOST, and the SQL/cache sections cite 'Referência obrigatória' files (core/templates/database/django-sql-snippets.py, cursor-multiagent-system) that do not exist in this skill's bundle. This matches 'Some concrete guidance but incomplete… missing key details' rather than 4, where gaps would be minor.

3 / 5

Workflow Clarity

Sections are clearly organized with explicit do/don't rules, and the destructive migration section includes a validation checkpoint ('SEMPRE testar migrations em desenvolvimento primeiro') plus a final checklist — matching 'Clear sequence with most checkpoints present; minor validation gaps'. It is below 5 because there is no explicit feedback loop (e.g., what to do when a migration test fails) for the destructive/batch operations it governs.

4 / 5

Progressive Disclosure

The file is well-sectioned with headers, but it is a ~230-line monolith exceeding the simple-skill threshold: the SQL-snippet and cache-system content belongs in bundled reference files, and the only references in the body point to files outside this skill's bundle ('core/templates/database/django-sql-snippets.py', 'core/templates/cache/redis-cache-snippet.py' from 'cursor-multiagent-system') that are not present. This matches 'Some structure but could be better organized' rather than 4, where references would be real and clearly signaled.

3 / 5

Total

14

/

20

Passed

Description

48%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 identifies its Django niche and provenance but functions as a label rather than an actionable trigger description. It lacks any 'Use when...' guidance and lists no concrete capabilities, and it misses natural trigger variations like DRF or Django REST Framework.

Suggestions

Add an explicit trigger clause, e.g., 'Use when working on Django or Django REST Framework projects — models, serializers, views, migrations, settings, or project structure.'

Enumerate 2-4 concrete capabilities in the description (e.g., 'Enforces cookiecutter-django project layout, environment-based settings, custom user model, and safe migration practices') instead of the generic 'best practices' label.

Include natural trigger variations users would actually say (DRF, Django REST Framework, 'Django conventions', 'Django project setup') to raise trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain ('Django best practices') and a concrete source ('baseadas em cookiecutter-django e produção real') but enumerates no concrete actions or capabilities, matching the anchor 'Names the domain but actions are minimal or generic'. It is above 1 because it is not pure abstract language, and below 3 because no specific actions (e.g., structure projects, write serializers, manage migrations) are listed.

2 / 5

Completeness

The 'what' is clear (Django best practices derived from cookiecutter-django and production experience), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the 'what' is not vague.

3 / 5

Trigger Term Quality

'Django' is the dominant natural keyword a user would say, but the description omits common variations and synonyms (DRF, Django REST Framework, conventions, project setup). This matches 'Some relevant keywords but missing common variations or synonyms' rather than 4, since coverage beyond the single word 'Django' is thin.

3 / 5

Distinctiveness Conflict Risk

'Django' carves a clear, distinct niche with minimal conflict against non-Django skills; residual overlap risk exists only with other closely related Django-specific skills (e.g., testing or deployment skills), matching 'Mostly distinct; minor overlap risk with closely related skills'. Not 5 because 'best practices' is a broad umbrella within the Django ecosystem.

4 / 5

Total

12

/

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

fernandezbaptiste/cursor-multiagent-system

Path

skills/backend/django/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.