django-patterns

Django架构模式、使用DRF的REST API设计、ORM最佳实践、缓存、信号、中间件以及生产级Django应用程序。

Install with Tessl CLI

npx tessl i github:affaan-m/everything-claude-code --skill django-patterns

What are skills?

Overall
score

61%

Review — 49%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

33%

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 identifies Django as its domain and lists relevant technical topics, but reads more like a feature list than actionable guidance for skill selection. It completely lacks explicit trigger conditions ('Use when...') and uses topic areas rather than concrete actions, making it difficult for Claude to know precisely when to select this skill over others.

Suggestions

Add an explicit 'Use when...' clause specifying trigger scenarios (e.g., 'Use when the user asks about Django projects, building REST APIs with Django, or Django ORM queries').

Convert topic areas into concrete actions (e.g., 'Designs REST APIs using Django REST Framework, optimizes ORM queries, implements caching strategies').

Include natural language variations users might say (e.g., 'Django web app', 'Django backend', 'DRF endpoints', 'Django models').

Dimension	Reasoning	Score
Specificity	Names the domain (Django) and lists several specific areas (DRF REST API design, ORM best practices, caching, signals, middleware), but these are topic areas rather than concrete actions the skill performs.	2 / 3
Completeness	Describes what areas the skill covers but completely lacks any 'Use when...' clause or explicit trigger guidance. The 'when' component is entirely missing.	1 / 3
Trigger Term Quality	Includes relevant technical terms like 'Django', 'DRF', 'REST API', 'ORM', 'middleware' that users might mention, but lacks common variations and natural language triggers users would actually say (e.g., 'Django project', 'web app', 'backend').	2 / 3
Distinctiveness Conflict Risk	Django-specific focus provides some distinctiveness, but could overlap with general Python skills, web development skills, or API design skills. The broad scope ('production-grade Django applications') increases conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid Django patterns reference with excellent actionable code examples covering models, DRF, caching, signals, and middleware. The main weaknesses are its monolithic structure (could benefit from splitting into separate reference files) and lack of explicit workflow validation steps for production deployment or migration processes. The content is slightly verbose in places but generally respects Claude's intelligence.

Suggestions

Split detailed sections (caching, signals, middleware, DRF patterns) into separate reference files and link from a concise overview in SKILL.md

Add explicit workflow sequences with validation checkpoints for common operations like migrations, deployment, or setting up a new Django project

Trim the settings examples - show only the key differences between environments rather than full configuration files

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some verbose sections. The project structure and settings examples are quite lengthy, and some patterns (like basic model fields) are things Claude already knows. However, it avoids explaining basic Django concepts.	2 / 3
Actionability	Excellent actionability with fully executable, copy-paste ready code examples throughout. Every pattern includes concrete Python code with proper imports, class definitions, and usage examples.	3 / 3
Workflow Clarity	The skill presents patterns clearly but lacks explicit validation checkpoints or feedback loops. For production-grade Django apps, there should be validation steps for migrations, deployment workflows, or testing sequences. The content is more reference-style than workflow-oriented.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers, but it's a monolithic document with no references to external files for detailed topics. Advanced topics like caching strategies, signals, and middleware could be split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Validation

91%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (734 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.