Skills lark-drive

📦

lark-drive

Name: lark-drive
Author: larksuite

v1.0.0 Content revision r2 Safe ⚙️ External commands🌐 Network access📁 Filesystem access🔑 Env variables

Manage Lark Drive Files and Permissions

Lark Drive work often requires many commands and careful token handling. This skill guides safe file, folder, comment, version, and permission workflows through lark-cli.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "lark-drive" from https://skillstore.io/skills/larksuite-lark-drive.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-drive/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/larksuite-lark-drive.md Signed manifest GET /api/skills/larksuite-lark-drive/manifest Signed lockfile GET /api/skills/larksuite-lark-drive/lockfile

Test it

Using "lark-drive". Find files I edited this week containing quarterly plan.

Expected outcome:

Found six matching resources across Drive and Wiki.
The top result is Quarterly Plan, edited yesterday and owned by Finance.
Two resources were excluded because access was denied.

Using "lark-drive". Check whether this document is publicly accessible.

Expected outcome:

The document allows company-wide link viewing.
External access is closed, and public internet access was not found.
Collaborator membership and audit history were outside this check.

Using "lark-drive". Compare my local release folder with the Drive release folder.

Expected outcome:

Three local files are new, one remote file is newer, and two files match.
No changes were made.
Review the newer remote file before selecting a synchronization policy.

Security Audit

Safe

v5 • 7/23/2026 Open versioned report

All 390 static findings are false positives caused by Markdown syntax, placeholder URLs, Chinese text entropy, or documented CLI examples. The package contains guidance files only, with no executable source, encoded payload, or prompt injection evidence. Destructive and permission-changing workflows include confirmation, dry-run, scope, or path-containment controls.

Files scanned

6,077

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (50)

🌐 Network access (31)

📁 Filesystem access (50)

🔑 Env variables (1)

references/lark-drive-workflow-knowledge-organize-rollback.md:7

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/larksuite-lark-drive/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/larksuite-lark-drive/security.svg)](https://skillstore.io/skills/larksuite-lark-drive?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/larksuite-lark-drive?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-drive/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/larksuite-lark-drive.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

larksuite. (2026). lark-drive security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/larksuite-lark-drive/audits/5

BibTeX citation

@techreport{larksuite-larksuite-lark-drive-2026,
  author = {larksuite},
  title = {lark-drive security audit report (audit version 5)},
  institution = {Skillstore},
  year = {2026},
  number = {5},
  url = {https://skillstore.io/skills/larksuite-lark-drive/audits/5},
  note = {Author version 1.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-drive security audit report (audit version 5)"
version: "1.0.0"
type: report
authors:
  - name: "larksuite"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/larksuite-lark-drive/audits/5"
identifiers:
  - type: other
    value: "skillstore:larksuite-lark-drive:audit:5"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Organize a shared Drive

Inventory folders, identify duplicates or temporary content, and prepare a confirmed organization plan.

Review access exposure

Assess public links, external access, security labels, and ownership before proposing permission changes.

Synchronize project files

Compare local files with Drive, resolve conflicts, and transfer approved changes with clear results.

Try These Prompts

List a folder

List the files in this Lark Drive folder: [URL]. Show names, types, paths, and access errors. Do not modify anything.

Upload a file

Upload [local file] to [folder URL]. Inspect the target first, use the correct token type, and ask before any overwrite.

Plan a synchronization

Compare [local directory] with [Drive folder URL]. Report new, modified, and conflicting files. Propose a synchronization plan without changing either side.

Audit permissions

Audit permissions for [scope]. Identify public links, external access, ownership concerns, and missing evidence. Produce a remediation plan, then wait for confirmation.

Best Practices

Inspect URLs and tokens before selecting a command or resource type.
Use read-only checks and dry runs before uploads, moves, permission changes, or synchronization.
Confirm exact targets, identities, scopes, and conflict policies before high-impact operations.

Avoid

Do not treat Wiki node tokens as Drive file tokens without inspection.
Do not bypass confirmation for deletes, ownership transfers, broad permission changes, or remote cleanup.
Do not use this skill for document body editing, spreadsheet cells, Base records, or Wiki hierarchy changes.