How to use Autopilot instructions to keep your voice consistent

Automation is wonderful right up until your feed starts sounding like a robot. If you let a tool turn your commits into posts, the real worry isn't whether it runs on time—it's whether the posts it writes sound like your team or like a generic press release. That's exactly the gap MarketMee's Autopilot closes with one small, easy-to-miss setting: the per-repository Instructions field.

This post walks through how to use those standing instructions to keep a consistent voice across every post Autopilot creates, without reviewing each one by hand.

Where Autopilot instructions live

Autopilot watches your GitHub repositories and automatically creates posts from new commits on a schedule you set. Each new post lands in your posting queue in the next open time slot. To get there:

1. Go to Autopilot in the sidebar.
2. Connect a GitHub account and select a repository.
3. Configure the repository's settings—including the Instructions field.

The Instructions field accepts up to 1,000 characters per repository. It's optional, but it's the single most important lever you have for controlling tone when nobody is reviewing posts before they go out. These are standing instructions: you write them once, and every run applies them until you change them.

What standing instructions are for

Think of the Instructions field as a short brief you hand to a writer who covers your product full-time. You're not describing a single post—you're describing how every post should read. The brief itself even suggests the shape of a good instruction: "Focus on the new billing dashboard and write for agency owners."

That one sentence is doing two jobs at once:

• Setting the audience — "write for agency owners" tells Autopilot who's reading, which changes vocabulary, examples, and what counts as a benefit.
• Setting the focus — "focus on the new billing dashboard" points attention at what matters this cycle, so a flurry of small refactors doesn't drown out the feature you actually want people to see.

Dial in your audience

Developers, founders, and product teams all ship code, but they announce it to very different people. Name your reader explicitly. A few patterns that work well inside 1,000 characters:

• "Write for non-technical founders evaluating our tool—lead with outcomes, not implementation."
• "Our audience is backend engineers; it's fine to use precise technical language."
• "Speak to agency owners who resell to their clients."

The more specific the reader, the more consistent the voice, because Autopilot isn't guessing who it's talking to on each run.

Lock in tone and phrasing

Voice is mostly tone plus a handful of word choices. Spend part of your 1,000 characters telling Autopilot how to sound:

• "Keep it plain and direct. No hype words like 'revolutionary' or 'game-changing.'"
• "Casual and a little playful—we're a small team and we sound like it."
• "Always call the product by name and never compare us to competitors."

Because these instructions apply to every run, your tenth automated post reads like your first. That's the whole point of using the field instead of fixing posts one at a time.

Pair instructions with your other Autopilot settings

Instructions shape the words, but a consistent voice also comes from consistent format. When you set up a repository in Autopilot, you also choose:

• Content: Images, Video, or Both.
• Video style (if Video is selected): Classic or Motion.
• Image style (if Images is selected): your preferred image and headline styles, which Autopilot rotates through so your feed stays varied but on-brand.
• Voice narration and Sound effects for videos (sound effects are available in Classic mode only).
• Check for new commits: a cadence of Every hour, Every 6 hours, Every 12 hours, Daily, or Weekly.
• Post to: which connected social accounts should receive the posts.

Your Instructions text and these format choices work together. If you tell Autopilot to "write for agency owners" and also pick the Feature Spotlight headline style, every post reinforces the same identity—same reader, same look, same tone.

One more detail worth knowing: during quiet weeks with no new commits, Autopilot finds an earlier commit worth talking about to keep your feed active. Your standing instructions apply to those posts too, so even the "we dug something up" posts stay on voice.

A simple workflow to get it right

You don't have to nail your instructions on the first try. Here's a low-risk way to tune them:

1. Write a first draft of your Instructions—audience, focus, tone, and any hard rules (words to avoid, product-name usage).
2. Toggle Autopilot on. The first run happens at the next scheduled time, or use Run now to trigger one immediately.
3. Open Recent runs to see which commits were picked up and which posts were made.
4. Read the generated posts. If the tone drifts, adjust the Instructions text and run again.
5. Because every post lands in your queue first (unless you've set it to publish immediately), you can still open a post from the Timeline and edit the words before it goes out.

That last point matters: standing instructions get you 90% of the way to a consistent voice automatically, and the queue gives you a safety net for the rest. Over a couple of cycles, you'll find the wording that makes Autopilot's posts indistinguishable from the ones you'd write yourself.

The payoff

The reason to invest a few minutes in the Instructions field is leverage. Every character you write there is applied to every future run, on every cadence, for that repository—no per-post effort required. You set the voice once, and MarketMee keeps it consistent while you stay heads-down in the code.

Ready to tune your own? Open Autopilot at marketmee.app, add a short standing brief to a repository, and let your commits start announcing themselves in your voice.