会议纪要AI整理器 Meeting Notes Pro
v1.0.05秒钟把会议录音/文字转成标准纪要，自动提取决议事项、待办任务和负责人
⭐ 0· 71·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
medium confidencePurpose & Capability
Name/description (convert meeting audio/text into structured minutes, extract decisions/tasks/owners) match the SKILL.md workflow. No unexpected binaries, credentials, or installs are requested; the skill relies on user-provided content (paste or text) which is appropriate for the described purpose.
Instruction Scope
Instructions remain within the meeting-notes domain (parse text, extract items, format Markdown). However, the SKILL.md repeatedly instructs the agent to 'remember' user preferences, department/role info, and participant names — this implies persistent storage of personal/company data. The skill does not direct data to external endpoints, nor request system files, but the memory requirement is scope-expanding and has privacy implications.
Install Mechanism
No install spec and no code files (instruction-only). This minimizes supply-chain risk — nothing is downloaded or written to disk by the skill itself.
Credentials
No environment variables, credentials, or config paths are required. Requested access is proportional to the stated capability.
Persistence & Privilege
The skill specifies automatic learning/memory (storing preferences, participant names, department info). While it doesn't set always:true or request extra system privileges, persistent memory of potentially sensitive PII is a real concern — users should confirm where/how this data is stored and how to view/delete it. Agent autonomous invocation is default and not inherently problematic here.
Assessment
This skill appears to do what it promises (turn meeting text into structured minutes) and has low technical risk because it contains no code or installs. Main considerations before installing: 1) Privacy — the skill's instructions say it will 'remember' participants, roles, and user preferences; confirm how the platform stores and lets you delete that memory and get consent from meeting participants before pasting sensitive PII. 2) Data handling — avoid pasting confidential content until you understand retention/visibility. 3) Validation — always review generated decisions, owners, and deadlines for hallucinations or incorrect attributions. 4) Integrations — the SKILL.md mentions inputs from WeChat/Feishu/email conceptually but provides no connectors; if you later enable integrations, re-evaluate permissions. Test first with non-sensitive sample meetings and ask the vendor/platform where memory is persisted and how to opt out.Like a lobster shell, security has layers — review code before you run it.
latestvk973qh11pyr00dkextpsjt9ne983qrjm
License
MIT-0
Free to use, modify, and redistribute. No attribution required.