scribe

Generate doctrine-compliant email templates from a user brief.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating consistent, doctrine-compliant email templates from a brief or specification, reducing manual drafting time and ensuring adherence to organizational standards.

Core Features & Use Cases

  • Doctrine-driven generation: produces templates that conform to loaded doctrines for email structure and content.
  • Dynamic context loading: reads required configuration and doctrine files to tailor templates per stack.
  • Use Case: when given an order-confirmation brief, it generates a ready-to-send transactional email that follows the prescribed standards.

Quick Start

Provide a brief for an order-confirmation email and generate a doctrine-compliant template.

Frequently Asked Questions about scribe

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

FAQPage Schema
How do I generate transactional email templates from a brief?▼

To generate transactional email templates from a brief, provide a specification for emails like order confirmations or password resets to produce ready-to-send, doctrine-compliant HTML output instantly.

What are doctrine-compliant email templates and why use them?▼

Doctrine-compliant email templates are pre-configured outputs that enforce alignment with your organizational standards and stack settings, ensuring consistent structure and content while reducing manual drafting time.

Can I use this for order confirmations and shipping notices?▼

Yes, you can use this for transactional emails including order confirmations, shipping notices, welcomes, and password resets, generating ready-to-send templates tailored to your specific stack settings.

What's the best way to automate email template generation for multiple stacks?▼

The best way to automate email template generation across multiple stacks is to load configured doctrines and let the system dynamically select the correct templating pattern to produce stack-specific output.

Does generating email templates require manually coding HTML?▼

No, generating email templates does not require manually coding HTML, because the system reads required configuration and doctrine files to automatically produce a ready-to-send HTML template from your brief.