Marketing

Receipt for every post

After each approved post goes out, write one row to the Distribution table: channel, live link, tracked link, who approved it and when, so what was published is a record, not a claim.

Download LobstackRead the file

In Lobstack: Skills › Library › Add

For your agents

What your agent will do.

Every time something is published for a launch, newsletter or campaign. It is what the results are later read against.

  1. 01

    If there is no table called Distribution, ask to create it with create_table: Campaign, Channel, Live link, Tracked link, Approved by, Published at, Status. Creating it is a person's yes, once.

  2. 02

    After each publish, read back the live URL the service returned. A post with no live URL is not published; mark it failed and say why.

  3. 03

    Write the row with upsert_rows, matching on Campaign and Channel, so a repost updates the row instead of adding a second.

  4. 04

    Approved by is the person who said yes on the card, never the agent.

  5. 05

    At the end, list the campaign's rows: what is live, what failed, what is still a draft.

Never write a row for a post you did not see go live.

The file

The whole SKILL.md: 28 lines of Markdown.

Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.

distribution-receipt/SKILL.md28 lines
---name: distribution-receiptdescription: "After each approved post goes out, write one row to the Distribution table: channel, live link, tracked link, who approved it and when, so what was published is a record, not a claim."metadata:  title: "Receipt for every post"  category: marketing  tags: [marketing, distribution, reporting]--- ## When to use this Every time something is published for a launch, newsletter or campaign.It is what the results are later read against. ## How 1. If there is no table called Distribution, ask to create it with   create_table: Campaign, Channel, Live link, Tracked link, Approved by,   Published at, Status. Creating it is a person's yes, once.2. After each publish, read back the live URL the service returned. A   post with no live URL is not published; mark it failed and say why.3. Write the row with upsert_rows, matching on Campaign and Channel, so a   repost updates the row instead of adding a second.4. Approved by is the person who said yes on the card, never the agent.5. At the end, list the campaign's rows: what is live, what failed, what   is still a draft. Never write a row for a post you did not see go live.
Agents that start with it

Ready-made agents that follow this skill.

All agents.

More skills

More for your agents, from Marketing first.

All skills, on their shelves.