CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

django-security

Django security best practices, authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations.

Quality

70%

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 ./.kiro/skills/django-security/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 well-organized, highly actionable reference with concrete settings and GOOD/BAD examples across all major Django security domains. Its weaknesses are token efficiency (significant boilerplate Claude already knows) and the complete absence of progressive disclosure — all 590 lines are inlined with no reference files.

Suggestions

Move the bulkier, less-frequently-needed sections (RBAC patterns, DRF permissions, logging config, file upload validation) into one-level-deep reference files under references/ and link them from a concise SKILL.md overview.

Trim content Claude already knows — the getCookie JavaScript, the AUTH_PASSWORD_VALIDATORS boilerplate, and explanatory comments about Django's defaults — down to one-line reminders.

Fix the minor executability gaps: import ImproperlyConfigured in the production settings snippet, import User/Response in view snippets, and remove the non-existent MEDIA_DOMAIN setting.

DimensionReasoningScore

Conciseness

The body is mostly lean code blocks with GOOD/BAD contrast rather than padded prose, but several sections restate knowledge Claude already has — the verbatim getCookie JavaScript from the Django docs, the full AUTH_PASSWORD_VALIDATORS boilerplate, and explanations like "Django ORM automatically escapes parameters" and "Django auto-escapes variables by default". It could be roughly halved without losing skill-specific value, matching anchor 3 rather than 4.

3 / 5

Actionability

Most guidance is concrete, copy-paste-ready code: production settings, a custom user model, DRF permission classes, raw SQL parameterization, CSRF cookie settings, and middleware. Minor gaps keep it below anchor 5: the production.py snippet references ImproperlyConfigured without importing it, some snippets use User/Response without imports, and MEDIA_DOMAIN is not a real Django setting.

4 / 5

Workflow Clarity

As a topic-organized reference rather than a sequential workflow, it provides a clear 'When to Activate' section and a final 'Quick Security Checklist' that acts as a verification artifact for review tasks. It reaches anchor 4 but not 5 because there is no explicit step sequence or feedback loop for tasks like a production security review or deployment.

4 / 5

Progressive Disclosure

No bundle files exist — everything (approximately 590 lines) is inlined in SKILL.md. Section headers are clear and well-ordered, but substantial content that belongs in one-level-deep reference files (RBAC patterns, DRF permissions, logging config, file upload validation) is inline, matching anchor 3's 'content that should be separate is inline'.

3 / 5

Total

14

/

20

Passed

Description

66%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 is specific and domain-distinct with good natural trigger terms for the Django security domain, but it completely lacks a "Use when..." trigger clause, which caps its completeness and weakens its activation guidance. Adding explicit usage triggers would lift both completeness and distinctiveness.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when setting up or reviewing Django authentication, permissions, or production security settings, or when the user mentions CSRF, SQL injection, XSS, or hardening a Django app.'

Include more user-natural synonyms such as 'permissions', 'security hardening', or 'secure my Django app' to broaden trigger term coverage.

Mention the remaining capability areas the skill actually covers (password validation, file uploads, rate limiting, security headers) so the description matches the body's scope.

DimensionReasoningScore

Specificity

The description lists several specific capability areas ("authentication, authorization, CSRF protection, SQL injection prevention, XSS prevention, and secure deployment configurations"), though these are noun-phrase topics rather than concrete actions and miss some areas covered by the skill (passwords, file uploads, rate limiting, security headers). It sits at anchor 4 rather than 3 because coverage goes well beyond 1-2 actions, and below 5 because it lacks concrete action verbs and comprehensive coverage.

4 / 5

Completeness

The "what" is clear (the enumerated Django security domains), but there is no "Use when..." clause or equivalent explicit trigger guidance — the "when" is only weakly implied. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like "Django security", "CSRF protection", "SQL injection", "XSS", and "authentication" are natural phrases users would say when needing this skill. It falls short of anchor 5 because common variations such as "permissions", "security hardening", or "secure my Django app" phrasing are absent, but exceeds anchor 3's partial keyword coverage.

4 / 5

Distinctiveness Conflict Risk

"Django security" carves out a clear niche unlikely to trigger for unrelated skills, with only minor overlap risk against a generic web-security or security-review skill. It does not reach anchor 5 because the absence of distinct explicit trigger phrases leaves some conflict room with closely related security skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (591 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

affaan-m/ECC

Path

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