email-template
Skill0 starsChanged 8 days agoMITView on GitHub
Write or edit a reusable email template in ChatMaxima for bots and automations to send. Use when the user wants a welcome, confirmation, follow-up or notification email that a ChatMaxima bot sends, or wants to change the wording of one.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- adityareddy-dev/deskstudiotheir own version, first seen Oct 25, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- adityareddy-dev/deskstudio★ 43same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository8 other files it gives its agents.
- build-chatbotSkill
- chatmaxima-apiSkill
- chatmaximaSkill
- fix-chatbotSkill
- get-startedSkill
- inbox-triageSkill
- whatsapp-flowSkill
- whatsapp-templateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Keep it short and plain: one purpose per email, the key detail near the top, and one clear next step.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Email templates in ChatMaxima
Email templates need no approval and are ready as soon as they are saved. A bot sends one through a Send Email block.
Create one
list_email_templatesreturns the existing templates and the workspace's email accounts. A template belongs to one email account: ask the user which one if there are several. If there are none, the user has to connect an email account in ChatMaxima first.- Draft the subject and the HTML body. Use
{variables}with single braces for values filled in at send time, for example{customer_name}or{booking_date}. Use only variables the bot actually collects or stores. - Keep it short and plain: one purpose per email, the key detail near the top, and one clear next step.
- Show the draft to the user, then call
create_email_template. - To send it from a bot, add or update a Send Email block with
broadcast_type: "email_template"and the template'semail_template_alias(see thebuild-chatbotskill).
Edit one
get_email_templateto read the current subject and body.- For a small change, send
replaceedits toupdate_email_templateinstead of a whole new body. - Send Email blocks keep their own copy of the subject and body. After editing a template, update each block that uses it with
update_block, settingemail_template_aliasagain, or the bots keep sending the old wording.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

