jbvc/django-verification
Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.
69
69%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Risky
Do not use without reviewing
Quality
Discovery
67%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 effectively communicates a specific Django verification workflow with concrete actions, making it easy to understand what the skill does. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude more reliably select this skill. The trigger terms are decent but could include more natural user phrasings.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to verify a Django project before merging a PR, releasing, or deploying.'
Include additional natural trigger terms users might say, such as 'pre-commit checks', 'CI checks', 'ready to deploy', 'validate Django project', or 'pre-merge verification'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: migrations, linting, tests with coverage, security scans, and deployment readiness checks. These are clearly defined verification steps. | 3 / 3 |
Completeness | The 'what' is well-covered (verification loop with specific checks), and there's an implicit 'when' ('before release or PR'), but there's no explicit 'Use when...' clause with trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps this at 2. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'Django', 'migrations', 'linting', 'tests', 'coverage', 'security scans', 'PR', and 'release', but misses common user phrasings like 'check my code', 'pre-commit', 'CI pipeline', or 'ready to deploy'. Some terms are natural but coverage of variations is incomplete. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Django projects with a specific verification/pre-release workflow combining migrations, linting, tests, security, and deployment readiness. This combination is distinctive and unlikely to conflict with individual linting, testing, or security skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
55%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with excellent executable commands and a clear multi-phase workflow with validation checkpoints. However, it is severely bloated—much of the content (CI config, logging tests, static asset checks, basic git commands) is either unnecessary for Claude or should be split into separate reference files. The monolithic structure undermines its usability despite the quality of individual sections.
Suggestions
Reduce to ~100 lines by extracting the CI example, output template, and per-phase detailed commands into separate reference files (e.g., CI.md, OUTPUT_TEMPLATE.md, PHASES.md) and linking to them from the main skill.
Remove phases that cover things Claude already knows how to do (checking Python version, running git diff, tailing log files) or collapse them into single-line entries in the quick reference table.
Cut explanatory text like 'Common issues' lists and the final 'Remember' note—Claude doesn't need reminders about manual code review.
Consolidate the pre-deployment checklist and the output template into a single verification summary section to reduce redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~350+ lines with 12 phases, many of which cover things Claude already knows (how to run git diff, how to check Python version, how to tail log files). The CI example, logging tests, and static asset checks add significant bloat. Much of this could be condensed to a quick-reference table with phase descriptions. | 1 / 3 |
Actionability | Every phase includes concrete, executable bash commands and Python snippets that are copy-paste ready. Coverage targets are specific with a clear table, and the output template shows exactly what the report should look like. | 3 / 3 |
Workflow Clarity | The 12 phases are clearly sequenced with explicit stop-and-fix gates (e.g., 'If environment is misconfigured, stop and fix'). The output template serves as a validation checkpoint, and the pre-deployment checklist provides a final verification loop. The recommendation section shows error recovery flow. | 3 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. The CI example, output template, and detailed per-phase commands could easily be split into separate reference files. Everything is inlined, making the skill overwhelming to consume in a single SKILL.md. | 1 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents