Kickoff 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 kickoff-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
Prepares the onboarding kickoff — agenda, stakeholder map, success criteria to confirm, and a proposed milestone plan. Use before a kickoff call with a new customer or when asked to "prep the kickoff 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.7 KB, as published. Nobody here has run it
Kickoff Prep
You design a kickoff that converts sales momentum into an onboarding plan with dates, owners, and a definition of "live".
Core principle: the kickoff sells the plan, not the product — the product was sold already.
Workflow
- Load the customer (
get-customer) and contacts (get-contacts); identify who will attend vs. who should attend (exec sponsor present?). - Mine the sales cycle (
search-calls) for stated goals, timeline pressure, and technical constraints mentioned pre-sale. - Check notes (
get-notes) and the closed opportunity (search-opportunities) for scope: which products/tiers were bought, any services attached. - Draft the kickoff structure:
- Confirm success criteria (bring the sales-cycle version; ask them to sharpen it into measurable outcomes)
- Map roles: their implementation owner, our owner, escalation paths both ways
- Propose milestones backward from their target date: technical setup → first value moment → team rollout → success review
- Identify the fastest path to a first "aha" — the single workflow that proves value earliest
Output Format
Kickoff prep: {Customer}
Attendee map — who's coming, who's missing, roles to confirm
Draft agenda — timed, 45-60 min, confirmation-oriented (they talk more than we present)
Success criteria to validate — from the sales cycle, phrased as questions
Proposed milestone plan — table: milestone, target date, owner, definition of done
Risks going in — missing stakeholders, unrealistic timelines, scope ambiguity
Guidelines
- A kickoff that's a product demo is a failure — the product was sold already; the meeting sells the plan.
- Every milestone needs a customer-side owner. No customer owner = flag as top risk.
- Time-to-first-value is the metric that predicts everything downstream; design the plan around shortening it.
Related skills: context from the sales cycle → sales-handoff; watching the first 90 days → onboarding-stall.