How to Build an Evergreen Tweet Library

Start with jobs, not with your best posts

Every library post holds a slot because of the job it does, so define the jobs before you choose a single post. The four buckets above cover most accounts: teaching shows competence, proof makes the competence believable, invitations give interested readers somewhere to go, and questions open conversations your other posts cannot start. A library built only of teaching posts reads as a lecture; one built only of invitations reads as advertising.

Write the bucket definitions in your own terms before selecting anything. A coach's teach bucket holds short frameworks; a shop's prove bucket holds making-of notes and care instructions. The definitions matter because they make admission decidable: instead of asking 'is this a good post?' you ask 'does it do one of these four jobs, and is that bucket short?'

• Teach: a self-contained lesson, tip, or correction of a common mistake
• Prove: evidence you know the work — a process, an example, a before-and-after explained
• Invite: a clear next step — read, download, reply, book, buy — stated plainly
• Question: a genuine question your readers can answer from their own experience

Admission criteria: what earns a library slot

Admission is deliberately strict, because every admitted post will speak for you repeatedly. The truth test removes anything riding on a moment: no launch-week excitement, no 'new' claims that will quietly expire. The voice test removes posts from an earlier positioning — a library that keeps repeating who you used to be works against the account you are building now. If a post fails a test but the idea is strong, rewrite it until it passes; the rewrite, not the original, is what enters.

The clarity test is the one people skip. A post that needed a follow-up explanation when it first published will need one every cycle, and the library has no follow-ups scheduled. Prefer posts that landed cleanly the first time — readers understood them, answered the actual question, or repeated the point back correctly. That history is evidence the wording works without you standing next to it — precisely the condition a library post lives under.

• Still true with no date, season, or news context attached
• Fully understandable alone, with no reference to an earlier post
• Written in the voice and for the offer you have now, not last year
• Clear on first reading when it originally published — readers got it without explanation
• Covers ground no existing library post already covers

A small worked example: a twelve-post starter library

Imagine a small library for an independent consultant. The teach bucket holds four posts: the three-line version of her core framework, a common mistake she corrects in client work, a short checklist readers can run themselves, and a definition post that reframes a term her field uses sloppily. None mentions a date, a client result, or a current event, so all four can cycle for a long time with only wording changes.

The prove bucket holds three: a walk-through of how she runs a first working session, an annotated example of a deliverable with identifying details removed, and a post explaining a decision she makes differently from common practice — described as reasoning, not as a claim about outcomes. Two invite posts point to her introductory call and her short guide. Two question posts ask about the reader's own process and tools. Twelve posts, four jobs, no filler — and every slot can explain itself.

Spacing and variation rules that keep the library fresh

A library post should return after weeks, not days, and the buckets should rotate so two invitations never land back to back. Space cycles widely enough that a regular follower encounters a repeat as a signature idea restated, not as last Tuesday's post again. Never run two posts making the same point in the same week, even if both are due: doubling a point reads as running out of things to say.

Variation is the second half of freshness. When a post returns, give it a genuinely new expression — a different opening line, a different example angle, the point made as a question instead of a statement — while keeping the claim itself stable. AutoTweet is built for exactly this discipline: recurring posts held as library entries with their variations together, on wide cycles you set once. Pro at $29/mo keeps the buckets, spacing, and variants organised as one maintained collection instead of a pile of separate scheduled posts you have to police by memory.

Maintain the library like a collection, not a loop

A finished library is the start of a maintenance habit, not the end of the work. New posts earn admission the same way the first twelve did — by passing the tests and filling a bucket that is short — never by being recent or by being yours. When a bucket grows heavy, a new admission should displace the weakest post already holding that job, so the library stays small enough to read end to end in one sitting.

Review the whole library on a regular pass: check each post against your current offer and voice, refresh dated wording, and retire posts whose job your account no longer needs done. That exit decision matters as much as admission. Keep the library small and current, and the cycle becomes an asset you govern instead of a loop you hope nobody notices.