lark-markdown
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "lark-markdown" from https://skillstore.io/skills/larksuite-lark-markdown.md and its manifest at https://skillstore.io/api/skills/larksuite-lark-markdown/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.
Test it
Using "lark-markdown". Fetch the remote README and show its content.
Expected outcome:
The README was retrieved successfully. It contains the project overview, installation steps, and contribution guidelines.
Using "lark-markdown". Compare the latest remote file with my local draft.
Expected outcome:
The files differ. The local draft adds three lines, removes two lines, and changes one installation step.
Using "lark-markdown". Replace the old release label and preview the update.
Expected outcome:
The preview found one match. The final file remains nonempty, and no remote version was uploaded.
Security Audit
Medium RiskSix 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.
Confirmed security concerns (2)
Capability review items (6)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
🌐 Network access (2)
📁 Filesystem access (24)
⚙️ External commands (30)
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.
Copy report link
https://skillstore.io/skills/larksuite-lark-markdown/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/larksuite-lark-markdown?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/larksuite-lark-markdown?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/larksuite-lark-markdown/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/larksuite-lark-markdown.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-markdown security audit report (audit version 5) [Author version 1.2.2]. Skillstore. https://skillstore.io/skills/larksuite-lark-markdown/audits/5BibTeX citation
@techreport{larksuite-larksuite-lark-markdown-2026,
author = {larksuite},
title = {lark-markdown security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/larksuite-lark-markdown/audits/5},
note = {Author version 1.2.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "lark-markdown security audit report (audit version 5)"
version: "1.2.2"
type: report
authors:
- name: "larksuite"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/larksuite-lark-markdown/audits/5"
identifiers:
- type: other
value: "skillstore:larksuite-lark-markdown:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Fetch the Lark Markdown file with token {file_token}. Return its content without saving a local copy.Create a native Markdown file from {local_file} in Drive folder {folder_token}. Preview the request before creating it.Compare remote file {file_token} at version {version} with {local_file}. Summarize additions and deletions without changing either file.Preview one RE2 patch on {file_token}. Replace {pattern} with {replacement}, explain escaping, and do not upload until I confirm.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.
Avoid
- 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.
Frequently Asked Questions
Can this skill create a Lark online document?
Can it save a remote file locally?
Can it compare two historical versions?
Does patch change only one server-side section?
Can one patch apply several different replacements?
Which identity should I use?
Developer Details
Author
larksuiteLicense
MIT
Author version
v1.2.2
Skillstore revision
r2
Ref
ebdfe608f5de2b66ff37ab4af12af8ac4f5e8006
Maintenance freshness
7/25/2026
Usage
3 downloads · 81 views
File structure