CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

improving-drf-endpoints

Use when editing, reviewing, or auditing DRF viewsets and serializers in PostHog. Triggers on files in posthog/api/, products/*/backend/api/, products/*/backend/presentation/, or any file importing rest_framework. Covers field typing, schema annotations, enum collision fixes, and OpenAPI spec quality — everything that flows downstream into generated TypeScript types and MCP tools.

65

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 dense, actionable audit guide with a clear workflow and concrete commands, weakened primarily by broken progressive disclosure — every detailed reference file it points to is absent from the bundle. Conciseness and validation coverage have minor room to improve.

Suggestions

Ship the four missing reference files (references/serializer-fields.md, viewset-annotations.md, quick-reference-table.md, common-anti-patterns.md) or inline their essential patterns so the deferred 'See ... for patterns and examples' links resolve.

Tighten the 'Why core discovers and calls the product' paragraph to a sentence or move it into a reference; the eager-registration rationale is design history that costs tokens without guiding the audit.

Add an explicit validate→fix→retry loop (e.g. 'run hogli build:openapi, fix any new unknown types, re-run') so the workflow has more than one validation checkpoint.

DimensionReasoningScore

Conciseness

Largely lean and assumes DRF/Django competence (no basic concept explanations), but the URL-routing rationale paragraph ('Why core discovers and calls the product...') over-explains design history that could be trimmed.

4 / 5

Actionability

Concrete and executable — specific decorators (@extend_schema, @validated_request), CLI commands ('hogli build:openapi', 'python manage.py find_enum_collisions'), and a complete routes.py snippet — but the before/after code pairs and detailed patterns are deferred to reference files that do not exist, leaving gaps.

4 / 5

Workflow Clarity

Clearly sequenced triage → serializer fields → viewset annotations with a decision flowchart and an explicit verify step in item 16, but only one validation checkpoint across the whole audit, so minor gaps remain.

4 / 5

Progressive Disclosure

Section structure is well-organized with one-level-deep, clearly signaled references, but all four referenced files (serializer-fields.md, viewset-annotations.md, quick-reference-table.md, common-anti-patterns.md) are missing from the bundle, so navigation is broken.

3 / 5

Total

15

/

20

Passed

Description

87%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, specific description that clearly states both capabilities and explicit trigger conditions scoped to PostHog's DRF stack. It is highly distinctive; the only weakness is slightly generic leading verbs and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete capabilities ('field typing, schema annotations, enum collision fixes, and OpenAPI spec quality'), but the leading verbs ('editing, reviewing, or auditing') are generic and routing/MCP coverage from the body is absent here, leaving minor gaps.

4 / 5

Completeness

Explicitly answers both 'what' ('Covers field typing, schema annotations, enum collision fixes, and OpenAPI spec quality') and 'when' ('Use when editing, reviewing, or auditing... Triggers on files in posthog/api/...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural phrases ('editing, reviewing, or auditing DRF viewsets and serializers') plus technical triggers ('rest_framework', exact file paths), but misses common synonyms/extensions a user might say (e.g. 'Django REST', 'OpenAPI schema').

4 / 5

Distinctiveness Conflict Risk

PostHog-scoped to DRF viewsets/serializers with exact path globs and a rest_framework import trigger — a clear niche with minimal conflict risk against other skills.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 5 missing, 1 suspicious

Warning

referenced_paths_exist

Referenced path issues: 5 missing

Warning

Total

14

/

16

Passed

Repository

PostHog/posthog

Path

.agents/skills/improving-drf-endpoints/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.