
jinja2
✓ Official★ 2,400by microsoft · part of microsoft/debugpy
Best practices for template rendering with Jinja2 including environments, filters, autoescaping, and security.
🔥🔥🔥🔥✓ VerifiedFreeQuick setup
🧰 Not standalone. This skill ships with microsoft/debugpy and only works together with that tool — install the tool first, then add this skill.
This is the playbook your agent receives when the skill activates — you don't need to read it to use the skill, but it's here to audit before installing.
name: jinja2 description: Best practices for template rendering with Jinja2 including environments, filters, autoescaping, and security.
Skill: Jinja2
Best practices for template rendering with Jinja2 including environments, filters, autoescaping, and security.
When to Use
Apply this skill when rendering templates with Jinja2 — HTML pages, emails, configuration files, and code generation.
Environment
- Create a
jinja2.Environment(loader=..., autoescape=...)once and reuse it. - Use
FileSystemLoaderfor file-based templates,PackageLoaderfor installed packages. - Enable
autoescape=Truefor HTML templates to prevent XSS.
Templates
- Use
{{ variable }}for output,{% if/for/block %}for control flow. - Use template inheritance (
{% extends 'base.html' %}) for layout reuse. - Define custom filters for reusable transformations.
Security
- Always enable
autoescape=Truewhen rendering HTML. - Use
SandboxedEnvironmentfor untrusted templates. - Never render user input as template code — only as template data.
- Use
|efilter explicitly when autoescape is off.
Pitfalls
- Don't use
Template(string)directly — it bypasses the environment's loader and settings. - Watch for undefined variable errors — use
undefined=StrictUndefinedduring development. - Avoid complex logic in templates — keep them focused on presentation.
Copy & paste — that's it
npx skills add https://github.com/microsoft/debugpy --skill jinja2Run this in your project — your agent picks the skill up automatically.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.