lark-drive Eval
===============

Status: failed
Score: 73/100
Risk: high
Decision: do_not_auto_install
Policy: block
Reason: Permission surface: secrets or environment access, shell or command execution

Install:
npx skills add larksuite/cli --skill lark-drive

Required checks:
- PASS Task fit: Task wording matches this skill metadata.
- PASS Install path: Install handoff is available.
- PASS Install command safety: standard package or runtime install path
- WARN Trust score: Potentially useful, but at least one trust signal needs human inspection.
- WARN Audit score: Needs review
- WARN Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- PASS License clarity: MIT
- FAIL Permission surface: secrets or environment access, shell or command execution

Warnings:
- Trust score: Potentially useful, but at least one trust signal needs human inspection.
- Audit score: Needs review
- Agent safety gate: Sparse or mixed signals. Useful for discovery, but not for autonomous installation.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- The SKILL.md depends on ../lark-shared/SKILL.md for authentication, permissions, and safe execution rules, but that file is outside the submitted skill directory. If the skill bundle does not include lark-shared, the instructions will be incomplete at runtime.
- The provided excerpt is truncated at the end, making it unclear whether the full SKILL.md includes all remaining routing rules and safety boundaries; the visible content is otherwise thorough.
- Several high-risk operations are documented as requiring explicit user confirmation and --yes, but some shortcut descriptions still allow broad natural-language triggers that require the agent to correctly decide when to stop. This is mitigated by the workflow references, but remains an operational risk if those references are not read.
- Quality score needs review
- Permission surface needs review: secrets or environment access, shell or command execution
- Dependency/runtime risk: command execution surface, credential or environment access

Validation plan:
1. Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. Install in an isolated workspace or sandbox with no production secrets available.
3. Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. Compare the selected skill against at least one alternative when the eval status is review or failed.
5. Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when:
- teams that need a vendor-supported SLA
- production agents without a repository review
- The SKILL.md depends on ../lark-shared/SKILL.md for authentication, permissions, and safe execution rules, but that file is outside the submitted skill directory. If the skill bundle does not include lark-shared, the instructions will be incomplete at runtime.
- High-risk permission hints: Shell or command execution, Secrets or environment access
- Dependency or permission surface needs review
- Permission surface may require sandboxing
- The provided excerpt is truncated at the end, making it unclear whether the full SKILL.md includes all remaining routing rules and safety boundaries; the visible content is otherwise thorough.
- Several high-risk operations are documented as requiring explicit user confirmation and --yes, but some shortcut descriptions still allow broad natural-language triggers that require the agent to correctly decide when to stop. This is mitigated by the workflow references, but remains an operational risk if those references are not read.

URLs:
- Skill: https://www.openagentskill.com/skills/larksuite-lark-drive
- Audit: https://www.openagentskill.com/skills/larksuite-lark-drive/audit
- JSON: https://www.openagentskill.com/api/agent/evals?slug=larksuite-lark-drive