Security audit
Security checks for vulnerabilities and agentic risk
This meeting-assistant skill is coherent and purpose-aligned, but users should understand that meeting records are saved locally in plain JSON.
Install only if local plain-text storage of meeting details is acceptable for your environment. Avoid using it for confidential meetings on shared or backed-up machines unless you add deletion, access-control, or encryption practices yourself.
The invocation examples "整理会议纪要", "提取待办事项", and especially "安排下周会议" are generic natural-language requests without any explicit trigger scope, constraints, or exclusion conditions. In a manifest-like skill description, this makes it unclear when the skill should activate versus when a user is simply discussing routine work tasks, increasing the risk of unintended invocation.
The skill explicitly stores meeting records in a local JSON file under a user workspace, and meeting notes commonly contain sensitive business information, attendee identities, action items, and timelines. The documentation does not warn about local persistence, retention, access control, or handling of confidential content, which can lead to unintentional exposure on shared machines or insecure environments.
The skill's docstring, command examples, output text, and trigger matching are all written for Chinese-language use, with no indication that users may choose another language or that the restriction is intentional. This can constitute a language/locale policy issue because the skill effectively forces one language without opt-in.
Meeting notes and minutes can contain sensitive business data, attendee names, action items, and internal decisions. This function persists that content to local JSON storage automatically without consent, disclosure, retention controls, or access protections, creating privacy and confidentiality risk if the host environment is shared, backed up, or otherwise accessible.
The natural-language instructions and usage examples are presented only in Chinese, with no indication that users may choose another language or locale. This can be a language/locale policy concern when a skill implicitly requires a specific language without opt-in or justification.
The skill title, trigger rules, feature descriptions, and example dialogue are all presented in Chinese, with no indication that users may choose another language. This can violate language/locale policy when a skill implicitly constrains interaction language without opt-in or justification.
The module docstring states that the assistant supports speech-to-text, alongside meeting notes, action items, scheduling, and templates. However, the code only processes text inputs, JSON persistence, parsing, formatting, and statistics; there is no audio input, transcription library, or related logic anywhere in the file.
Persisting created meetings to disk without user awareness can expose schedules, participant lists, and locations. In this skill's context, that metadata may reveal internal operations or personal information, though it is typically less sensitive than full meeting notes.
