postmark-templates

Use when creating, managing, or sending with Postmark server-side email templates — Handlebars syntax, layout inheritance, template validation, and cross-server pushing.

1.10x

Quality

86%

Does it follow best practices?

Impact

97%

1.10x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured skill with strong actionability and progressive disclosure. The main weaknesses are some redundancy between the body content and the Notes section, and the lack of explicit error recovery workflows for operations like template pushing and validation failures. Overall it serves as an effective reference for Postmark template operations.

Suggestions

Remove or significantly trim the 'Notes' section, as nearly all bullet points repeat information already presented in the body (template types, aliases, layout inheritance, validation).

Add an explicit feedback loop for template validation failures (e.g., 'If validation.AllContentIsValid is false, inspect validation.HtmlBody.ValidationErrors, fix issues, and re-validate').

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient but has some redundancy. The 'Notes' section at the end repeats information already covered in the body (e.g., template types, aliases vs IDs, layout inheritance, validation). The overview table and quick start are lean, but the repeated content costs tokens without adding value.	2 / 3
Actionability	Provides fully executable JavaScript code examples for both sending with templates and validating templates. The Handlebars syntax examples are concrete and copy-paste ready. API endpoints are clearly listed with methods and descriptions.	3 / 3
Workflow Clarity	The Quick Start provides a clear 4-step sequence, and validation is mentioned. However, there's no explicit feedback loop for error recovery (e.g., what to do if validation fails), and the workflow for cross-server pushing (staging → production) is only mentioned but not sequenced with validation checkpoints.	2 / 3
Progressive Disclosure	Excellent progressive disclosure with a clear overview in the main file and well-signaled one-level-deep references to handlebars-syntax.md, layout-templates.md, and template-api.md. Content is appropriately split between the overview and detailed reference files.	3 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong description that clearly identifies a specific niche (Postmark server-side email templates), lists concrete capabilities (Handlebars syntax, layout inheritance, template validation, cross-server pushing), and includes an explicit 'Use when' trigger clause. It uses proper third-person voice and is concise without being vague.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: creating, managing, sending, Handlebars syntax, layout inheritance, template validation, and cross-server pushing. These are distinct, concrete capabilities.	3 / 3
Completeness	Clearly answers both what (creating, managing, sending Postmark templates with Handlebars syntax, layout inheritance, validation, cross-server pushing) and when ('Use when creating, managing, or sending with Postmark server-side email templates'). The 'Use when...' clause is explicit.	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Postmark', 'email templates', 'Handlebars', 'layout inheritance', 'template validation', 'cross-server pushing', and 'server-side'. These cover the domain well with terms users would naturally use.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — 'Postmark' is a specific service, 'server-side email templates' with 'Handlebars syntax' and 'cross-server pushing' create a very clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: ActiveCampaign/postmark-skills
Commit: 73ea6bf

Reviewed: about 2 months ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.