Menu
Write a follow-up that answers the objection rather than repeating the offer.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Based on SOC occupation classification
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/vstorm-co/agenticos --skill abandoned-cart-follow-upThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
| name | Abandoned cart follow-up |
| description | Write a follow-up that answers the objection rather than repeating the offer. |
| category | marketing |
Most abandonment is a question, not indecision. Answer the question.
Reached shipping and stopped → the shipping cost or the delivery date. Sat on sizing → fit uncertainty. Repeated visits to one item → a specification they cannot find. Payment page → a method you do not offer.
One message, one objection, answered concretely: the actual delivery date, the returns terms in one line, the size chart, the missing specification.
A discount on the first message teaches the customer to abandon. If the diagnosis is price, say what the price includes rather than reducing it.
Two messages maximum, at least a day apart, both with a one-click way to stop. Never send after they have bought — check first, every time.
Fabricate scarcity, invent a countdown, or claim stock is low unless the record says so.
Work with messaging-channel bots — Telegram, Slack or Mattermost. Register a bot, route inbound messages through an agent, choose webhook vs polling, handle an @slug mention, or add a new channel adapter. Use when wiring chat into a messaging platform or debugging bot delivery, identity linking or "the bot answered as itself".
Change the agent spec — add or remove a field, rename one, tighten a rule, bump SPEC_VERSION, change publish-time validation, or touch YAML export/import. Use whenever editing app/agents/spec.py or anything that reads a stored spec. Every published agent and every client git repository holds a copy of this format, so a change that only works forwards breaks agents nobody touched.
Work with MCP servers — connect one, add an entry to the server catalog, debug "the agent cannot see my MCP tools" or a failing OAuth flow, or change how connections are probed, prefixed or filtered. Use when the ask involves an external SaaS tool (GitHub, Linear, Notion, Slack, Stripe, Postgres…) and before writing a capability that would just be an API client for one.