Display Name: ChatMerge - 智能多渠道聊天纪要助手

What to check before installing or enabling this skill: - Metadata mismatch: the registry claims no required env vars, but docs show the skill needs many tokens (chat platforms, Jira/Notion/GitHub, calendar, meeting APIs). Ask the publisher to declare exactly which credentials the skill will access and why. - Where tokens live: the QUICKSTART instructs editing ~/.openclaw/openclaw.json; the skill's allowed-tools include read/write, so the agent could read that file. Verify what is stored there and prefer putting minimal, scoped tokens (least privilege) or using per-integration limited scopes. - Integrations: if you enable automatic creation of Jira/Notion/GitHub items, provide tokens with narrowly scoped permissions (e.g., allow issue creation but not admin access), and avoid sharing broad admin tokens. - Persistent monitoring and scheduling: enabling those features grants ongoing access to channels. If you don't want continuous access, use one-shot modes (file import or manual paste) instead of enabling monitoring or scheduled tasks. - Posting capability: the skill may post messages or ask clarifying questions in channels. Confirm whether you want it to post autonomously and review its confirmation/approval behavior (auto-create vs. require explicit confirmation). - Audit and logs: ask how the skill records its actions (task creations, notifications). Despite claims of 'no storage', scheduling/monitoring and incremental updates typically require storing some state; confirm where state is stored and retention policies. If you are not comfortable granting channel/config access or providing integration tokens, prefer using manual file import or paste mode, and only enable integrations one at a time with least-privilege credentials. Finally, request the maintainer to update registry metadata to list required env vars and config paths so you can make an informed decision.