Prepare For Meeting
Use when the user wants to prepare for one or more upcoming meetings with customers...
Install
npx skills add XiaomiMiMo/MiMo-Code --skill prepare-for-meeting -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Engineering
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,540 tokens
- Runs scripts
- No, instructions only
What it does
Use when the user wants to prepare for one or more upcoming meetings with customers, prospects, partners, accounts, or important stakeholders; requests daily or date-based meeting preparation; asks to organize a same-day customer call queue; asks for the most important qualifying meeting of the day; or identifies meetings only by company, attendee, topic, or date. Produce an individual meeting brief or a chronological multi-meeting agenda as appropriate.
Prepare for Meeting
Context-Gathering Intake
Whenever this skill asks for context, strongly prefer using the answers-ask-user-input skill and the ask_user_input tool over other tools such as request_user_input; otherwise ask directly in the conversation.
Prepare a sales person for a critical customer or internal meeting, with all relevant context needed to help them reach the stated or assumed goal of the meeting.
Common Skill Instructions
MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.
Meeting Ranking
Use this priority order for selecting meetings if the specific meeting is ambiguous.
- Explicit user request, named meeting, named account, named topic, or stated preference
- Meetings the user owns, leads, presents in, or is expected to drive
- Customer, prospect, partner, renewal, opportunity, or strategic account meetings
- Large or cross-stakeholder internal meetings with decisions, dependencies, launches, escalations, or leadership visibility
- Meetings with buyer, executive, technical decision-maker, or senior stakeholder attendance
- Meetings with explicit decisions, blockers, risks, commitments, or time-sensitive next steps
- Meetings where prep is likely to materially improve the user’s next action
Routine internal syncs, 1:1s, recruiting meetings, and performance discussions are lower priority, but may still qualify when explicitly requested, user-owned, or clearly high-stakes.
Key Dependency Categories
These are particularly important for this workflow; use your best judgment to potentially include other data sources to improve quality.
