CtrlK
BlogDocsLog inGet started
Tessl Logo

dmr-from-drf

Migrate an existing Django API from Django REST Framework to django-modern-rest while preserving routes, request/response contracts, auth, permissions, throttling, pagination, and test coverage. Use when replacing APIView/ViewSet/GenericAPIView and DRF serializers/routers with dmr controllers/routers and typed DTOs.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A well-structured, workflow-driven migration skill with strong sequencing, validation gates, and a properly signaled one-level reference. Its main weakness is redundancy across the workflow, rules, pitfalls, and checklist sections, and a lack of executable code examples.

Suggestions

Consolidate the repeated parity concerns (auth/permissions/throttles, parser/renderer, pagination) so each is stated once in the Workflow and referenced from the checklist, rather than restated in Translation Rules, Migration Pitfalls, and the Output Checklist.

Add one or two short executable snippets (e.g. a minimal Controller[...] with Body[...]/ResponseSpec and a validate_responses snippet) to lift actionability from prose-instructed to copy-paste-ready.

Trim or fold the 'Migration Pitfalls (DRF-derived)' section into the relevant workflow steps (e.g. trailing-slash under step 8, partial=True under step 6) to reduce token overhead while preserving the guidance.

DimensionReasoningScore

Conciseness

Mostly efficient and assumes Claude knows Django/DRF, but it is long and somewhat repetitive — the same parity concerns (auth/permissions/throttles, parser/renderer, pagination) are restated across Workflow, Translation Rules, Migration Pitfalls, and the Output Checklist, which could be tightened.

2 / 3

Actionability

It gives concrete, specific guidance (named DMR constructs like Controller[...], Body[...], Query[...], ResponseSpec, validate_responses) and points to a real mapping reference, but contains little executable code — it instructs in prose rather than giving copy-paste-ready snippets, which suits an instruction-heavy skill but stops short of fully executable examples.

2 / 3

Workflow Clarity

A clearly sequenced 12-step workflow with explicit gates and feedback loops — a 'Decide error strategy (required gate)', per-slice validation ('Validate each slice with repository-native CI entrypoints'), and a 'Finish gate' that blocks completion until linters/tests pass and the report is updated.

3 / 3

Progressive Disclosure

The body is an overview that signals a single one-level-deep reference ([references/drf-to-dmr-map.md]) plus two external doc URLs, and the reference file exists and is appropriately scoped; the detailed construct mapping lives in the reference rather than inline.

3 / 3

Total

10

/

12

Passed

Description

100%

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 description in third person that covers what it does, when to use it, and the exact construct mapping involved. It is concise, well-targeted, and unlikely to conflict with sibling skills.

DimensionReasoningScore

Specificity

Names many concrete actions — 'preserving routes, request/response contracts, auth, permissions, throttling, pagination, and test coverage' and itemizes the concrete class swaps from 'APIView/ViewSet/GenericAPIView and DRF serializers/routers' to 'dmr controllers/routers and typed DTOs'.

3 / 3

Completeness

It answers 'what' ('Migrate an existing Django API from Django REST Framework to django-modern-rest while preserving...') and 'when' explicitly ('Use when replacing APIView/ViewSet/GenericAPIView and DRF serializers/routers with dmr controllers/routers and typed DTOs').

3 / 3

Trigger Term Quality

Surfaces the natural terms users would actually say — 'Django REST Framework', 'django-modern-rest', 'APIView', 'ViewSet', 'GenericAPIView', 'serializers', 'routers', and 'DTOs' — giving strong keyword coverage for someone asking to migrate from DRF.

3 / 3

Distinctiveness Conflict Risk

It carves a narrow niche (DRF→dmr transport migration) with distinct triggers tied to specific DRF class names, making it unlikely to fire for unrelated Django or generic migration skills.

3 / 3

Total

12

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wemake-services/django-modern-rest
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.