Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
61
73%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
High
Do not use without reviewing
Fix and improve this skill with Tessl
tessl review fix ./skills/django-tdd/SKILL.mdThe canonical home for this skill is jbvc/django-tdd
Security
2 findings: 1 high severity, 1 medium severity. You should review these findings carefully before considering using this skill.
The skill handles credentials insecurely by requiring the agent to include secret values verbatim in its generated output. This exposes credentials in the agent’s context and conversation history, creating a risk of data exfiltration.
The skill prompt embeds multiple hard-coded passwords and a payment token (e.g. 'testpass123', 'adminpass123', 'tok_visa') directly in example code and tests, which would require an LLM to reproduce those secret-like values verbatim if it outputs or generates the same snippets.
The skill is specifically designed for direct financial operations, giving the agent the ability to move money or execute financial transactions — such as payment processing, cryptocurrency operations, banking integrations, or market order execution.
The skill documentation includes explicit references to the Stripe payment gateway API (e.g., patch('apps.payments.services.stripe'), mock_stripe.Charge.create, and payment tokens like 'tok_visa') used in payment processing tests. Stripe is a specific payment gateway API, so this skill includes explicit financial execution capabilities (even though the calls are mocked in tests).
754b8dd
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.