elder

Audit email templates for rendering, accessibility, deliverability, and templating violations.

2|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/ppryde/pip-skills --skill elder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: elder
Source: https://github.com/ppryde/pip-skills/tree/main/plugins/email-absolution/skills/elder
Command: npx skills add https://github.com/ppryde/pip-skills --skill elder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Elder automates thorough audits of email templates and codebases to ensure rendering correctness, accessibility compliance, deliverability readiness, and templating integrity across ESPs and templating stacks.

Core Features & Use Cases

  • Mode-aware auditing across changed-files, full project scans, single-file checks, interactive sessions, and doc-mode outputs.
  • Doctrine-driven evaluation that loads core and per-language rules to enforce rendering, HTML/CSS discipline, content UX, accessibility, and deliverability standards.
  • Config-driven scope and reporting that respects .email-absolution/config.yml settings (ESP, templating, rendering targets) and produces structured findings with actionable guidance.
  • Doc-mode output saves rich Markdown reports under docs/emails/audits/ for traceability and sharing.

Quick Start

Run /email-absolution:elder in Claude to begin auditing your configured email templates.

Frequently Asked Questions about elder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit email templates for rendering and deliverability issues?

Email template audits check rendering, accessibility, deliverability, and templating violations by applying a config-driven, multi-phase rule workflow to configured email paths and generating structured findings with actionable guidance.

What is doctrine-driven email evaluation and how does it work?

Doctrine-driven email evaluation loads core and per-language rules to enforce HTML/CSS discipline, content UX, accessibility, and deliverability standards across ESPs and templating stacks during the audit workflow.

Can I run an email accessibility and deliverability audit on only the changed files?

Changed-files auditing is supported alongside full project scans, single-file checks, interactive sessions, and doc-mode outputs, allowing you to evaluate email templates selectively without scanning the entire codebase.

Do I need a specific configuration file to lint email templates across different ESPs?

A `.email-absolution/config.yml` file configures ESP, templating, and rendering target settings, which drives the audit scope and reporting logic for your email templates.

What's the best way to generate shareable reports for email rendering and accessibility checks?

Doc-mode audits save rich Markdown reports under `docs/emails/audits/` to provide traceability and easy sharing of email rendering, accessibility, and deliverability findings.

Why does my email template audit report templating violations across different rendering targets?

Templating violations occur when email templates break HTML/CSS discipline or content UX standards defined by the configured ESP and rendering target doctrines loaded during the multi-phase audit workflow.