Django testing strategies with pytest-django, TDD methodology, factory_boy, mocking, coverage, and testing Django REST Framework APIs.
56
66%
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 ./docs/ja-JP/skills/django-tdd/SKILL.mdSecurity
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 includes literal passwords and payment tokens (e.g., 'testpass123', 'adminpass123', 'tok_visa') in code examples and fixtures, which the LLM would reproduce verbatim in generated output, posing an exfiltration risk.
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 a payment gateway API (Stripe) and shows usage of stripe.Charge.create in payment-related tests (mocking a real payment gateway). This is a specific payment integration rather than a generic tool, so it meets the criterion for Direct Financial Execution capability even though shown within tests/mocks.
dfbf946
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.