Email Template Design: a Tokeny case study

Prepare the inputs

Create a separate workspace in Tokeny, download and unpack the sample inputs, then select a model that supports tools. The sample uses synthetic data or the public sources named in the article.

product-brief.md

Download sample inputs

Send the task to Tokeny

The original task was executed in Chinese. Copying these instructions reproduces the same task; the results below include an English report.

设计活动邀请 HTML 邮件模板和纯文本备用版本，使用 table 布局与内联样式，提供取消订阅占位。仅本地预览，不发送邮件；说明尚未测试的客户端。

交付文件：email.html、email.txt。
验收要点：
- 邮件包含主题、主文案和行动入口
- 不使用 JavaScript
- 不把浏览器预览等同于全部邮件客户端兼容
这是使用合成演示输入或指定公开资料的真实操作案例。请先读取工作空间输入，再实际生成文件并自检。所有写入、脚本与临时服务限于当前工作空间；临时服务只监听 127.0.0.1，执行后关闭；不触达外部收件人、不发布、不付款、不更改系统设置，不调用子智能体。需要公开资料时可读取给定 URL。只启用完成任务必需的工具。另写 report.md（中文）和 report.en.md（英文），简洁、完整，包含输入、处理步骤、真实结果、检查方式和局限；失败或未验证部分如实记录，不能宣称成功。最终回复用中文列出产物、关键结果与待核实项。

The recorded run used an isolated demonstration workspace. Review the commands and file paths before approving operations in your own workspace.

What actually ran

The task was submitted through the Tokeny input box. An online model read the inputs and executed tools. This run covers the local sample task and its actual files. Results and checks are recorded below.

The actual Tokeny 1.7.8 session and files for Email Template Design. Open the image at full size.

A preview of the actual generated file included in the download.

Results and verification

Inputs

Read product-brief.md: the fictional product is Songguo Task Board for teams of 3–10 people, with task lists, assignees, due dates, and CSV export.
Brand color: #176B52. Contact: hello@example.test.
Read ENVIRONMENT.md: Windows, Tokeny 1.7.8; local Edge/Playwright environment notes were available.
No public sources or external URLs were used.

Processing

Wrote invitation copy with a subject, main message, event details, and a call to action based on the product input.
Generated email.html with table layout, inline styles, preview text, text links, and an unsubscribe placeholder; no JavaScript was added.
Generated email.txt as a plain-text fallback.
Performed static file checks for required content, structure, placeholders, and prohibited items.

Actual Results

Generated email.html and email.txt.
Generated this report and the Chinese version report.md.
Registration URL, date/time, meeting URL, and unsubscribe URL remain placeholders and must be replaced before sending.
No email was sent and no external recipient was contacted.

Checks

Read the generated files and verified the subject, main message, call to action, and unsubscribe placeholder.
Checked that the HTML contains no <script>, event-handler attributes, or JavaScript protocol.
Checked that the HTML uses role="presentation" table structure and inline style for the main visual styling.
Performed local file-level checks only; no temporary server was started and no browser automation preview was run.

Limitations and Open Checks

Not tested in Gmail, Outlook for Windows/Microsoft 365, Apple Mail, Yahoo Mail, iOS Mail, or Android Gmail.
Client-specific handling of CSS, links, preview text, fonts, dark mode, image policies, and long-line wrapping remains unverified.
Browser rendering or static checks must not be treated as proof of compatibility across all email clients.
Before sending, replace every placeholder and run real-client rendering and link checks.

Download and inspect the outputs

The archive contains the files created during this run. Use these checks when adapting the example to your own data.

Reconcile the reported results against the downloadable sample inputs.
Open the generated files and check the contents relevant to your task.
Review the limitations and any unverified steps in the report.

email.html · 4 KBemail.txt · 1 KBreport.md · 2 KBreport.en.md · 2 KB

Download actual outputs