CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

django-access-review

django-access-review

Quality

53%

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

Quality

Content

77%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 strong, highly actionable investigation methodology with an exemplary worked example, executable commands, and a validation-gated workflow. Its weaknesses are textual hygiene — a malformed duplicated frontmatter block leaking into the body — and monolithic organization with no reference files for the pattern catalogue and report template. Fixing the frontmatter leak and trimming redundant sections would lift it substantially.

Suggestions

Delete the stray second frontmatter block and dangling '--- LICENSE' line from the body — the truncated description there is malformed metadata noise, not content, and its intended description belongs in the real frontmatter.

Move the 'Common Django Authorization Patterns' catalogue and the 'Report Format' template into references/ files (e.g. references/patterns.md, references/report-template.md) and link to them one level deep from SKILL.md.

Trim redundancy: the closing 'Investigation Checklist' restates the five phases and the 'When to Use' section duplicates description-level content — collapsing these would tighten token usage without losing guidance.

DimensionReasoningScore

Conciseness

The body is mostly dense and actionable (phases, grep commands, worked example), but includes clear waste: a stray duplicated and truncated frontmatter block plus a dangling '--- LICENSE' line at the top, a 'When to Use' section that duplicates description content, and a closing 'Investigation Checklist' that restates the five phases. This fits anchor 3 ('Mostly efficient but includes some unnecessary explanation or could be tightened') better than anchor 4, since the redundant sections exceed 'minor instances'.

3 / 5

Actionability

Fully executable throughout: copy-paste grep commands ('grep -rn "permission_classes\|@login_required\|@permission_required" --include="*.py"'), concrete Python patterns for each authorization mechanism, a complete worked IDOR investigation of GET /api/documents/{pk}/, and explicit GOOD/BAD fix code ('if resource.owner_id != user.id: raise PermissionDenied'). Specific examples cover the common cases, matching anchor 5.

5 / 5

Workflow Clarity

Five clearly sequenced phases with an explicit gate ('Do not proceed until you understand the authorization model'), a verification loop in Phase 3 ('If you can't find a check, is there one you missed? Check parent classes / middleware / managers'), a confidence-level table that validates findings before reporting, and a final checklist. This matches anchor 5's 'clear sequence with explicit validation steps; feedback loops; checklists'; the destructive/batch cap does not apply to this read-only review skill.

5 / 5

Progressive Disclosure

There are no bundle files at all — everything is inlined in a single ~350-line SKILL.md. Internal headers are clear, but content that naturally belongs in reference files (the 'Common Django Authorization Patterns' catalogue and the full report-format template) is inlined, and the stray frontmatter block adds navigation noise at the top. This is anchor 3 ('Some structure but could be better organized; content that should be separate is inline'), not anchor 2 (structure is genuinely good) nor anchor 4 (which expects appropriately split content).

3 / 5

Total

16

/

20

Passed

Description

7%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 field is effectively empty of descriptive content — it merely repeats the skill name as a slug. It fails on every dimension except a weak nominal distinctiveness from the name itself. The well-written description that exists in the body's stray second frontmatter block was never placed in the actual frontmatter.

Suggestions

Replace the description with a real sentence describing what the skill does, e.g. 'Django access control and IDOR security review: investigates views, DRF viewsets, and ORM queries to find object-level authorization gaps.'

Add an explicit 'Use when' trigger clause with natural phrases users would say, such as: 'Use when reviewing Django/DRF code for IDOR, access control, authorization, object permissions, or tenant isolation issues.'

Move the trigger keywords already drafted in the body's duplicated frontmatter block ('IDOR', 'access control', 'authorization', 'Django permissions', 'object permissions', 'tenant isolation') into the actual frontmatter description so the skill can be discovered.

DimensionReasoningScore

Specificity

The description is the bare slug "django-access-review", identical to the name field, with no action verbs or described capabilities whatsoever. This matches the anchor 'Entirely vague; no concrete actions; pure abstract language' and is below anchor 2, which at least requires minimal/generic actions.

1 / 5

Completeness

Neither 'what does this do' nor 'when should Claude use it' is present in any form — the field is only a slug. This is squarely anchor 1 ('Missing both what and when'), and the guideline capping completeness at 3 for a missing 'Use when' clause is far exceeded here.

1 / 5

Trigger Term Quality

There are no natural keywords or phrases a user would say — just a hyphenated identifier. Anchor 1 ('No natural keywords; only technical jargon or entirely generic language') is the closest fit; anchor 2 would require at least one or two generic keywords in sentence form.

1 / 5

Distinctiveness Conflict Risk

The slug does explicitly name a niche ("django", "access", "review"), making it more specific than the generic anchors 1-2, but with no descriptive text or triggers it can only be distinguished by name and could still overlap with other Django/security review skills. It sits at anchor 3 ('Somewhat specific but could still overlap with similar skills'), not anchor 4, which presumes descriptive content establishing distinct triggers.

3 / 5

Total

6

/

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

BigSimmo/Communication

Path

.agents/skills/django-access-review/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.