Creating workflows
Open Workflows → New workflow. Under the hood, workflows are stored as SKILL.md documents — a structured markdown format — but the editor lets you build them without touching the raw file.
Title and description — the title is how you'll recognize the workflow in the list. The description should say what it accomplishes ("Run a weekly competitor scan across the three closest competitors and summarize findings").
Steps — each step has a title and a description. The agent runs them in order. Good steps read like instructions to a competent teammate:
- Step 1: Pull this week's Google Ads spend — "Query Google Ads for the last 7 days. Group by campaign. Return total spend, impressions, and click-through rate."
- Step 2: Compare to last week — "Look at the previous 7 days for the same campaigns. Flag any campaign whose CTR dropped more than 20%."
- Step 3: Draft the summary — "Write a Slack-ready summary: top 3 wins, top 3 concerns, recommended next action."
Steps can each specify their own tool (e.g., browser) and skills if you want to nudge the agent.
Focus skills — at the workflow level, focus skills tell the agent which skills to lean on across every step. Typical entries are things like seo-research, copywriting, or social-scheduling.
Required integrations — if a workflow needs Google Ads data, list Google Ads as a required integration. The workflow won't run if the integration is missing — Magister will tell the user to connect it first.
Inputs — turn parts of your steps into variables with {{name}}