Implements transactional emails with Action Mailer and TDD. Use when creating email templates, notification emails, password resets, email previews, or when user mentions mailer, email, notifications, or transactional emails.
Install with Tessl CLI
npx tessl i github:fernandezbaptiste/rails_ai_agents --skill action-mailer-patterns89
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
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 well-crafted skill description that excels across all dimensions. It uses third person voice, lists specific capabilities (Action Mailer, TDD, various email types), includes an explicit 'Use when...' clause with comprehensive trigger terms, and carves out a clear niche in Rails email functionality that distinguishes it from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'transactional emails', 'Action Mailer', 'TDD', 'email templates', 'notification emails', 'password resets', 'email previews'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Implements transactional emails with Action Mailer and TDD') and when ('Use when creating email templates, notification emails, password resets, email previews, or when user mentions mailer, email, notifications, or transactional emails'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'mailer', 'email', 'notifications', 'transactional emails', 'password resets', 'email templates', 'email previews'. These match how developers naturally describe email-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on Rails Action Mailer and email functionality. The combination of 'Action Mailer', 'TDD', and specific email types creates a distinct trigger profile unlikely to conflict with general coding or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable skill with excellent executable examples and clear TDD workflow. The main weaknesses are moderate verbosity (explaining Rails conventions Claude knows) and being a single large file rather than using progressive disclosure to separate core patterns from advanced topics.
Suggestions
Remove or condense the Overview section - Claude knows what Action Mailer does; jump straight to Quick Start
Split advanced topics (attachments, bulk emails, i18n, callbacks) into a separate ADVANCED_MAILER.md file and reference it
Remove the Project Structure section - Rails conventions are well-known and this adds 15+ lines of minimal value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity. The overview section explains basic concepts Claude knows (what Action Mailer handles), and some sections like the project structure could be trimmed since Rails conventions are well-known. | 2 / 3 |
Actionability | Excellent executable code throughout - generator commands, complete mailer specs, full mailer implementations, templates, and previews are all copy-paste ready. Every section provides concrete, working examples. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit checklist (RED -> GREEN progression). The workflow section provides numbered steps, and the final checklist serves as validation. The progression from spec to implementation to preview is well-sequenced. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic document (~350 lines) that could benefit from splitting advanced topics (attachments, bulk emails, i18n) into separate reference files. No external file references are provided. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (537 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
Table of Contents
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.