dmr-openapi-skeleton

Generate django-modern-rest transport-layer skeletons from OpenAPI 3.1+ specs. Use when Codex needs to turn an OpenAPI file, URL, or pasted document into typed DTOs, controllers, routers, Django URL wiring, and minimal tests for this repository or similar projects built on dmr. Trigger on requests to scaffold APIs, bootstrap apps, or map OpenAPI operations to Controller, Router, and OpenAPI view constructs without implementing business logic.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

81%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.

A well-structured, highly specific instruction skill with an excellent sequenced workflow and explicit validation gates, backed by real one-level-deep reference files. Its main costs are repetition of spec-fidelity guidance across multiple sections and the absence of a complete executable code example in the body itself.

Suggestions

Consolidate the spec-fidelity rules that currently repeat across sections 1a, 10, 11, Translation Rules, and the Output Checklist into a single gate (e.g. keep step 11 authoritative and reference it elsewhere) to reduce duplicated tokens.

Add one complete, copy-paste-ready example (a small Controller + Router + DTO set) either inline or prominently at the top of references/framework-patterns.md, since the body currently only shows API fragments.

Move the media-type negotiation and translation-rule details (Translation Rules section) into references/framework-patterns.md or a dedicated reference, keeping the body as a lean overview that signals where each rule lives.

Dimension	Reasoning	Score
Conciseness	The body is dense imperative guidance with no padding or explanation of concepts Claude already knows, but spec-fidelity rules repeat across sections 1a, 10, 11, Translation Rules, and the Output Checklist, and dependency guidance appears in both step 2 and Translation Rules — efficient with some tightening possible, above anchor 3 but short of anchor 5's 'every token earns its place'.	4 / 5
Actionability	Guidance names exact constructs ('Body[...]', "@modify(status_code=HTTPStatus.NO_CONTENT)", "include((router.urls, 'app_name'), namespace='...')") and exact commands ('uv run python manage.py runserver'), but the body itself contains no complete executable example — fragments like 'ResponseSpec(..., headers={...})' are pseudocode-ish with real code deferred to references, fitting anchor 4 rather than anchor 5's copy-paste-ready coverage.	4 / 5
Workflow Clarity	Eleven clearly sequenced steps include an explicit verification step (10) and a fidelity gate (11) with a blocking/non-blocking mismatch taxonomy and a feedback loop ('If blocking mismatches remain, keep iterating or ask the user... Do not claim completion until...'), plus a closing checklist — matching anchor 5.	5 / 5
Progressive Disclosure	Three one-level-deep references (framework-patterns.md, project-map.md, spec-fidelity.md — all present on disk) are clearly signaled with when-to-read conditions in the Overview, but the ~169-line body inlines substantial translation-rule and fidelity-gate detail that could live in those reference files, fitting anchor 4 rather than anchor 5's clean overview split.	4 / 5
	Total	17 / 20 Passed

Description

88%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.

A strong description that explicitly states concrete capabilities, use conditions, and trigger phrases in third person. Its only weaknesses are a few missing natural synonyms and slightly broad triggers that could overlap with general Django scaffolding skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete outputs — 'typed DTOs, controllers, routers, Django URL wiring, and minimal tests' — giving comprehensive, specific coverage of what the skill produces; anchor 4's 'minor gaps in coverage' is not evident.	5 / 5
Completeness	It explicitly answers both what ('Generate django-modern-rest transport-layer skeletons from OpenAPI 3.1+ specs') and when ('Use when Codex needs to...', 'Trigger on requests to scaffold APIs, bootstrap apps, or map OpenAPI operations...') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'scaffold APIs', 'bootstrap apps', and 'OpenAPI file, URL, or pasted document' are present, but common synonyms users might say (e.g. 'swagger', 'API spec', 'REST endpoints') are missing, matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	The django-modern-rest + OpenAPI niche is clear, but the broad triggers 'scaffold APIs' and 'bootstrap apps' create minor overlap risk with generic Django scaffolding skills, fitting anchor 4 ('mostly distinct; minor overlap risk') better than anchor 5's 'minimal conflict risk'.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: wemake-services/django-modern-rest
Path: .agents/skills/dmr-openapi-skeleton/SKILL.md
Commit: c1de4a6

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