A set of capabilities for creating party activities, getting party venue recommendations, inviting friends to attend, and viewing party details.
Trigger scenarios
Examples of user utterances (routing hits this skill):
- "Help me organize a party"
- "I want to throw a birthday party this weekend"
- "What places are good for parties that you can recommend"
- "Recommend a few party houses"
- "Help me invite friends to the party"
- "Let me see my party details"
- "Create a weekend dinner gathering activity"
Out of scope
- Requests such as in-store queue number taking, online ordering, and order payment → not within the scope of this skill; handled by the queue/order skill
- Requests such as map navigation, route planning, and taxi travel → not within the scope of this skill
- Requests such as historical orders, membership points, and coupons → not within the scope of this skill
API flow
createParty: Create a party activity, filling in basic information such as party name, date, and time.getRecommendations: Get party venue recommendations (restaurants/party houses/KTVs/outdoor, etc.).inviteFriends: Select friends and initiate invitations.getPartyDetails: View complete party details (including member status).
Usage order
- Before creating a party, the party name, date, and time must first be determined; when necessary information is missing, guide the user to supplement it.
- Before getting recommendations, the user should not have a specific venue; when a specific venue is already available, recommendations should no longer be called.
- Before inviting friends, there must first be a created party; when there is no partyId, create the party first.
- Before viewing party details, there must be a valid partyId; when there is none, create or select a party first.
- All APIs with bound components should prioritize displaying cards, and should not be changed to plain text expanded item by item.