Directly inserting a dynamic report into a shell-quoted argument can enable command injection
Source references: 1The cloud-document commands carry the dynamic report in `$'<内容>'`. If an executor substitutes meeting-derived text directly into this shell template, a single quote in that text can terminate the quoting early; following shell operators or commands may then be interpreted by the terminal instead of being document content.
A crafted meeting title, transcript passage, or report fragment could execute local commands with the agent user's privileges, potentially reading or changing accessible files and credentials. Ordinary apostrophes can also make document creation fail.
The file does show a shell template that passes dynamic body text through ANSI-C single quotes (`$'…'`); an unescaped single quote could alter shell parsing. However, the evidence is only a placeholder example, with no script or instruction requiring raw meeting text to be concatenated into it, so unsafe interpolation is not established. A user can ask the author to require file/stdin or structured JSON input and explicitly forbid direct placeholder substitution.
This assessment concerns the code and conditions shown, not proof that harm has occurred.### Step 5: 生成文档(可选,用户要求时)阅读 [`../lark-doc/SKILL.md`](../lark-doc/SKILL.md) 学习云文档技能。```bashlark-cli docs +create --doc-format markdown --content $'<title>会议纪要汇总 (<start> - <end>)</title>\n<内容>'# 或追加到已有文档lark-cli docs +update --doc "<url_or_token>" --command append --doc-format markdown --content $'<内容>'```