Menu
Detect a late purchase order, chase it with the right ask, and escalate on a schedule.
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 supplier-chaseThe 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 | Supplier chase |
| description | Detect a late purchase order, chase it with the right ask, and escalate on a schedule. |
| category | operations |
A chase that says "any update?" gets an answer that says "we're looking into it". Ask for a commitment.
PO number · what was ordered and how many · the date promised · how many days late it is now · what it is blocking, in customer orders rather than internally.
"What date will this ship, and what quantity?" Not a status. A date and a number can be planned around; an update cannot.
Day 1 late: the buyer contact. Day 3: their manager, with the original request attached. Day 7: sourcing, with the customer impact quantified. Say at each step what the next step will be and when.
"Is any of it available now?" A partial shipment usually clears the urgent orders and nobody offers it unprompted.
Accept "next week" without a date, or promise a customer a date the supplier has not committed to in writing.
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.