# Manage Lark Markdown Files

Managing native Markdown across Lark Drive and local drafts requires several precise commands. This skill guides safe creation, retrieval, comparison, patching, and replacement.

## Install

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

## Metadata

- Status: approved
- Slug: larksuite-lark-markdown
- Version: 1.2.2
- Author version: 1.2.2
- Skillstore revision: r2
- Version status: valid
- Tree hash: 2cd6a678c6aeefbad43cf93e9e34283cd27ba11d1678f3ceef0971c90050308e
- Author: larksuite
- GitHub username: larksuite
- License: MIT
- Repository: https://github.com/larksuite/cli/tree/main/skills/lark-markdown/
- 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: network, filesystem, external\_commands
- Quality score: 50
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/larksuite-lark-markdown
- Manifest: https://skillstore.pages.dev/api/skills/larksuite-lark-markdown/manifest

## Capabilities

- Creates native Markdown files in a Lark Drive folder or Wiki node.
- Fetches remote Markdown content and can save it to a local path.
- Compares two remote versions or a remote version with a local draft.
- Applies one literal or RE2 regular expression replacement to a remote file.
- Overwrites remote Markdown using inline content, a local file, or standard input.
- Supports user and bot identities when the available permissions allow them.

## Use Cases

- Publish Project Notes: Create a native Markdown file from a local project note and place it in the correct Drive folder.
- Review Documentation Changes: Compare a remote Markdown version with a local draft before replacing shared documentation.
- Update Repeated Content: Apply a controlled literal or regular expression replacement across one remote Markdown file.

## Prompt Templates

### Read a Remote File

```
Fetch the Lark Markdown file with token {file_token}. Return its content without saving a local copy.
```

### Create from a Local Draft

```
Create a native Markdown file from {local_file} in Drive folder {folder_token}. Preview the request before creating it.
```

### Compare Before Publishing

```
Compare remote file {file_token} at version {version} with {local_file}. Summarize additions and deletions without changing either file.
```

### Preview a Regular Expression Patch

```
Preview one RE2 patch on {file_token}. Replace {pattern} with {replacement}, explain escaping, and do not upload until I confirm.
```

## Limitations

- It handles native Markdown files, not imported Lark docx documents.
- It does not manage search, permissions, comments, moves, renames, or deletion.
- Patch supports one replacement group and is not an atomic remote update.
- It requires lark-cli, valid authentication, and access to the target Drive resource.

## Best Practices

- Use dry-run before create, overwrite, or regular expression patch operations.
- Prefer user identity for files owned in a user's cloud space.
- Compare the latest remote version before overwriting shared content.

## Anti Patterns

- Do not guess whether a token belongs to a Drive folder or Wiki node.
- Do not use an unescaped regular expression for literal punctuation.
- Do not treat patch as atomic when other users may edit the file.

## Security Audit

- Audited at: 2026-07-23T16:35:39.83\+00:00
- Summary: Six path findings are confirmed because the skill mandates loading sibling instructions outside the audited package. Other static detections are documentation syntax, placeholder URLs, or plain Markdown, while two medium data-integrity and permission risks were found semantically.

## Stats

- Views: 81
- Downloads: 7
- Favorites: 0
- Popularity score: 0