InnerVault

Your cart

Your cart is empty. Add a skill and it waits here. See skills you own

Subtotal$0.00

One payment, secure checkout by Whop. Prices in USD.

My skills

Master Claude: Your AI-Powered Work Assistant / Claude Code and workflows

Building useful workflows

About 12 minutes

A workflow is a task you do the same way each time, with Claude doing the repetitive parts and you doing the judgement. This lesson shows how to design one and which Claude features help.

Step 1: Pick a task worth systemising

Good candidates are tasks that:

  • happen weekly or more often,
  • follow roughly the same steps each time,
  • have a clear "good enough" standard.

Examples: weekly client update emails, turning meeting notes into action lists, writing product listings from supplier sheets.

Step 2: Write the steps down

Before involving Claude, write the steps you follow today. For a weekly client update:

  1. Collect what was done this week.
  2. Note what is next.
  3. Flag any blockers or decisions needed from the client.
  4. Write the email.
  5. Check it and send.

Step 3: Split into a chain of prompts

Anthropic's guide recommends chaining complex tasks: one clear step per prompt, with the output of one feeding the next. Each step is easier to check.

Prompt A, extract:

<notes>
[paste this week's rough notes]
</notes>

From the notes, list: (1) work completed, (2) work planned next week, (3) blockers or decisions needed from the client. Use only what is in the notes. If a section has nothing, write "none".

Check the list. Fix anything wrong.

Prompt B, draft:

Using the corrected list above, write the weekly update email following the project instructions. Put decisions needed from the client at the top in bold.

Prompt C, check:

Check the email against the list. Name anything in the email that is not in the list, and anything in the list that is missing from the email.

Step 4: Put it in a Project

Create a Project for the workflow (Lesson 3). Put the three prompts in a knowledge file called "Workflow steps", plus the instructions and examples. Each week you open the Project and run A, B, C.

Step 5: Connect your tools (optional)

Connectors let Claude read from other services. As checked on 2026-11-18, the Gmail, Google Calendar and Google Drive connectors are available to all users on Claude and Claude Desktop.

  1. Ask Claude a question that needs your Gmail, Calendar or Drive data.
  2. Claude sends you to Google to sign in and approve access.
  3. In a chat, click +, hover over Connectors, and switch individual connectors on or off.

On Team and Enterprise plans, an owner must enable the connectors for the organisation first.

Look in my Google Drive for the document called "Week 46 notes" and run step A of the workflow on it.

Only connect accounts you are comfortable letting Claude read. Switch connectors off in chats that do not need them.

Step 6: Package it as a skill (optional)

Skills give Claude packaged instructions and workflows it can use when they fit your request. As checked on 2026-11-18:

  • Skills are available on Free, Pro, Max, Ultra, Team and Enterprise.
  • They need code execution and file creation turned on (Settings > Capabilities).
  • You manage them at Customize > Skills. To add your own, click +, then + Create skill, then Upload a skill, and upload a ZIP of a skill folder in the required structure (see the help article "Use skills in Claude").

For most people, a well-built Project is enough. Consider a skill once a workflow is stable and you use it across many chats.

Step 7: Measure it honestly

Keep a short log for four weeks:

  • time spent before and after,
  • number of corrections you had to make,
  • any errors that reached the client.

If the corrections are not falling, improve the prompts or instructions. If errors reach clients, add a check step.

Common mistakes

  • Automating a process you never defined. Write the steps first.
  • One giant prompt that does everything and is impossible to debug.
  • Removing the human check because the first few runs looked fine.
  • Connecting every account "just in case".

Exercise

  1. Choose one weekly task and write its current steps.
  2. Turn it into a chain of at least three prompts: extract, draft, check.
  3. Put the chain in a Project and run it on real material.
  4. Start the four-week log.