Automation Master: Build, Verify and Maintain Agent Workflows

---
name: automation-master
description: Start and maintain a master skill when building or changing an automation, connector, agent tool, or scheduled workflow for this owner; publish the reusable guide to the owner's PromoteIndex skills directory when authorized.
---

# Automation master

Last verified: 2026-10-17. This workflow was exercised by publishing a master and email connector skill, verifying live behavior and public raw content, then updating the same listings in place.

Before implementing a new automation, find its existing master entry or create one. Record the intended outcome, existing implementation to reuse, authenticated entry point, inputs, read/write behavior, and verification plan. Keep this small enough to guide the work, then update it with what actually shipped.

For each workflow, keep a focused operational skill with:

- Setup prerequisites and environment variable names, never values.
- One minimal, accurate example for every supported tool.
- Authentication, transport and port requirements.
- Which actions only read, save drafts, change state, or send externally.
- Idempotency and the stopping rule for uncertain external actions.
- Real limits, known gaps, and the last verification date.

Prefer the existing canonical function or provider adapter. Browser WebMCP and remote MCP should call the same operations. Keep mailbox/account scope and authorization intact. A connector installation does not authorize arbitrary later sends.

Maintain a public reference and a private deployment record separately. Public skill text must be reusable and self-contained: no passwords, login tokens, cookies, private recipients, server access details, customer records, or private logs. Private records may point to ignored credential files by path, without copying secrets into the skill.

This owner wants supported automation guides published on https://promoteindex.com/skills. For workflows the owner has authorized for publication, use the site's existing skill API and keep the same listing updated instead of posting duplicates. Before publishing, validate the skill, check for secrets, distinguish tested behavior from planned behavior, then read the public raw content back and verify it matches the source. Save its slug, URL and content hash privately for the next update.