Kit

Social Presence

Your cadence against your intention, and next week’s drafts in your own voice.

Consistency beats virality, and what kills consistency is losing track. This keeps two plain records: what you actually posted — when, where, what it was about — and what you were aiming for, in your own words: the platforms you post on, how often you meant to post on each, and the topics you keep coming back to. The first sweep reads your own recent posts on the platforms you have connected and fills the log from them; after that it runs each Monday, shows the week against your own intention rather than anyone else's numbers, and keeps a queue of drafts written from your notes in your voice. The ideas you have go in a bank, and the ones you give a day go on a calendar of what goes out when. Ask and Aster reworks a post of yours for each platform you use, or drafts a fresher bio or headline for you to paste. It never posts, never replies, never reacts, and never rates a post beyond what the platform itself reports — which for LinkedIn is nothing at all: LinkedIn hands back your posts and no engagement whatsoever, so those columns stay empty there and the board says so rather than guessing.

Try it free

1 agent, 1 routine, 1 dashboard, 3 datasets, 4 skills. Installing offers the first sweep on the same screen — connect, run it, and everything can be retimed or paused after.

PresenceExample data
X — this week against your intentionyour own rate, never a benchmark
X — 4 a week3 of 4
What you post aboutevery post on the log, by topic
Build logs18
Lessons11
Questions7
Links5
Drafts waiting for youwritten from your own notes, never posted

The retry loop, in the end

for X · from a note on Tuesday

What a week of red builds taught me

for LinkedIn · from the week notes

How do you keep a changelog honest?

for X · from a conversation on Thursday
Every postengagement where the platform reports it
The retry loop, in the endX · a build log34 likes
What a week of red builds taught meLinkedIn · a lesson learnednot reported
How do you keep a changelog honest?X · a question to the room21 likes
A good piece on writing less codeLinkedIn · a link with a commentnot reported

The crew

Aster

Keeps your posting steady against your own intention — and never posts, replies or reacts.

Steady, plain, unimpressed by numbers; keeps flowering week after week, and never picks up the megaphone for you.

What else it installs

Post logdataset

Everything you actually posted — when, where, what it was about, and the figures the platform itself reports.

Presence intentdataset

What you meant to do: where you post, how often you are aiming for, and the topics you keep to.

Post plandataset

Every post you have in mind: the ideas waiting in the bank, and the ones you have given a day.

Post captureskill

"Put out a thread about the retry loop this morning" — one sentence, and it is on the log.

Ideas and planskill

"I could write about the flaky test" goes in the bank; "put it on Thursday, for X" puts it on the plan.

Post draftsskill

Turns a note you already wrote into a post in your own voice — and stops at the draft, every time.

Profile refreshskill

A fresher bio, headline or About section, made from what you already say about yourself, for you to paste.

Presencedashboard

The week against your own intention, what you post about, what landed on X, what is planned, and the drafts waiting.

Presence sweeproutine

Mondays — reads back your own recent posts, refreshes what X reports, and shows the week against your own rate.

Runs mondays · 8am

How it works

The mechanics of this kit, plainly — what runs and when, where the data lands, and what you look at.

  • Presence sweep runs mondays · 8am and keeps the Presence dashboard fresh. Mondays — reads back your own recent posts, refreshes what X reports, and shows the week against your own rate.
  • What is captured lands in the Post log dataset, which lives at Data/Post Log in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Presence intent dataset, which lives at Data/Presence Intent in your vault — yours to open, search, and edit like any other file.
  • What is captured lands in the Post plan dataset, which lives at Data/Post Plan in your vault — yours to open, search, and edit like any other file.
  • The Presence dashboard reads from the dataset and shows, at a glance: linkedin — this week against your intention · x — this week against your intention · ideas and plan, by where each stands · what you post about · what landed on x · drafts waiting for you · what goes out when · your intentions, as you wrote them · every post · what this board can and cannot see.

The wiring, in one breath: Post capture writes to Post log · Presence sweep writes to Post log · Post capture writes to Presence intent · Post log shown by Presence · Presence intent shown by Presence · Presence kept fresh by Presence sweep · Presence sweep run by Aster · Aster holds Post capture · Aster holds Post drafts · Ideas and plan writes to Post plan · Post drafts updates Post plan · Post capture updates Post plan · Post plan shown by Presence · Presence sweep reads Post plan · Aster holds Ideas and plan · Aster holds Profile refresh.

Getting the most from it

A kit earns its place when it changes what you look at and what you say, not when it is installed. This is the rhythm that makes it pay.

  • Look at the board on Monday, after the Presence sweep has been through. The two cards at the top are the whole point: posts filed this week against the rate you set yourself. A week under it is information, not a telling-off — and if it happens three weeks running, the honest fix is usually to change the rate on the Presence intent record rather than to try harder.
  • Say a post the way you’d mention it to someone — "put out a thread about the retry loop this morning" — and Post capture files it with the day, the platform and the topic. That is how a talk, a newsletter or a post on a platform this kit cannot read gets onto the log at all, and it is the only way anything older than the last twenty posts arrives.
  • When a planned post goes out, say so. Post capture puts it on the Post log and, when it was on your plan, asks once and marks it posted there. When the Monday sweep has a card for you, it carries what is on the plan for the week ahead, as you wrote it.
  • Keep your ideas in one place. Say "I could write about the flaky test" and Ideas and plan puts it on the Post plan in your own words; give it a day and a platform when you know one, and it appears on What goes out when, the calendar on the board. To plan a week, ask Aster: it sets what is already planned beside your own rate and goes through the bank with you, and the picks and the days stay yours. Keep the topics few and in your own words, because they are what the board groups by and what an idea is filed under.
  • Stuck for something to say? Ask Aster for ideas and Ideas and plan looks only in what you have already written, naming the note each one came from. It never ranks an idea, never picks a day for you and never fills an empty one.
  • Ask Aster for a draft from something you have already written: "draft a post from my notes on the importer rebuild". Post drafts reads the note and writes in your voice, saves it under Presence/Drafts, and for X can put it on the review panel where you edit the words and tap Post yourself. Nothing here posts for you, and the LinkedIn drafts are notes you copy across on purpose.
  • Hand Aster a post you have already written and ask for it on each platform you use: Post drafts keeps your words and changes only what each platform needs. Paste a tired bio or headline and Profile refresh drafts a fresher one, measured against the platform’s own limit, for you to paste yourself. Correct either out loud — "too long", "never open with a question", "don’t say we’re excited" — and Aster keeps that as a standing preference, so the next draft starts where the last one ended up.
  • Read What landed on X as the typical post on a topic, not the best one — it is a median over at least two of your own X posts, and it exists only because X reports likes, replies and reposts. There is nothing equivalent for LinkedIn: it hands back your posts and no engagement at all, which is why those cells are blank rather than zero, and why there is no follower line anywhere on the board.

Make it yours

Nothing here is fixed. The pieces are ordinary agents, routines, datasets and dashboards, so anything you know about shaping those applies. Retire whatever earns nothing.

Things people usually change first

Say any of these in chat, or edit them on the kit’s page in the app.

  • How many posts a week you are aiming for on each platform, and the topics you keep to — both live on the Presence intent record and change by saying so.
  • Your ideas and the days you give them, on the Post plan: add, move or drop any of them by saying so. A day there is a note to yourself; nothing is ever posted from it.
  • Which platforms count. A platform this kit cannot read still gets a row and still counts; one you have stopped is paused, not deleted.
  • The voice the drafts are written in — length, how they open, what you never say — kept as standing preferences and applied to the next draft.
  • When the Presence sweep runs, or pausing it and keeping the log by hand.
  • Whether X is connected at all. Without it there are no engagement figures anywhere, which the board says plainly rather than showing zeros.

Your first run

Installing starts a short setup conversation — not a form. Answer roughly, correct later.

  1. Installing ends at the first sweep’s own screen. Reading your own posts is the whole pitch, so connect X, LinkedIn or both on the Connectors screen first. Then start the sweep with one tap and Aster reads back your OWN recent posts on whichever of the two you have connected: the last twenty on each, which is as far back as either service lets us look. From X it takes the likes, replies and reposts each post has now; LinkedIn returns no engagement of any kind, so those stay empty. It never reads your feed, anyone else’s posts, or your messages, and it never posts, replies or reacts. It is a real run and uses credits like any other.
  2. When that first sweep finishes, Aster leaves one card with what it found — how many posts, across which platforms — and an invitation to spend ten minutes together. Aster starts from what 1Presence already knows, what you have told it and notes in your vault, offers it back for a yes, and asks only for the gaps. That conversation is where the intention gets written down: where you actually post, roughly how many posts a week you are aiming for on each, and the two or three topics you keep coming back to. Then you go through the filed posts a handful at a time and say which is which, so the board has something honest to group by. Anything the sweep could not see — older posts, a talk, a newsletter — goes on there too.
  3. Skip the sweep and the kit still works entirely by hand: Aster looks at what 1Presence already knows first, then takes the intention one platform at a time, and logs posts as you mention them. Nothing in that conversation touches your accounts, and the Presence sweep waits on your Routines screen until you choose to run it.
  4. Whatever is still missing, usually where you post, what you post about or how often you are aiming for, waits on the Kit page with a way back to Aster, and Aster offers it once the next time you talk. Tell it a part does not apply to you, or that you have finished setting up, and it stops asking.
  5. After that the sweep runs every Monday at eight: it reads back the same twenty, files anything new, refreshes the figures X reports on posts it can still see, redraws the board, and leaves at most one short card — the week against your own rate, what is waiting in drafts and what is on your plan for the week ahead — or nothing at all, when nothing has changed.

Watch the first pass, then tell it what you would have done differently — that correction teaches it more than any setup could.

The essentials

Learning, preferences and run costs work the same in every kit — so they are covered once, in the Kits guide.

Living with a Kit — the Kits guide →

← All kits

Put the Social Presence kit to work.

Install it, run it once against something that already happened, and see whether what comes back sounds like you.

Try it free

Everything it installs can be retimed, paused, or removed.

Last reviewed