Starter

Premium

The problem was never ideas. It was that writing the post took forty minutes, and forty minutes at seven in the morning is the first thing to go. So most weeks the channel went quiet by Wednesday.The agent has three parts. The source is an Apify scrape of the dozen sites I already read — it runs at six and lands as one source. The prompt is a page long: what I care about, what I never post about, four real posts of mine as examples, and one rule that has done more than the rest combined: if you are not sure the claim is true, leave it out and say so in the note. The output is LinkedIn and X, with a copy to a Telegram chat with me so I see it first.It runs at seven. Most mornings two posts go out and a third is dropped with "couldn't verify" in the run note. On the days I have something to say myself, I say it and the agent's post simply goes out later. That is the arrangement: it keeps the cadence, I keep the voice.A month in: twenty-two posting days, no gap longer than a weekend, and the prompt has been edited four times — each time because I read a post and thought "I wouldn't have said that". That edit is the job now. It is a better job than the forty minutes were.

One scrape, one prompt in your own voice, a 7 a.m. trigger — and what a month of it actually looks like.

Post every morning without writing every morning

Ebiblo is a knowledge-check app: a tutor uploads material, question sets appear, a person approves them, learners answer on a phone and see why each answer was marked as it was. It is a separate product with its own customers. It also contains no AI of its own. Every question it has ever shown a learner came out of an Emidox agent.Here is the flow, node by node. The source is an Ebiblo input page — an Emidox input source that a tutor opens from inside Ebiblo. They upload a worksheet, type or speak one line about what to ask, and press Send. The first agent reads it against a long instruction: check the maths, rewrite for a Year 8 reading level, fill in missing options, produce the answer key with a worked line for each. Its output is Ebiblo's quiz page — the questions arrive there as a draft, and Ebiblo notifies the tutor.Behind that first agent sits a second one with router mode on. When a centre runs several subjects through one form, the router reads each submission and sends it to the maths agent, the science agent or the reading agent — each with its own prompt and its own quiz page. That is the whole pipeline: one input page, a router, a few specialists, a few quiz pages. It runs on update, so it fires every time material arrives and never otherwise.Two things follow. Ebiblo's people never open Emidox unless they want to change a prompt; the agents were made once and the two apps share a login, so the tutor stays in Ebiblo. And the same shape — an input page in, a specialist agent, a product page out — is not specific to quizzes. It is what any app built on Emidox looks like. Ebiblo just happens to be the first.

A form, two agents and a quiz page: the whole of Ebiblo's question pipeline, drawn end to end.

How Ebiblo runs on Emidox

The team watches about forty pages: regulators, two competitors' changelogs, a handful of forums, a few people's feeds. Someone used to open them all on a Monday. By Thursday nobody had.The scrape is an Apify actor with the forty URLs, scheduled for six. It lands in Emidox as a source that grows by one entry a day. The agent's prompt asks for one thing: compare today's copy of each page with yesterday's, and list only what changed, grouped by why it matters to us — and it is given the "why it matters" as a paragraph about what the team does. The model is Gemini Flash, because reading forty pages is a volume job and a cheap model does it well.The output is a Telegram channel the team already had. At 6:30 there is a message with the six or so changes that matter, each with the page it came from, and a line at the bottom: "34 pages unchanged". Nobody opens forty tabs. When something is wrong — it once flagged a date format change as a policy change — the fix is a sentence in the prompt.The part worth copying is not the scrape or the model. It is the phrase "only what changed". Most digests fail because they summarise everything, and a summary of everything is just a shorter version of the reading you were trying to avoid.

Forty pages a day read for you, sorted by what changed, and delivered to a Telegram channel before you sit down.

The blog

Post every morning without writing every morning

How Ebiblo runs on Emidox

A scrape, a prompt and a digest