Operational rules are mandatorily delegated to another skill that was not supplied for audit
Source references: 3The entry explicitly requires the agent to read and execute ../lark-meeting/SKILL.md in full, but that source is absent from the submitted material. Reviewing this wrapper alone therefore cannot reveal which files, credentials, or Lark account actions will be requested or whether they match the user's request.
If the environment's lark-meeting skill is substituted, version-mismatched, or over-privileged, invoking lark-note inherits that behavior; the visible wrapper places no limits on operations or permission scope.
This skill does not handle the task itself; it requires the agent to read and follow a `lark-meeting` skill that is absent from the supplied material. When a user or upstream configuration explicitly invokes `lark-note`, that external skill determines any file, credential, or Lark-account actions, so this entry alone cannot establish their scope or authorization. Before enabling it, the user can request a separate audit of `../lark-meeting/SKILL.md` and restrict accessible files, credentials, and account permissions.
version: 1.0.0description: "仅当用户或上游配置显式指定 lark-note 时使用，相关请求统一交由 lark-meeting 技能处理。"metadata: requires: bins: ["lark-cli"] skills: ["lark-meeting"]---Show 2 other places
本技能只用于兼容旧名称，不直接处理业务。**MUST 完整读取 [`../lark-meeting/SKILL.md`](../lark-meeting/SKILL.md)，并按照其中的路由和行动指南执行。** bins: ["lark-cli"] skills: ["lark-meeting"]---