A social media workflow you can set up this week
This is the social media example from today's session, written out step by step. Each step adds one piece, and each piece moves the work one rung up the trust ladder. The ladder runs from L0 suggest, through L1 draft, L2 act internally and L3 act externally with approval, to L4 act and report. Start at step a and stop at the step where you would still want to check every post yourself.
// the examples use a neighborhood bakery as an illustration. Swap in your own business, and copy any prompt with its button.
- L0 · Suggesta Start with three prompts
- L1 · Draftb Save your rules as a skill
- L2 · Act internallyc Give it a project with the brief d Connect the inbox, drive and scheduler
- L3 · Act externally, with approvale Schedule the weekly run
- L4 · Act and reportf Build context across the business g Share it with the team h Log every decision and feed it back
Start with three prompts
Open Claude or ChatGPT and paste these one at a time. Replace the brackets with your own details, and paste two or three of your past posts where it asks, because that is how it picks up your voice.
You still write the final version and post it yourself. The assistant is doing what a sharp friend would do over coffee.
I run [business], a [what you do] in [neighborhood or city]. Most of my customers are [who buys]. Here are three posts that did well for us: [paste them] Give me three ideas for this week's post about [topic]. For each one, write the opening line and say which customer it is for.
Turn idea [number] into an Instagram caption under 60 words with one call to action, and a LinkedIn post under 150 words in the first person. Match the voice in the posts above. Do not invent prices, dates or claims; if you need one, ask me.
Read both drafts as a customer who has never heard of us. Tell me what is unclear, which line sounds like a machine wrote it, and the one change that would make you stop scrolling.
// Works the same in Claude and ChatGPT, on the free plans too.
Save your rules as a skill
After a few weeks you will notice you correct the same things: too long, too many hashtags, a made-up price. Write those rules down once instead of retyping them.
In Claude, a skill is a short instruction file it loads whenever the task comes up. You can ask Claude to write the skill with you from your corrections.
--- name: weekly-social-post description: Use when drafting social posts for the bakery. --- Read decisions/decision-log.md first and follow it. Voice: warm and specific. Name the bread and the baker. Instagram: under 60 words, one call to action. LinkedIn: under 150 words, first person. Never invent prices, dates or opening hours. Ask. Two hashtags at most. No staff photos without their OK. Before you hand back a draft, compare it with the posts in voice-examples.md and list anything you guessed.
// Claude: every plan can create custom skills. ChatGPT: put the same rules in a custom GPT or in a project's instructions.
Give it a project with the brief
A project keeps the instructions, files and past chats for one piece of work together, so you stop pasting the same background into every chat.
Put in who you are, who buys, what you sell, the posts that worked and the month's calendar. This is what lets it act inside the business at L2, and the brief is the real work.
Use the weekly-social-post skill. Draft next week's posts from the October calendar, and ask before you use a price.
- brief.mdwho we are, who buys, what we sell
- voice-examples.mdsix posts that did well
- october-calendar.mdholidays, specials, closures
- what-worked.mdupdated every Monday
// Both Claude and ChatGPT have projects. Add the four files and paste the instructions.
Connect the inbox, drive and scheduler
Connectors let the assistant read from and write to the tools you already use. Connect the inbox so customer questions become post ideas, the drive so it can find photos, and your scheduler so drafts land in the queue.
Give it the right to draft, not to publish. Buffer's connector, for example, puts every post in the queue for you to approve before anything goes out.
- Gmailreadcustomer questions become post ideas
- Google Drivereadphotos and the brief
- Canvacreateimages from your templates
- Bufferdrafts onlyevery post waits in the queue for your OK
// Claude: connectors. ChatGPT: Settings, then Apps. Buffer's connector works with both, on every Buffer plan.
Schedule the weekly run
A scheduled task runs a prompt on a timer without you opening the app. Once a week it can read the replies and the inbox, draft the week into your scheduler and send you one summary.
Your job shrinks to one sitting: read the summary, fix what is off, approve the week.
Read last week's replies and any customer questions in the inbox, and update what-worked.md. Draft this week's four posts into Buffer as drafts with the weekly-social-post skill. Send me one summary that lists anything you guessed.
// ChatGPT: the Scheduled section, on every plan with a cap on active tasks. Claude: scheduled tasks in Cowork, on Pro, Max, Team and Enterprise.
Build context across the business
The best posts pull from outside marketing: the price from the menu, the wholesale question from the inbox, the closure from the calendar. Keep one folder for each part of the business.
The README matters most. It says what lives where and who keeps each file current, because a brief nobody updates quietly goes stale.
bakery-context/
├── README.md (who updates what)
├── marketing/
│ ├── brief.md
│ ├── voice-examples.md
│ └── what-worked.md
├── sales/
│ ├── offers.md
│ └── questions-from-the-inbox.md
├── operations/
│ ├── menu-and-prices.md
│ └── hours-and-closures.md
└── decisions/
└── decision-log.md// A shared drive folder works, and so do a project's files.
Share it with the team
When the owner, the counter lead and a freelancer all work in one shared project, a correction any of them makes reaches everyone's next draft.
Decide up front who can change the brief and who approves a post. Approval stays with one person.
- OOwneredits the brief and approves every postCan edit
- CCounter leadadds the week's customer questionsCan edit
- FFreelance designerreads the brief before making imagesCan view
// ChatGPT: share a project with Chat or Edit access. Claude: project sharing on Team and Enterprise, with Can view or Can edit.
Log every decision and feed it back
Every time you approve, change or reject a post, write one line saying what you decided and why.
Make the log the first thing the skill reads. The assistant then stops repeating mistakes you already corrected, and the log becomes the record of how your business talks.
| Date | Decision | Why |
|---|---|---|
| Oct 6 | Post before 7 pm | evening posts got almost no replies |
| Oct 9 | Name the baker in the post | customers ask for Maria by name |
| Oct 13 | No discount posts on Saturdays | we sell out by noon anyway |
Read decisions/decision-log.md first and follow it.// A plain file is enough. Point the skill at it so it is read first.
Swap the post for customer onboarding, invoice generation or lead-to-cash, and the same eight steps apply.
If you haven't mapped your own workflow yet, the four questions from today are at silentintel.com/unstuck.