# ad-campaign-runbook (Agent Skill)

> A LinkedIn Ads campaign runbook for one blog post: what the site can measure, a campaign structure sized by the budget, ad copy traced to the post, tracking and click-by-click Campaign Manager steps.

Page: https://timerise.ai/skills/ad-campaign-runbook

Agent Skill `ad-campaign-runbook`: https://github.com/timerise-ai/ad-campaign-runbook. Category: Marketing. Runs on Next.js; backend: No data store, markdown posts in the repository; analytics vendor and consent component behind a seam.

Latest release: v0.1.4 (2026-10-07).

Install: npx skills add timerise-ai/ad-campaign-runbook. A tool for an agent, not a module: nothing for Timerise to build or quote.

A good blog post with a real offer in it deserves paid traffic. On LinkedIn the usual plan is a funnel: awareness, consideration, conversion, a campaign for each. At a small B2B budget that plan cannot run. The platform's daily minimum leaves money for one campaign, and a tag that records page views cannot report a conversion, however the plan words it.

So the plan has to start from the sums and from what the site can actually measure, not from the funnel someone would like to draw. Then the ads have to say only what the post says, and a marketer has to be able to run the campaign without the author in the room.

This skill gives an agent the runbook we write for every post we promote: it checks what the site measures, sizes the campaign to the budget, writes ads whose every sentence traces back to the post, and adds an organic companion post, tracking links, conversions and click-by-click Campaign Manager steps. It reads the ad account but changes nothing without a yes.

Write a LinkedIn Ads campaign runbook for one blog post: goals and metrics, a code-and-live probe of what the site can actually measure, budget-derived campaign structure, audience, ad copy traceable to the post, an organic companion post with author-only fact slots, UTM and conversion tracking, click-by-click Campaign Manager steps, operating cadence, tracking sheet and post-mortem template. Use when: (1) a blog post, case study or manifesto page should get paid LinkedIn promotion, (2) a runbook already exists and the next post needs its own, (3) the user mentions: ads runbook, ad campaign for this post, LinkedIn ads for the blog post, promote this post, campaign runbook, Campaign Manager instructions, ad copy for the post, utm_content, Insight Tag, lintrk, conversion tracking for ads, "a runbook like the last one". Carries the arithmetic that sizes the plan to the budget, a probe that establishes what the site measures before anything is promised, copy traceable sentence by sentence to the post, and the platform defaults that leak budget when left on. Takes the path to the post's markdown file as a required argument and stops without it. Written for a Next.js App Router marketing site whose posts are markdown in the repository; the host's analytics vendor, consent component, conversion vocabulary and runbook folder are the seam. LinkedIn only. Not an organic posting skill, not an ads API client, and not a writer of the blog post itself.

This skill was written by the engineer who has shipped this work. The earlier implementation it was audited against was a LinkedIn ads runbook for a B2B marketing site with consent-gated analytics and a sign-in wall between the ad click and the conversion. The procedure holds the properties a runbook has to hold: a campaign count that follows from the budget and the platform minimum, a dated record of what the site measures, every ad claim traceable to a sentence in the post, personal facts left as slots for the person whose name goes on them, an ad account the agent reads but never changes without a yes, and a finished file with no placeholder and no fact older than the day it was handed over. [`references/provenance.md`](references/provenance.md) has the record.

What it builds:
- A probe of what the site actually measures
- A campaign structure sized by the budget and the platform minimum
- Ad copy traceable to the post
- An organic companion post with author-only slots
- UTMs, conversions and click-by-click Campaign Manager steps

When to use:
- A post with a real offer in it should get paid LinkedIn traffic.
- The host already has one campaign runbook and the next post needs the same.
- Someone asks for ad copy, UTMs or Campaign Manager steps for a specific post.

When not to use:
- **Organic LinkedIn posts or comments**: `linkedin-marketing`. This drafts one companion post for its audit.
- **Boosting a Company Page post (Engagement, link in the first comment)**: `linkedin-boost`.
- **Writing the blog post itself**: `blog-markdown` and the host's content workflow.
- **Meta, Google or X ads**: not covered, see [provenance.md](references/provenance.md).
- **Creating campaigns through an ads API**: this produces a document for a human to execute.
- **A post with no offer or next step**: fix the post first, and say so.

Non-negotiables:
- Never run without the post file. Which content gets the budget is the user's decision. The preflight exits `2` on a missing, non-file or non-markdown argument, and the skill stops there and asks.
- Never write a claim the post does not make. Every ad sentence names the post sentence it comes from, and the post's own caveats bind the ads. The creative audit drops what has no source.
- Never invent a budget, a benchmark or a fact about the author. Budgets come from the user, planning numbers are labelled as assumptions until a post-mortem replaces them, personal facts stay as slots the author fills before publication, and an input nobody gave takes its documented default and is listed as open.
- Never assume tracking works. An installed tag records page views. The probe reads the code and one live page, dates its findings, and what is missing becomes a ticket rather than a promise.
- Never change the ad account without an explicit yes for that action. Reading a signed-in session is fine. Creating a conversion, audience or campaign accepts the advertising agreement on the user's behalf, so the skill fills the form, stops at the review step and shows what will be created.
- Never leave a placeholder or a stale fact in the finished runbook. The verification step greps for `{{` and rereads the tracking, creative and build sections against what is true on the day it is handed over.

Not this:
- Writing and publishing organic LinkedIn posts or comments: The `linkedin-marketing` skill. This skill drafts one companion post and hands it to that skill's audit
- Boosting a Company Page post (Engagement objective, link in the first comment): The `linkedin-boost` skill
- Writing the blog post itself: `blog-markdown` and the host's content workflow. A post with no offer in it is not a paid candidate
- Meta, Google or X campaigns: Not covered. The build steps are LinkedIn's, and another channel needs its own minimums, objectives and formats established first
- Creating campaigns through an ads API: This skill produces a document for a human to execute in Campaign Manager
- Reporting on a campaign that has already run: Section 9 of the template, the post-mortem, which feeds its actuals into the next runbook

What to tell your agent:
- Save the post below as content/blog/en/stop-confirming-bookings-by-phone.md, then write the LinkedIn ads runbook for it. We have 2,000 EUR a month, we sell to clinic and studio owners in Germany and Poland, and I will post the organic companion myself.

---
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 LinkedIn ads for our latest blog post. We can spend about 1,500 EUR a month.
- Here is a short post of ours; save it as content/blog/en/new-calendar-view.md and give me the LinkedIn ad copy and the Campaign Manager steps to promote it on 600 EUR a month.

---
title: A new calendar view
date: 2026-09-15
---

The calendar now has a week view for each staff member. Drag an appointment to move it, and the client gets a message with the new time. [See it in the demo](/demo).

Agent eval results (newest per agent and prompt):
- Gemini CLI (gemini-3.8-flash) on v0.1.4, 2026-10-07: pass (No data store)
- Codex CLI (gpt-6.1-sol) on v0.1.4, 2026-10-07: pass (No data store)
- Claude Code (claude-opus-5-5) on v0.1.4, 2026-10-07: pass (No data store)

Recent releases:
- v0.1.4 (2026-10-07): A wording release, from scoring the prompt-1 agent eval runs of 0.1.3.
- v0.1.3 (2026-10-07): A fix release, from scoring the prompt-1 agent eval runs of 0.1.2.
- v0.1.2 (2026-10-07): A fix release, from scoring the prompt-1 agent eval runs of 0.1.1 against a fidelity rubric.
