The issue is done and it's good, and the last step of the process is still copying it into an email tool by hand. We add one more step to the skill: after you approve the tightened draft, it pushes the issue to the connected email platform as a draft broadcast. Never scheduled, never sent. The step is written against "the connected email platform" rather than a specific tool, and we prove why that matters by pushing to Kit, then swapping the connection to Mimeo and pushing again with the same prompt. Same skill, different platform, nothing changed.
What's covered:
- Naming the last-mile friction: a finished draft that dead-ends in the repo
- Adding a push step to a skill that's already unpacked into steps
- Connecting an email platform through its MCP
- Pushing to Kit and verifying the draft in the dashboard
- Swapping to Mimeo with the same skill and the same prompt
- Writing skills that survive a tool switch
- The guardrail: the agent drafts, a human presses send