Workflow setup skill

Download the skill (.zip) Read it first

Add it to the AI assistant or agent your team uses, start a chat and say “Set up my workflow.” It asks one question at a time, connects what it needs, and leaves your team with a skill that runs your own brief-to-email flow.

What it does

1. Learns how you work

   Where requests come from (a project tool, a brief you attach or paste, or your team’s own website), how you spot one that’s ready, who writes the copy, which template you start from, who hears when a draft is ready and how review edits come back. It reads the real projects and statuses from your tools instead of asking you to type them.

2. Connects your tools

   Stensul first, then where requests come from: your project tool (Adobe Workfront, Asana, Wrike, Jira, Monday and others), a brief you attach or paste, or pages on your own website. Then where brand files live, and Slack, Teams or email for notifications. When a step needs an admin, it writes the message for you to send.

3. Writes your team its own skill

   A <team>-brief-to-email skill with your sources, template, naming, notifications and rules built in. Next time you just ask: “What emails do we need to build?”

4. Builds your first email

   It runs your new skill on a real brief and builds a draft in Stensul. Anything you’d change goes back into your skill as a rule.

If your assistant can run scheduled tasks, it can set one up at the end that checks for new requests every weekday morning, or every hour in work hours, and has drafts waiting, applies review edits and tells the right people.

Who it’s for

You are	What you get
A marketer or email builder	The guided setup above. No technical knowledge needed.
IT, security or ops	Plain answers on sign-in, single sign-on, user provisioning, AI gateways, permissions and cost tracking, plus a review brief and a pilot plan.
A developer or platform team	Auth, gateways, what Stensul exposes and how to hand off from your own platform.

Add it to your assistant

The zip holds one folder with a standard SKILL.md file, so it works in any assistant or agent that supports skills. If yours doesn’t, paste the contents of SKILL.md into its custom instructions, project instructions or system prompt.

1. Download the zip

   Keep it zipped unless your tool asks for a folder.

2. Add it to your assistant

   In Claude, go to Customize > Skills, click +, then Create skill > Upload a skill, and choose the zip. You need a plan with Skills and code execution turned on; see Use skills in Claude. In Claude Code, unzip it into ~/.claude/skills/. In other assistants and agents, add it wherever they load skills from; their own docs have the steps.

3. Turn it on and start

   Open a new chat and say “Set up my workflow.”

In Claude, an owner on a Team or Enterprise plan can share the skill with the whole organization so nobody has to install it.

Before you start

• Drafts only. It never sends, schedules or approves an email. That stays in Stensul.
• It asks first. It asks before changing anything in your tools or posting a message during setup, and it never deletes anything.
• It acts as you. Each tool uses your own sign-in, so it can only see and do what you already can.
• Using your website as a source? Web search and web fetch need to be on in Claude (or your assistant’s equivalent). On Team and Enterprise plans, an owner may need to allow them.
• Tip on images. Image links, such as your website’s page images, go straight to Stensul with no upload step. Attached image files need one quick upload in a browser window, and the upload link expires after 15 minutes, so attach them all with the brief.

Updates

Download the zip again for the latest version. Changes are listed in the changelog.