Security audit
Security checks for vulnerabilities and agentic risk
The skill is a coherent meeting-notes helper, but its optional integration guide includes third-party AI processing and bulk Jira issue creation without clear consent or confirmation safeguards.
Install only if you are comfortable using it as a meeting-summary template and review any generated action items before sharing. Do not let an agent sync notes, send bot messages, upload transcripts, or create Jira/Linear issues unless you have participant consent, approved vendors, scoped tokens, and explicit confirmation for each external write.
The meeting summary template, extraction rules, priority labels, checklist, output format, and tips are primarily written in Chinese or bilingual Chinese-first form. This effectively steers the skill toward Chinese output and workflow conventions without explicit user opt-in or a stated language-selection mechanism.
The listed Chinese weak triggers include broad phrases like "我们应该...", "可以考虑...", and "最好能...", which commonly appear in ordinary discussion and do not clearly distinguish actionable commitments from general brainstorming. The guide labels them as triggers without giving exclusion criteria or negative examples, making activation scope ambiguous.
Phrases such as "We should probably...", "It would be good if...", and "Someone needs to..." are broad conversational forms that often express ideas rather than agreed tasks. Because the document provides no explicit boundaries or non-trigger examples, the extraction criteria are likely to fire on ambiguous discussion.
The manifest describes a skill for organizing meeting notes, extracting action items, and generating structured summaries from transcripts or notes. This file documents behavior that pushes outputs into external collaboration and project-management systems, including bot-delivered summaries and automatic Jira issue creation, which is broader than pure note processing.
The Python example uses a bearer token and sends POST requests to create Jira issues. For a skill presented as transforming meeting notes into structured summaries and action items, authenticated issue creation in an external system is an additional capability that is not explicitly justified by the manifest description.
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
}
}
response = requests.post(
f"{jira_config['base_url']}/rest/api/3/issue",
json=payload,
headers=headers
The workflow recommends sending recordings or transcripts to third-party AI services without mentioning consent, data classification, retention, or confidentiality controls. Meeting notes often contain personal data, internal strategy, and customer information, so omission of privacy safeguards can lead to unauthorized disclosure or policy violations.
The document specifies trigger recognition only for Chinese and English and does not state whether other languages are unsupported by design or whether the user can choose locale behavior. This can create a language-policy concern if the skill is applied in multilingual contexts without explicit opt-in or limitation.
The embedded prompt explicitly specifies "语言：中文", which forces a specific language choice in natural-language instructions. The file does not state that this guide is intentionally China/Chinese-only or offer an option to choose another language.
The title explicitly labels the file as a Chinese meeting-template collection, and the entire template content is written only in Chinese. Because this is natural-language guidance rather than a clearly documented region-specific compliance artifact, it imposes a locale/language constraint without user opt-in.