Overview

At Zeabur, I designed and implemented an AI-assisted workflow for the monthly newsletter. I packaged the workflow as a reusable agent skill and documented the process in the internal wiki so colleagues could run it with their own agents.

My role Building the workflow and writing the operating instructions that supported its adoption by other team members.

The problem

A recurring newsletter needs a repeatable production process. For that process to be useful beyond its creator, colleagues also need a way to understand and run it themselves.

I treated the workflow and its documentation as parts of the same service: the first supports execution; the second makes that execution transferable.

From individual execution to shared use

  1. Build the workflow. I established an AI-assisted process for producing the monthly newsletter and packaged it as a reusable agent skill.
  2. Make the process explicit. I wrote the workflow into wiki-based standard operating procedures, providing a shared reference for how to run it.
  3. Enable colleagues to use it. Other team members used the documentation with their own agents and completed newsletter sends.

The handoff is between a person, a documented process and that person's agent. Colleagues can use the workflow through their own working setup, with the wiki providing the common operating reference.

Implementation and reusable skills

Newsletter repository showing the implementation structure
The repository brings the implementation, preview site and reusable skills together.
Reusable newsletter skills organised in the repository
The skills package recurring workflow steps for reuse by teammates with their own agents.

Newsletter preview

Newsletter preview interface showing the June 2026 issue and content ready for review
The newsletter preview brings the content together for review before sending.
Test newsletter received in an email inbox
A test delivery shows how the newsletter appears in an email inbox.

Outcome

The workflow was implemented and used by other team members to complete actual newsletter sends. This demonstrated adoption beyond my own use and made the process available for repeated team use.

Related work

Connecting self-service sponsorship codes with internal operations

Back to Projects