# 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.

## Install

```bash
npx skillstore add larksuite/lark-drive
```

## Metadata

- Status: approved
- Slug: larksuite-lark-drive
- Version: 1.0.0
- Author version: 1.0.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 6bd95e6b59d3fdfa57d294f616c8a4e409cdcf8011fab989957d951a69c11e03
- Author: larksuite
- GitHub username: larksuite
- License: MIT
- Repository: https://github.com/larksuite/cli/tree/main/skills/lark-drive/
- Ref: ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, network, filesystem, env\_access
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/larksuite-lark-drive
- Manifest: https://skillstore.pages.dev/api/skills/larksuite-lark-drive/manifest

## Capabilities

- Search Lark Drive and Wiki resources by title, owner, type, and activity filters.
- Upload, download, import, export, preview, and inspect supported Drive resources.
- Create folders, copy resources, move items, and build shortcuts with token-aware routing.
- Manage comments, reactions, permission requests, collaborators, public settings, security labels, and ownership workflows.
- Compare, pull, push, and synchronize local files with Drive folders using documented conflict controls.
- List, download, revert, and delete supported file versions.

## Use Cases

- 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.

## Prompt Templates

### 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.
```

## Limitations

- Requires installed lark-cli and valid Lark or Feishu authentication, scopes, and resource access.
- Does not edit document bodies, spreadsheet cells, Base records, or Wiki hierarchy content.
- Some operations depend on tenant rollout, document type, identity mode, API limits, and organization policy.
- Destructive and permission-changing operations require explicit confirmation and may not provide complete rollback.

## 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.

## Anti Patterns

- 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.

## Security Audit

- Audited at: 2026-07-23T16:14:08.741\+00:00
- Summary: 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.

## Stats

- Views: 96
- Downloads: 15
- Favorites: 1
- Popularity score: 0