← 웨딩플로우CONTENT HISTORY
WHAT CHANGED
Update to 웨딩플로우
Snapshot Nov 2, 2026 · 06:11 UTC · version 2.1.0
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save 웨딩플로우 and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "내 정보, 활동 배지, 티켓, 결혼 조사, 플랜, 웨딩 메시지 기록과 남은 메시지 사용량을 볼 때 사용한다. Use when the user asks who they are in WeddingFlow, their badges, tickets, marriage survey, plans, or saved planner messages. Do not use to send gifts or generate an in-app AI reply.",
"included_files": [],
"name": "wedding-account",
"skill_md_contents": "---\nname: wedding-account\ndescription: 내 정보, 활동 배지, 티켓, 결혼 조사, 플랜, 웨딩 메시지 기록과 남은 메시지 사용량을 볼 때 사용한다. Use when the user asks who they are in WeddingFlow, their badges, tickets, marriage survey, plans, or saved planner messages. Do not use to send gifts or generate an in-app AI reply.\n---\n\n# WeddingFlow account\n\nAnswer in Korean. Profile and entitlement data come from the MCP server. Do not infer a wedding date, partner, or ticket balance that the tool did not return.\n\n## Tools\n\n| Intent | Tool |\n| --- | --- |\n| Signed-in profile | `get_api_v1_auth_me` |\n| Activity badges | `get_api_v1_activity_badge` |\n| Unseen badges | `get_api_v1_activity_badge_unseen` |\n| Tickets | `get_api_v1_ticket`, `get_api_v1_ticket_by_ticket_id` |\n| Received and sent ticket gifts | `get_api_v1_ticket_gift_received`, `get_api_v1_ticket_gift_send` |\n| Marriage survey and stats | `get_api_v1_survey`, `get_api_v1_survey_statistic` |\n| Plans | `get_api_v1_plan` |\n| Saved planner messages | `get_api_v1_message` |\n| Message usage | `get_api_v1_message_usage` |\n\nStart account questions with `get_api_v1_auth_me` when the wedding, name, or permission is unclear. Keep list sizes at 20 or below.\n\nWhen the user asks who the connected WeddingFlow account is, call `get_api_v1_auth_me` and answer with `email` and `name`. If `name` is empty, say the name is not set and still give the email. Do not mention a numeric user id. Do not send the user to My Page when the tool returned `email` or `name`.\n\n## Limits\n\nThis connection cannot edit the profile, withdraw, invite a partner, send or issue a gift, or mark a badge as seen. Gift tools here are read-only lists.\n\n`get_api_v1_message` is the saved WeddingFlow planner thread, not this ChatGPT conversation. `get_api_v1_message_usage` reports remaining usage. Do not call `post_api_v1_message` to store this chat, and do not claim an in-app AI reply was generated. That generation tool is not available. If the user explicitly asks to save one message into WeddingFlow, confirm the exact `content` first and explain that it only stores the message.\n\nIf OAuth is required, use the host flow. Never ask the user to paste a token. Hide password, token, and secret fields if any appear in a result.\n"
}SHA-256 of public snapshot: 245bc9e947a0d9e0e09c7f656d4dcd699b6ef74e6b700a7316672f9898839c62