Use it when analysing a competitor, or finding our positioning.
4 rolesRead moreYour agents already know the job.
A skill is a working playbook — how to review a pipeline deal by deal, close the month so the numbers hold, read an ad account without double-counting. Each one was written around a specific way the work goes wrong, and the agent loads it when the task calls for it. Every one we ship is below.
SHOWING 1–22 OF 22
Use it when asked why conversion or activation is down.
3 rolesRead moreUse it when asked which channel is working, or why one dropped.
3 rolesRead moreUse it when planning a campaign, an ad set, or a scheduled send.
2 rolesRead moreUse it when a writer needs a brief for a search-driven piece.
2 rolesRead moreUse it when designing or fixing a referral or advocacy program.
2 rolesRead moreUse it when planning search strategy, not writing one page.
2 rolesRead moreUse it when something was published and nothing happened.
2 rolesRead moreUse it when before running an A/B test or split experiment.
2 rolesRead moreUse it when a specific page or step converts badly.
2 rolesRead moreUse it when planning what gets published, when and by whom.
2 rolesRead moreUse it when planning a webinar, conference or customer event.
2 rolesRead moreUse it when planning a newsletter, lifecycle or broadcast email.
2 rolesRead moreUse it when the same message must land on a specific platform.
2 rolesRead moreUse it when considering or reviving a customer community.
2 rolesRead moreUse it when a talk, podcast or article should become posts.
2 rolesRead moreUse it when a customer result must become a usable story.
2 rolesRead moreUse it when a recurring email to a list must be written.
2 rolesRead moreUse it when drafting or editing any customer-facing copy.
2 rolesRead moreUse it when planning, scaling or cutting paid acquisition spend.
1 roleRead moreUse it when a public statement, launch story or incident note.
1 roleRead moreUse it when a video, demo or talk needs a script.
1 roleRead moreTreating a competitor's marketing claims as their capabilities, and shipping a feature matrix that concludes we have more features.
Reporting the biggest drop-off as the problem. The biggest drop is structural everywhere; the CHANGED drop is the leak.
Comparing channels on volume, which always crowns the cheapest top-of-funnel source and starves the one producing customers.
Assuming an expired approval means yes. A mission approval holds for 72 hours and then expires, and an expired approval is a DECLINE.
Briefing around a keyword and a word count. That produces a piece that matches the words in the query and answers a different question from the one the searcher asked, which is the standard way a technically correct article fails completely.
Bolting an incentive onto a product nobody recommends, which buys a burst of low-intent signups at a real cost and reads as proof that referrals do not work here.
A keyword list ranked by search volume, which reliably produces traffic that never buys — and a programme judged on sessions rather than on the customers it produced.
Treating publication as the end of the work. A piece published and posted once reaches a fraction of the audience it was made for, and the team concludes the content was bad rather than that it was never distributed.
Calling a winner on a test that never had the volume to detect the effect it was looking for, then rolling out a change that does nothing. The stopping rule decided after seeing the data is the specific failure.
A list of best-practice tweaks — bigger button, less copy, social proof — applied to a page whose problem was that the traffic was wrong. Changing the page cannot fix the audience, and the test that follows measures nothing.
A calendar of topics with no owner and no purpose per item, which produces posts nobody can evaluate and a schedule that quietly stops.
An event judged on registrations, with no follow-up plan written before the date — so the week it cost produces a list nobody works and the same event is repeated next quarter.
Treating a list as an audience that is owed nothing. Deliverability is earned per send and lost permanently, and a broadcast to a list nobody has cleaned damages every future send including the one that mattered.
Writing one post and pasting it everywhere. Each surface has a different unit of attention, a different first-line budget and a different relationship to links, so the cross-posted version is subtly wrong on every platform including the one it was written for.
Opening a public channel with no reason for anyone to be in it, which produces a visibly empty room that reads as evidence the company has no customers.
Summarising the source. A summary of an hour of talking is the one output nobody wants — the source already exists — and it hides the two or three claims that were worth arguing with, which is the only reason to post at all.
Publishing a result the customer did not confirm and cannot be attributed to us. An unverified number in a case study is quoted back by a prospect, checked by the customer, and it is the customer who is embarrassed — which ends the reference relationship and the story at once.
Writing the newsletter as a round-up of company news. The list did not subscribe to the company; it subscribed to something useful, and a sequence of announcements trains the most engaged readers to stop opening — which shows up as a healthy list and a dying one.
Rewriting into blandness — losing the specific, odd, true detail that was the best line on the page.
Scaling spend on a platform-reported ROAS, which is the platform marking its own homework. The store is the source of truth for money and the two numbers routinely disagree by more than the decision margin.
A public statement that commits the company to something nobody internally agreed, or an incident note whose hedging reads as a cover-up. Both are unretractable and both come from drafting before the facts and the approver were settled.
Writing a script as prose to be read aloud. Written sentences are longer and more subordinate than spoken ones, so a script that reads well is delivered stiffly and the viewer leaves in the first seconds — before anything the script was about.
Show us the work you want to delegate.
Book a tailored demo for AI Crew, Voice, Build or Missions. Track is available free for 30 days.