Seven Claude Code workflows: organise the work before repeating it

Inspect the two account-facing builds

The 22 March 2026 description reports bulk updates to 329 YouTube descriptions and a Chrome extension for opening Skool notifications. These are Luke’s recorded examples, not a recommended batch size or permission to alter another account. Both start with a specific annoyance and end with a change whose scope should be inspectable.

1. Follow the YouTube API workflow at 0:15 and identify the exact videos and description changes intended for your own task.
2. Preserve the original metadata and review a small proposed change before applying a wider batch.
3. For the notification extension at 4:47, define which notifications it should open and inspect its behaviour on a small set rather than assuming every new tab is relevant.

Keep measurement and scheduling distinct

CTA analysis with short.io starts at 7:21. Scheduling through cron jobs follows at 14:53, with the source explaining that Claude need not be running. A tracked link supplies observations; a recurring job supplies a trigger. Neither establishes that the generated report is complete or that clicks became meaningful conversions.

1. Match tracked links to the actual video and CTA before comparing performance.
2. Record the reporting period and distinguish clicks from any outcome that was not measured.
3. For a scheduled task, define the input, timing and expected output, then inspect an actual run and its destination.

Use email context before accepting a draft

The MCP email workflow begins at 18:28. Luke reports replying to 70 emails in 30 minutes, but that is his historical workload example, not a quality or speed guarantee. Drafting, choosing a recipient and sending are separate decisions, especially when a message depends on earlier correspondence.

1. Inspect the exact thread and relevant prior messages before asking for a reply.
2. Review the complete draft, recipient and attachments before any send step.
3. Keep unresolved questions visible rather than letting a fluent draft silently decide them.

Review local conversions and cleanup separately

File conversion begins at 23:43 and deleting or organising files at 25:56. The description stresses local conversion without uploading. A converted file needs an opening check; a duplicate-cleanup proposal needs evidence that the files are genuinely redundant. Those checks protect different kinds of work.

1. Choose a known source, retain its original and open the converted file to check content and usability.
2. For cleanup, inspect the proposed file list and compare contents before treating similar filenames as duplicates.
3. Start with a small recoverable operation and verify the resulting folder structure before repeating it more widely.

The takeaway

The shared method is explicit scope and an inspected result. Account changes, outbound messages and file deletion each need their own concrete review.