dmr

Write the best DMR code possible with all the recommended best practices, avoiding common mistakes.

Quality

48%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/dmr/SKILL.md

Quality

Content

65%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 content is highly actionable, with complete Wrong/Correct code pairs and per-rule rationale, limitations, and docs links for every guideline. Its weaknesses are a monolithic 1570-line structure with no progressive disclosure into separate files and notable repetition (import boilerplate, duplicate 404/500 sections).

Suggestions

Split the catalog into one reference file per topic (e.g. references/controllers.md, references/routing.md, references/testing.md) and keep SKILL.md as a concise overview with one-level-deep links, improving progressive_disclosure and conciseness.

Remove repeated import boilerplate from examples (show imports once per topic or use '...' elision) and merge the near-identical build_404_handler and build_500_handler sections into one parameterized rule.

Add a brief top-of-file workflow or decision guide (e.g. 'When adding a new endpoint: pick serializer -> define controller -> set error handling -> wire routing -> add tests') to give the catalog a sequencing backbone.

Dimension	Reasoning	Score
Conciseness	The body is mostly code-focused with brief rationales and no padding about basic concepts, but it repeats full import blocks in every example and includes near-duplicate 404/500 handler sections, fitting 'Mostly efficient but includes some unnecessary explanation or could be tightened'. It is above 2 because it avoids concept re-explanation, but the boilerplate repetition keeps it below 4.	3 / 5
Actionability	Every rule provides complete, copy-paste-ready Wrong/Correct Python examples with imports, plus rationale, Limitations, and Docs links, matching 'Fully executable; copy-paste ready code... specific examples cover the common cases'. The examples are concrete and cover the framework's main surfaces.	5 / 5
Workflow Clarity	This is a catalog of independent best-practice rules organized by topic rather than a sequenced multi-step process, so there is no workflow sequence or validation checkpoint to follow, fitting 'sequence present but checkpoints missing or implicit' only loosely. It is above 2 because topical headers give clear navigation, but the absence of any process/verification structure caps it at 3.	3 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and all 1570 lines live inline in SKILL.md with only external Docs links and no local file references, fitting 'content that should be separate is inline'. The clear hierarchical section headers keep it above 2, but the monolithic length and lack of any split-out reference files prevent a 4.	3 / 5
	Total	14 / 20 Passed

Description

32%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 names its target framework but relies on abstract phrasing ('best practices', 'common mistakes') instead of concrete capabilities, and it omits any 'Use when...' trigger guidance. It is reasonably distinct as a DMR-specific skill yet weak on specificity, triggers, and completeness.

Suggestions

Replace abstract language with concrete capabilities, e.g. 'Define DMR controllers, choose serializers, handle errors, configure routing and throttling for django-modern-rest.'

Add an explicit trigger clause: 'Use when writing or reviewing django-modern-rest (DMR) controllers, serializers, routing, or error handling.'

Include the full name 'django-modern-rest' alongside 'DMR' so users who don't know the abbreviation can still trigger the skill.

Dimension	Reasoning	Score
Specificity	The phrase 'Write the best DMR code possible with all the recommended best practices, avoiding common mistakes' names the DMR domain but only offers generic actions ('best practices', 'common mistakes') rather than concrete capabilities, matching the anchor 'Names the domain but actions are minimal or generic'. It does not list 1-2 concrete actions, so it stays below 3.	2 / 5
Completeness	It gives only a vague 'what' ('best DMR code... best practices... avoiding common mistakes') and entirely lacks a 'Use when...' trigger clause, matching 'Has a vague what and no when'. The missing explicit trigger guidance caps completeness at 3, and the vague what pulls it to 2.	2 / 5
Trigger Term Quality	The only substantive keyword is the jargon abbreviation 'DMR code'; 'best practices' and 'common mistakes' are generic and the natural phrases a user would say ('django-modern-rest', 'Django REST views/controllers') are absent, fitting 'one or two generic keywords; missing the natural phrases users say'. It is above 1 because it does name the target domain.	2 / 5
Distinctiveness Conflict Risk	Naming the specific framework 'DMR' (django-modern-rest) carves a clear niche with only minor overlap against general Django skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is below 5 because the generic 'best practices / common mistakes' framing dilutes the distinct triggers.	4 / 5
	Total	10 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: wemake-services/django-modern-rest
Path: .agents/skills/dmr/SKILL.md
Commit: 87a02f5

Reviewed: 3 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.