CtrlK
BlogDocsLog inGet started
Tessl Logo

django-verification

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./skills/django-verification/SKILL.md

The canonical home for this skill is tdg-personal/django-verification

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.

A thorough, actionable verification playbook with clear phase sequencing and validation before risky steps. Its weaknesses are token bulk (large inlined examples), implicit rather than explicit feedback loops, and no progressive disclosure into reference files.

Suggestions

Move the full CI workflow YAML and the ~80-line output report template into separate reference files (e.g. references/ci-example.yml, references/report-template.md) and link to them from SKILL.md to cut inlined bulk.

Add explicit per-phase feedback loops, e.g. after Phase 5: 'If pip-audit reports vulnerabilities, upgrade the dependencies and re-run pip-audit before proceeding to deployment checks.'

Remove the duplicated `python manage.py check --deploy` (Phase 2 and Phase 5) and replace Phase 7's manual browser inspection with an executable query-count check.

DimensionReasoningScore

Conciseness

Mostly commands that earn their place, but an ~80-line illustrative output report, a full ~60-line CI workflow YAML, and redundancy (`check --deploy` appears in both Phase 2 and Phase 5) could be tightened or moved to references.

3 / 5

Actionability

Extensive copy-paste-ready commands across all phases, but Phase 7 performance checks are partly manual/instructional and the `create_superuser` snippet uses an incorrect call signature.

4 / 5

Workflow Clarity

Twelve clearly sequenced phases with dry-runs and checks before destructive migration steps, plus a pre-deployment checklist; however, fix-and-retry feedback loops are only implied per phase rather than explicitly stated.

4 / 5

Progressive Disclosure

Well-organized section headers and a quick-reference table, but ~460 lines are monolithic with the CI workflow and full report template inlined; no bundle files exist to offload detail.

3 / 5

Total

14

/

20

Passed

Description

83%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, specific, third-person description that names concrete actions and a clear niche. Its main gap is the brief, implicit "when" clause rather than an explicit, trigger-rich "Use when..." phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete verification actions — "migrations, linting, tests with coverage, security scans, and deployment readiness checks" — giving comprehensive coverage of the loop's capabilities.

5 / 5

Completeness

Clearly states what the skill does (a verification loop with named checks) and when ("before release or PR"), but the "when" is brief rather than a full explicit "Use when..." trigger phrase with concrete triggers.

4 / 5

Trigger Term Quality

Includes natural terms a Django developer would say ("Django projects", "migrations", "linting", "tests with coverage", "security scans", "release or PR"), but lacks some synonyms or variations that would round out coverage.

4 / 5

Distinctiveness Conflict Risk

Targets a clear Django-specific verification niche with distinct triggers, so overlap risk with non-Django or non-verification skills is 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
affaan-m/ECC
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.