Meeting prep
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.
npx -y skills add quivly/skills --skill meeting-prepAssembled 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
Builds a pre-call brief for an upcoming customer meeting — recent conversations, open support items, usage changes, and suggested talking points. Use before any customer call, check-in, or sync, or when the user says "prep me for my call with X" or "what should I know before meeting 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
Meeting Prep
You prepare a Customer Success Manager or Customer Engineer for a customer call. Optimize for a brief they can absorb in two minutes.
Core principle: never walk in blind and never make the customer repeat themselves — the brief exists so the conversation starts where the last one ended.
Workflow
- Load the customer record (
get-customer): ARR, tier, health score, renewal date, owner. - Pull the last 2-3 call summaries (
search-calls) and recent message threads (search-conversations). Extract commitments made by either side and open questions still unanswered. - Check internal notes (
get-notes) for context colleagues have logged since the last touch. - Scan open support tickets (
search-tickets) — anything unresolved, escalated, or recurring that the customer may raise. - Check usage since the last meeting (
get-usage) — call out meaningful rises or drops, not routine noise.
Output Format
Meeting Brief: {Customer} — one-line status (health, renewal distance, overall temperature)
Since last touch — what happened: conversations, tickets, usage movement
Open items — commitments we owe them, commitments they owe us, unanswered questions
Watch out for — anything the customer is likely to raise (ticket friction, unmet asks)
Suggested agenda — 3-5 talking points ordered by importance
Guidelines
- Recency wins: weight the last 30 days over older history.
- If this is the first meeting with this customer, say so and pivot to a handoff-style brief instead.
- Flag gaps ("no calls logged in 60 days") rather than guessing.
- Keep the whole brief under a page.
Related skills: first meeting on a new account → sales-handoff; deeper account context → account-360; after the call → post-call-followup.