6 Claude Workflows Every Knowledge Worker Should Set Up This Week

Most people use Claude for one-off tasks — answer a question, draft a paragraph, summarise a document. The real time savings come from configuring Claude to handle recurring workflows: tasks you do every week that follow a consistent pattern. Once properly configured, these six workflows can save three to five hours per week for a typical knowledge worker.

Why should you build workflow Skills instead of using one-off prompts?

A one-off prompt works once and disappears. The next time you need the same output, you start from scratch — re-explaining the format, the audience, the conventions. A workflow Skill persists. It loads automatically when Claude detects the matching task. It applies your format, voice, and audience preferences every time without being asked. The difference is the gap between asking a new temp to write your meeting notes versus having a trained assistant who already knows exactly how you want them.

Each workflow Skill requires four components: a clear output description (what the finished product looks like), format and structure rules (headers, sections, length), audience adaptation requirements (who reads this and what they expect), and examples of good output. The investment is fifteen to thirty minutes per workflow. The return is every instance of that task handled to your standards automatically.

How should you set up a meeting notes workflow in Claude?

Meeting notes are the highest-value workflow to automate because they happen frequently, follow a predictable format, and consume disproportionate time relative to their complexity. A well-built meeting notes Skill encodes your specific format: header structure, how action items are formatted, attendee listing conventions, decision logging format, and distribution list preferences.

The Skill should also specify what to exclude — tangential discussions, repeated context, social pleasantries — and how to handle ambiguity in the source material. Once configured, you paste raw meeting notes or a transcript and receive a properly structured document in your format. Five minutes instead of twenty.

How do you configure Claude for email drafting?

Email drafting is where voice consistency matters most, because emails go directly to other people and represent you personally. Build a Skill encoding your email voice by recipient type: the tone you use with clients versus colleagues versus leadership. Include sign-off conventions, greeting patterns, and the structural differences between a quick update, a formal request, and a difficult conversation.

The most effective email Skills include conditional rules. For example: "If the recipient is a client, open with context about their project. If the recipient is internal leadership, lead with the ask and follow with justification. If the email is a follow-up, reference the previous exchange date." These conditionals eliminate the need to re-explain context for every email.

What is the best way to automate status updates with Claude?

Status updates are the workflow most likely to be done inconsistently because they feel administrative rather than creative. Yet inconsistent status updates create confusion and erode stakeholder trust. Encode your organisation's format — RAG rated, structured by workstream, grouped by priority, whatever the template requires.

Feed Claude your raw notes for the period — bullet points, Slack messages, task completions — and the Skill handles the transformation into a properly structured update. The Skill should know your organisation's conventions for risk flagging, escalation language, and how to frame delays constructively.

How should you set up weekly planning and meeting prep workflows?

Weekly planning and meeting preparation are both compilation tasks — gathering information from multiple sources and structuring it for a specific purpose. A planning Skill runs your start-of-week and end-of-week routines: what was accomplished, what carries forward, what the priorities are for the coming week, and what deadlines are approaching. This creates accountability and reduces the cognitive load of context-switching on Monday morning.

Meeting prep is similar but audience-specific. Before important meetings, the Skill compiles attendee context, agenda items, talking points, key decisions needed, and relevant background from previous meetings. Structured compilation is exactly what Claude excels at — the skill just needs to know your specific format and level of detail.

How do you build an executive summary workflow?

Executive summaries require a different skill from the others because the audience has different expectations. Leadership wants conclusions first, supporting evidence second, and granular detail only when requested. A well-built executive summary Skill knows your specific leadership audience, the appropriate level of detail for each type of communication, and the framing your organisation's culture expects.

The Skill should encode rules about length (executives rarely read past one page), structure (lead with the recommendation, not the analysis), and tone (confident and direct, acknowledging uncertainty only where material). If you produce executive summaries for different audiences — a board, a steering committee, a project sponsor — build conditional rules for each.

How do you get started building these workflows?

Start with the workflow you do most frequently and find most tedious. Build one Skill, use it for a week, and refine based on what works and what needs adjustment. Then add the next. Most people find their optimal setup is three to six well-built workflow Skills.

Start with our complete setup guide to get the foundation right, then layer in workflow Skills. Before building workflows, make sure your writing voice is configured — it determines how every workflow output reads.

MyOS includes all six as configurable workflow modules. The onboarding asks the relevant questions and generates the skill files. Fifteen minutes for the full set.

For the broader system these workflows plug into, see our guide on building a personalised AI system. If you are getting inconsistent results from your workflows, persistent Skills are usually the fix. And if you are switching from ChatGPT, our migration guide covers how to bring your workflow context across.