agentsclimarketplace

Post call followup

Skill quivly/skills/customer-engineering/post-call-followup

Production-ready Agent Skills for Customer Engineering, Post-Sales, and Customer Success teams. Quivly Skills is a curated open-source collection of reusable skills that give AI agents deep expertise in customer engineering workflows. Every skill follows the official Agent Skills specification.

Install
npx -y skills add quivly/skills --skill post-call-followup

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Turns the most recent customer call into structured follow-up — action items with owners, commitments made, risks heard, and a draft recap message. Use after a customer call ends, or when the user says "summarize my call with X" or "draft the follow-up for X".

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.6 KB, as published. Nobody here has run it

Post-Call Follow-up

You convert a customer call into follow-through: clear actions, honest risk notes, and a recap the CSM can send with light editing.

Core principle: a follow-up item that isn't verb-first, owned, and dated isn't a follow-up — it's a wish.

Workflow

  1. Get the call summary (get-call-summary) for the most recent call with the customer. When nuance matters — exact wording of a commitment, tone on a sensitive topic — go to the transcript (get-call-transcript).
  2. Cross-check attendees against known contacts (get-contacts) — note any new stakeholders who appeared.
  3. Check recent notes (get-notes) so follow-ups don't duplicate work already in motion.
  4. Extract, in order of importance:
    • Action items — ours and theirs, each with an owner and a suggested due date
    • Commitments made (exact language if the stakes are high)
    • Risks or friction heard, even if implicit (hesitation about renewal, mention of a competitor, budget language)
    • New information about goals, org changes, or timeline

Output Format

Call recap: {Customer} — {date}

Action items — table: item, owner, due

Commitments — what we promised, what they promised

Signals worth logging — risks, expansion hints, stakeholder changes

Draft follow-up message — short, warm, specific; confirms actions and next step. Write it in the first person for the CSM to send.

Guidelines

  • Action items must be verb-first and assignable — "Send SSO setup guide (us, Friday)", not "discuss SSO".
  • Don't soften risks in the recap-for-internal-use section; do keep the customer-facing draft positive and concrete.
  • If the call was a negative one (escalation, complaint), lead the draft message with acknowledgment, not agenda.

Related skills: a new stakeholder appeared on the call → champion-change; prepping the next touch → meeting-prep.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.