← All use cases

中文

Operations & admin · Claude in Chrome

Let a browser agent edit and move your Substack posts

Idea + starter prompt, not run by us yet

For: Newsletter writers who need to fix old posts or move content between publications

Three Substack jobs went to Claude in Chrome: edit a live post, migrate another post and insert a note. Claude studied the editor's structure, put the content in at the right spots, checked the email setting in the publish dialog and confirmed each result with screenshots. All three came out right. One accidental click on the comments setting was spotted and undone.

Steps

  1. Write each job as a clear prompt: which post, what to change, and what must stay the same.
  2. Try an edit on a draft or a test post first.
  3. Tell the agent to check delivery settings before publishing: email on or off, audience and comments. The migrated post had defaulted to paid-only with restricted comments.
  4. Ask for screenshots of the final result and look at them yourself.
  5. Publish only after you have confirmed the email setting.

Starter prompt

Starter prompt. Change the [brackets] first.

Trial first: do the edit on a draft copy, titled [TEST copy of post title], and never on the live post. If the job is a migration, move it into a new draft marked as a test.

Open my Substack editor for [post title]. I want you to [edit these paragraphs / copy the post from URL into a new draft]. Details: [what to change]. Tell me exactly what you plan to do before you change anything. Do not click anything you did not tell me about.

Stop and wait for my yes before publishing, and before any change to a live post. Before that, show me the settings for email, audience and comments. Showing me the finished draft is not permission to publish. Take a screenshot of the result. Never ask for my password.

Original post: priscasolutionsai.substack.com · found via agentusecases.ai. Written up in our own words. We haven't run it, so test it on made-up data first.