The problem
What problem does LinkedIn boost solve?
Boosting a Company Page post is the cheapest paid test on LinkedIn, and the easiest to waste. The post carries no link, so LinkedIn cannot optimise for visits to the site. Every sign-up depends on readers opening the first comment. The Boost button also hides most of the settings that decide where the money goes.
What makes a boost work happens around it: the image, the first comment with the link, the first 90 minutes, founders reposting with their own words, messages to the people who know you. When nobody's name is on those tasks, they do not happen, and when the publish date moves, half of them stay on the old day.
This skill gives an agent the runbook we write for every boost: what the boost can and cannot buy, a lifetime budget sized to the run, the post, comment and image traced to the blog post, the Campaign Manager build with every setting visible, a named person on every task, weekly decision rules, and one date that moves everything else with it.
The tool
What does the skill do?
This skill adds no module to your app: your agent runs it as a tool. What LinkedIn boost does:
- 1. What a boost buys and what it cannot
- 2. A lifetime budget sized to the run
- 3. The image
- 4. Post text and first comment with the link
- 5. Founder reposts and network DMs
- 6. The Campaign Manager build the Boost button hides
- 7. A named person on every task
- 8. Weekly decision rules and a date cascade when the publish date moves
Provenance
Where do the rules come from?
This skill was written by the engineer who has shipped this work. The earlier implementation it was audited against was a boost runbook for a B2B marketing site, written as a delta of a Website visits runbook. The procedure holds the properties a boost runbook has to hold: a lifetime budget whose run days and pace match the dates, every sentence of the post, comment, reposts and DMs traceable to the blog post, a named person on every task and checklist item, a boost built in Campaign Manager with every setting visible, an ad account that is never changed without a yes, and a finished file with no placeholder and no stale date. `references/provenance.md` has the record.
The ledger for this skill: what the audit changed and how the procedure holds it, what was kept on purpose, and what was designed here. Read it before simplifying anything.
The ledger separates what the audit changed, what was kept on purpose, and what has not run in production yet.
Fixed
- Owners that were teams The header named "Marketing" and "Sales", and no task had a person. Before launch the user had to ask for the unassigned tasks and go through them one by one: most got a person, a few were deleted as nobody's work. Held by: the hard rule, the owner forms and the unassigned-tasks pass in schedule-and-owners.md.
- A moved date that needed a manual cascade Moving the publish by one day moved the boost start, the build's start date, a founder's repost and the DM start, and changed the run days, the daily pace and the weekly pace quoted in the decision rules. Each was a separate edit, and a missed one would have left the boost starting before the post. Held by: the date cascade table and the grep for old dates in schedule-and-owners.md.
- Checklist items that repeated build steps The before-launch list re-checked audience expansion and the Audience Network, which the build unticks, and asked to notify Sales when the people receiving conversions were already named. Both were deleted by the user. Held by: the checklist rule: only checks that are not build steps, no notification item when the receivers are named.
- The Boost button Boosting from the post hides the settings and leaves expansion and the Audience Network on. Held by: the build starts in Campaign Manager from Browse existing content, in campaign-manager.md.
Non-negotiables
What are the 6 rules the module never breaks?
Every module built from this skill holds these, whoever builds it. The same list is in the skill's README and SKILL.md, so the agent reads it before it writes a line.
Never run without the post file.
Which content gets the budget is the user's decision. A missing, non-file, non-markdown or short post stops the skill, and it asks.
Never write a claim the post does not make.
The company post, comment, reposts and DMs each name the blog post sentence they come from, and the post's caveats bind them. The creative audit drops what has no source.
Never invent a budget, a benchmark or a fact about a person.
Budgets come from the user, planning numbers are labelled as assumptions, a person the user did not name stays a role, and repost texts in someone's voice need that person's yes.
Never leave a task without a named person.
A team is not an owner. The unassigned-tasks pass gets a name for every task or deletes it; when the agent cannot ask, the task stays
openin the runbook and the handover asks for it, never a guess.Never change the ad account without an explicit yes for that action.
Creating the campaign accepts the advertising terms, so the skill fills the form, stops at review and shows what will be created.
Never leave a placeholder or a stale date.
One moved date runs the cascade, recomputes the run days and the pace, and the handover greps for
{{and the old dates.
Fit
When should you use it, and when not?
Use it for
- A blog post already has, or will get, a Company Page post with the link in the first comment.
- The budget is small and the team wants to learn what the audience engages with before paying for clicks.
- A boost runbook exists and its dates or owners must change.
Not for
- A Website visits campaign with link adsInsteadThe sibling skill `ad-campaign-runbook`
- A post on a personal profileInsteadThe author's own posting or voice skill. This skill drafts repost texts and hands them over
- Thought Leader Ads, Meta, Google or XInsteadNot covered
- Creating campaigns through an ads APIInsteadThis skill produces a document for a person to execute in Campaign Manager
Install
How do I install it?
One command. The skills.sh CLI installs the skill into every skills-compatible agent it finds.
$ npx skills add timerise-ai/linkedin-boostClaude Code
Invoke with /linkedin-boost
Codex CLI
Invoke with $linkedin-boost
Gemini CLI
Invoke with /skills
Name the agents instead with -a, for example npx skills add timerise-ai/linkedin-boost -a claude-code -a codex. Or clone the repository into your agent's skills folder. Nothing in it is agent-specific.
What is inside the repository (15 entries)
SKILL.mdEntry point: the required input, architecture, eight critical facts, six hard rules, quick start, reference directoryreferences/adaptation.mdThe seam with the host: what it must provide, the rename table, languages, the non-negotiables restatedreferences/inputs.mdThe required post, the optional main runbook, the inputs to ask for in one batch, every placeholderreferences/strategy.mdBoost versus Website visits, one test at a time, lifetime versus daily, planning numbers, bidding, decision rules, month-end decisionreferences/creative.mdImage, company post, first comment, first 90 minutes, reposts, DMs, the auditreferences/campaign-manager.mdWhy not the Boost button, the ten build steps, a second post in the month, gotchasreferences/schedule-and-owners.mdOwner forms, the unassigned-tasks pass, the date cascade, the before-launch checklistreferences/runbook-template.mdThe document to produce, with fixed section numbersreferences/provenance.mdThe engineering ledger: what the audit changed, what was kept on purpose, what was added hereREADME.mdThis fileCHANGELOG.mdRelease history, newest firstCLAUDE.mdThe editing conventions, for an agent editing this repositoryLICENSEMITevals/The prompts an operator types after installing (prompts.md) and one file per agent eval: the skill installed into an empty Next.js app, one prompt carrying what it works on, no help, then type-checked and built.github/workflows/agent-eval.ymlThe caller of the index's reusable eval workflow, run on every published release and on a maintainer's dispatch
Recent releases
- v0.1.3October 7, 2026
Fix release, from scoring the prompt-1 agent eval runs against 0.1.2.
- v0.1.2October 7, 2026
Fix release, from scoring the prompt-1 agent eval runs against 0.1.1.
- v0.1.1October 7, 2026
Fix release, from scoring the prompt-1 agent eval runs against 0.1.0.
After installing
What do I tell my agent?
Say what you need in your own words; the skill supplies the how. These are starting points, and the ones we tested say how it went.
Save the post below as content/blog/en/stop-confirming-bookings-by-phone.md, then write the runbook for boosting our Company Page post about it. 1,500 EUR for November, we post on Tuesday 2026-11-03 at 7:30. Ana publishes and builds the boost, Ben checks tracking, and our two founders repost in Polish. There is no main ads runbook yet. --- title: Stop confirming bookings by phone date: 2026-09-01 author: Head of Product --- Most small clinics and studios still confirm every appointment by phone the day before. A receptionist works down a list, leaves voicemails, and marks the ones who answered. It feels like care. It is mostly lost time. [Try automatic confirmations free for 14 days](/signup). ## Where the first hour goes We looked at how front desks using our booking software spend the first hour of the day. The confirmation calls were the largest single block, larger than check-ins and larger than rescheduling. The calls also reached the fewest people: a client who books online rarely answers an unknown number at work. ## What we changed So we replaced the call with a message the client can answer in one tap. Two days before the visit they get a text and an email with three buttons: keep, move, or cancel. Keep does nothing. Move opens the calendar at the same service and the same staff member. Cancel frees the slot at once, and the waiting list gets the offer within a minute. Three things changed for the clinics that switched. The front desk got its first hour back. Cancellations arrived two days out instead of at the door, which is early enough to fill the slot. And the clients who never answered calls started answering, because a button is easier than a conversation. ## What it does not fix A client who has decided not to come will not tell you, whatever the channel. A deposit or a cancellation fee is the tool for that, and we do not think a reminder should pretend otherwise. If most of your no-shows come from new clients booking free first visits, start there. Setting it up takes about ten minutes. You choose when the message goes out, write the text in your own words, and decide whether a cancellation opens the slot to the waiting list or to everyone. Nothing changes for clients who prefer to call: the phone still works, it just stops being the only way. If your desk still starts the day with a call list, try it for two weeks and compare the first hours. [Start the free trial](/signup).
Write a boost runbook for our latest blog post, 1,000 EUR this month.
No data storeSave the runbook below as docs/runbooks/linkedin-boost-phone-confirmations.md. We moved the Company Page post from Wednesday to Thursday, same time. Update the runbook. # Runbook: LinkedIn Boost Post for "Stop confirming bookings by phone" **Type:** Short campaign runbook (one boosted Company Page post) **Budget:** 1,500 EUR for November 2026, lifetime, ends 2026-11-30 **Source content:** `content/blog/en/stop-confirming-bookings-by-phone.md` **Owner:** Ana (post, comment, first 90 minutes, build); Ben (tracking, weekly check, results) **Status:** Draft, not launched **Last updated:** 2026-10-20 ## 2. Budget and schedule | Date | What | Who | | :-- | :-- | :-- | | Mon 2026-11-02 | Image, post text and comment ready; blog post review | Ana | | Wed 2026-11-04, 7:30 | Company Page post, first comment with the link | Ana | | Thu 2026-11-05 | Boost starts (build step 6 start date); first founder repost; DMs start | Ana, Marek | | Mon 2026-11-09 | Second founder repost | Ola | | Mon 2026-11-16, 11-23, 11-30 | Weekly check | Ben | | Mon 2026-11-30 | Boost ends 23:59; results row | Ben | 26 days at 1,500 EUR is about **58 EUR a day**, about 404 EUR a week. Use a **lifetime** budget. ## 4. Setting up the boost **Owner: Ana.** Step 6: lifetime 1,500 EUR from 2026-11-05 to 2026-11-30 23:59. ## 6. Weekly check (Mondays, 15 minutes) **Owner: Ben.** Spend under 60% of pace (about 404 EUR a week): raise the bid to the middle of the suggested range.
No data store
Tested
How does it do in each agent?
We install the skill into an empty Next.js app, give the agent one of the prompts above and no further help, then type-check, build and run the tests it left behind. Nothing is fixed by hand before the checks, and a failing run is published like a passing one. The procedure and every result are public, and the first prompt runs again before each release.
- Built, checks pass
Gemini CLI0.63.0
gemini-3.8-flash
Save the post below as content/blog/en/stop-confirming-bookings-by-phone.md, then write the runbook for boosting our Company Page post about it. 1,500 EUR for November, we post on Tuesday 2026-11-03 at 7:30. Ana publishes and builds the boost, Ben checks tracking, and our two founders repost in Polish. There is no main ads runbook yet. --- title: Stop confirming bookings by phone date: 2026-09-01 author: Head of Product --- Most small clinics and studios still confirm every appointment by phone the day before. A receptionist works down a list, leaves voicemails, and marks the ones who answered. It feels like care. It is mostly lost time. [Try automatic confirmations free for 14 days](/signup). ## Where the first hour goes We looked at how front desks using our booking software spend the first hour of the day. The confirmation calls were the largest single block, larger than check-ins and larger than rescheduling. The calls also reached the fewest people: a client who books online rarely answers an unknown number at work. ## What we changed So we replaced the call with a message the client can answer in one tap. Two days before the visit they get a text and an email with three buttons: keep, move, or cancel. Keep does nothing. Move opens the calendar at the same service and the same staff member. Cancel frees the slot at once, and the waiting list gets the offer within a minute. Three things changed for the clinics that switched. The front desk got its first hour back. Cancellations arrived two days out instead of at the door, which is early enough to fill the slot. And the clients who never answered calls started answering, because a button is easier than a conversation. ## What it does not fix A client who has decided not to come will not tell you, whatever the channel. A deposit or a cancellation fee is the tool for that, and we do not think a reminder should pretend otherwise. If most of your no-shows come from new clients booking free first visits, start there. Setting it up takes about ten minutes. You choose when the message goes out, write the text in your own words, and decide whether a cancellation opens the slot to the waiting list or to everyone. Nothing changes for clients who prefer to call: the phone still works, it just stops being the only way. If your desk still starts the day with a call list, try it for two weeks and compare the first hours. [Start the free trial](/signup).
Typecheck: passBuild: passTests: not run- Time
- 6 min
- Changed
- 5 files, +369 lines
- Stack
- No data store
- Skill
- v0.1.3
- Run
- Oct 7, 2026
What we saw
Rubric 8/8, scored from the final summary. This dispatched run takes the place of the 0.1.3 release run's gemini-cli job, which never ran because GitHub rejected the claude-code result push with a 500. The four handover lines are there, and the Open: line names eight open owners and inputs, each with what it blocks: deployment and review, image, the first 90 minutes, founder names, DM senders, the weekly check, results and baseline, and the account and launch approval. The boost starts at 07:30 Warsaw on 2026-11-04, runs 27 days at 55.56 EUR a day and 388.89 a week, and the first weekly check is 2026-11-16. The founders stay
repost-founder-1andrepost-founder-2, the campaign isPOST | phone-confirmations | BOOST | 2026-11, and no credential is named. Not scored: a second index atdocs/README.md. - Built, checks pass
Codex CLIcodex-cli 0.161.0
gpt-6.1-sol
Save the post below as content/blog/en/stop-confirming-bookings-by-phone.md, then write the runbook for boosting our Company Page post about it. 1,500 EUR for November, we post on Tuesday 2026-11-03 at 7:30. Ana publishes and builds the boost, Ben checks tracking, and our two founders repost in Polish. There is no main ads runbook yet. --- title: Stop confirming bookings by phone date: 2026-09-01 author: Head of Product --- Most small clinics and studios still confirm every appointment by phone the day before. A receptionist works down a list, leaves voicemails, and marks the ones who answered. It feels like care. It is mostly lost time. [Try automatic confirmations free for 14 days](/signup). ## Where the first hour goes We looked at how front desks using our booking software spend the first hour of the day. The confirmation calls were the largest single block, larger than check-ins and larger than rescheduling. The calls also reached the fewest people: a client who books online rarely answers an unknown number at work. ## What we changed So we replaced the call with a message the client can answer in one tap. Two days before the visit they get a text and an email with three buttons: keep, move, or cancel. Keep does nothing. Move opens the calendar at the same service and the same staff member. Cancel frees the slot at once, and the waiting list gets the offer within a minute. Three things changed for the clinics that switched. The front desk got its first hour back. Cancellations arrived two days out instead of at the door, which is early enough to fill the slot. And the clients who never answered calls started answering, because a button is easier than a conversation. ## What it does not fix A client who has decided not to come will not tell you, whatever the channel. A deposit or a cancellation fee is the tool for that, and we do not think a reminder should pretend otherwise. If most of your no-shows come from new clients booking free first visits, start there. Setting it up takes about ten minutes. You choose when the message goes out, write the text in your own words, and decide whether a cancellation opens the slot to the waiting list or to everyone. Nothing changes for clients who prefer to call: the phone still works, it just stops being the only way. If your desk still starts the day with a call list, try it for two weeks and compare the first hours. [Start the free trial](/signup).
Typecheck: passBuild: passTests: not run- Time
- 3 min
- Changed
- 5 files, +310 lines
- Stack
- No data store
- Skill
- v0.1.3
- Run
- Oct 7, 2026
What we saw
Rubric 8/8, scored from the diff. This dispatched run takes the place of the 0.1.3 release run's codex job, which never ran because GitHub rejected the claude-code result push with a 500. Item 8 now holds: the Open: line in the final message names each open task and input (deployment, content and image owners, the first-90-minutes coordinator, founder names, DM senders, the weekly, results and baseline owners, the account details, launch approval, audience, conversions and tracking sheet), and pointing at the runbook is gone. Drafts:, Assumptions: and Ad account: are all there. The runbook keeps sections 1 to 9 and leaves no
{{. The boost starts at 07:30 Warsaw on 2026-11-04 and runs 27 days at 55.56 EUR a day and 388.89 a week, and the first review is 2026-11-16. The founders stayrepost-founder-1andrepost-founder-2, every role nobody was given isopen, and no credential is named. - Built, checks pass
Claude Code2.1.292
claude-opus-5-5
Save the post below as content/blog/en/stop-confirming-bookings-by-phone.md, then write the runbook for boosting our Company Page post about it. 1,500 EUR for November, we post on Tuesday 2026-11-03 at 7:30. Ana publishes and builds the boost, Ben checks tracking, and our two founders repost in Polish. There is no main ads runbook yet. --- title: Stop confirming bookings by phone date: 2026-09-01 author: Head of Product --- Most small clinics and studios still confirm every appointment by phone the day before. A receptionist works down a list, leaves voicemails, and marks the ones who answered. It feels like care. It is mostly lost time. [Try automatic confirmations free for 14 days](/signup). ## Where the first hour goes We looked at how front desks using our booking software spend the first hour of the day. The confirmation calls were the largest single block, larger than check-ins and larger than rescheduling. The calls also reached the fewest people: a client who books online rarely answers an unknown number at work. ## What we changed So we replaced the call with a message the client can answer in one tap. Two days before the visit they get a text and an email with three buttons: keep, move, or cancel. Keep does nothing. Move opens the calendar at the same service and the same staff member. Cancel frees the slot at once, and the waiting list gets the offer within a minute. Three things changed for the clinics that switched. The front desk got its first hour back. Cancellations arrived two days out instead of at the door, which is early enough to fill the slot. And the clients who never answered calls started answering, because a button is easier than a conversation. ## What it does not fix A client who has decided not to come will not tell you, whatever the channel. A deposit or a cancellation fee is the tool for that, and we do not think a reminder should pretend otherwise. If most of your no-shows come from new clients booking free first visits, start there. Setting it up takes about ten minutes. You choose when the message goes out, write the text in your own words, and decide whether a cancellation opens the slot to the waiting list or to everyone. Nothing changes for clients who prefer to call: the phone still works, it just stops being the only way. If your desk still starts the day with a call list, try it for two weeks and compare the first hours. [Start the free trial](/signup).
Typecheck: passBuild: passTests: not run- Time
- 3 min
- Changed
- 5 files, +375 lines
- Stack
- No data store
- Skill
- v0.1.2
- Run
- Oct 7, 2026
What we saw
Rubric 8/8, scored from the final summary. The handover now has the four labelled lines. Open: names each task with no owner (weekly check, results, baseline, putting the site live, image, Launch, DMs) and each missing value (founder names,
POST_URL, account, audience location). Drafts: asks for each founder's yes. Assumptions: labels the CPM, impressions and 0 to 3 sign-ups as planning numbers. Ad account: says nothing was changed. The boost runs from 07:30 on 11-04 to 11-30, 27 days at about 56 EUR a day and 389 a week, built in Campaign Manager. The weekly checks are 11-16, 11-23 and 11-30, and the founders stay roles.
Generated from the skill's own files at commit a87eb8d. Every rule above links to where the repository says it. All skills