Agent skill

Verify Openlark

Prove OpenLark (Feishu/Lark Rust SDK) changes the way a maintainer does — cargo build/test, public examples, API coverage and field-verify harnesses.

Apache-2.0Auto-check passedProductivity & Automation

Install Verify Openlark

skills CLI

$ npx skills add foxzool/openlark --skill verify-openlark -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install foxzool/openlark verify-openlark --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/foxzool/openlark.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/verify-openlark .claude/skills/verify-openlark && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "verify-openlark" agent skill from https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark into .claude/skills/verify-openlark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-openlark", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add foxzool/openlark --skill verify-openlark -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install foxzool/openlark verify-openlark --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/foxzool/openlark.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.cursor/skills/verify-openlark .agents/skills/verify-openlark && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "verify-openlark" agent skill from https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark into .agents/skills/verify-openlark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-openlark", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add foxzool/openlark --skill verify-openlark -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install foxzool/openlark verify-openlark --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/foxzool/openlark.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.cursor/skills/verify-openlark .cursor/skills/verify-openlark && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "verify-openlark" agent skill from https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark into .cursor/skills/verify-openlark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-openlark", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/foxzool/openlark.git --path .cursor/skills/verify-openlark

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add foxzool/openlark --skill verify-openlark -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install foxzool/openlark verify-openlark --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/foxzool/openlark.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.cursor/skills/verify-openlark .gemini/skills/verify-openlark && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "verify-openlark" agent skill from https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark into .gemini/skills/verify-openlark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-openlark", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install foxzool/openlark verify-openlark

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add foxzool/openlark --skill verify-openlark -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/foxzool/openlark.git skills-src && mkdir -p .github/skills && cp -r skills-src/.cursor/skills/verify-openlark .github/skills/verify-openlark && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "verify-openlark" agent skill from https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark into .github/skills/verify-openlark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-openlark", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add foxzool/openlark --skill verify-openlark -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install foxzool/openlark verify-openlark --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/foxzool/openlark.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.cursor/skills/verify-openlark .opencode/skills/verify-openlark && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "verify-openlark" agent skill from https://github.com/foxzool/openlark/tree/main/.cursor/skills/verify-openlark into .opencode/skills/verify-openlark/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "verify-openlark", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: verify-openlark
GitHub stars: 106
Token cost: ~1.8k tokens
SKILL.md length: 651 words
Files: 9 (incl. scripts)
Skills in repo: 8
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Prove OpenLark (Feishu/Lark Rust SDK) changes the way a maintainer does — cargo build/test, public examples, API coverage and field-verify harnesses.

Verifying a library change
SKILL.md covers Launch, Doctor, Drive and Evidence, plus 3 more sections
Calls cargo, python3 and bash
Before claiming an SDK fix works

What it does

Verify Openlark is an agent skill from foxzool/openlark. Prove OpenLark (Feishu/Lark Rust SDK) changes the way a maintainer does — cargo build/test, public examples, API coverage and field-verify harnesses. Use when verifying a library change, before claiming an SDK fix works, or when asked to drive OpenLark verification.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts (for example `features/README.md`, `features/api-coverage.md` and `features/api-field-verify.md`).

It sits in Productivity & Automation, covering Messaging and chat bots. It works with Feishu (Lark) and Rust. The repository describes itself as: 飞书开放平台的非官方 Rust SDK，支持自定义机器人、长连接机器人、云文档、飞书卡片、消息、群组等 API 调用。 The licence is Apache-2.0.

When your agent uses it

Verifying a library change
Before claiming an SDK fix works
Asked to drive OpenLark verification

Example prompts

“/verify-openlark”

Requirements

Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit 6128d6d. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/, which the agent can run.
Shell commands in SKILL.md call:
- cargo
- python3
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Verify Openlark loads about 1.8k tokens when it runs. Until then it costs about 71 tokens; SKILL.md has 651 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~71
When it runs · the whole SKILL.md, loaded when a task matches: ~1.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from foxzool/openlark at commit 6128d6d, republished under its Apache-2.0 licence (© foxzool). 651 words, ~1,777 tokens.

Download SKILL.mdSave it as .claude/skills/verify-openlark/SKILL.md (or your agent's skills folder). This skill also uses 8 other files; get the full folder from GitHub.

name: verify-openlark
description: Prove OpenLark (Feishu/Lark Rust SDK) changes the way a maintainer does — cargo build/test, public examples, API coverage and field-verify harnesses. Use when verifying a library change, before claiming an SDK fix works, or when asked to drive OpenLark verification.

Verify OpenLark

OpenLark is a Rust workspace library SDK, not a GUI or long-lived server. Verification means compiling and exercising the SDK the way maintainers do: cargo build/test, public examples (usually offline), and the Python harnesses under tools/. Read this skill cold mid-task; follow it literally.

Put control-openlark on PATH for the session:

bash

export PATH="$(pwd)/.cursor/skills/verify-openlark/scripts:$PATH"
# or from anywhere:
export PATH="/absolute/path/to/repo/.cursor/skills/verify-openlark/scripts:$PATH"

Evidence lives under .cursor/skills/verify-openlark/artifacts/<run-id>/ (override with VERIFY_OPENLARK_ARTIFACTS). Cleanup never deletes that tree.

Feature recipes: features/README.md. A proof that drives one convenient entry point is incomplete when the map lists others for the change under test.

Launch

There is no daemon to keep alive. Launch = toolchain ready + one workspace build so later drives share a warm target/.

bash

# Optional isolation (recommended when sharing a machine):
export CARGO_TARGET_DIR="/tmp/openlark-verify-$USER-$$"
control-openlark launch --target-dir "$CARGO_TARGET_DIR"
# Ready when the transcript ends with: READY workspace build finished
# Equivalent raw command:
#   cargo build --workspace --all-features

Teardown is control-openlark cleanup (see Cleanup). Do not leave isolated CARGO_TARGET_DIR trees forever; purge only paths under /tmp/openlark-verify-* via cleanup --purge-target.

If rustc is older than 1.88, upgrade before generating proofs (rustup update stable && rustup default stable). Edition 2024 requires a modern Cargo.

Doctor

Run first whenever anything looks off, and before the first drive of a run:

bash

control-openlark doctor

Doctor passes only when all of these hold:

Repo root contains Cargo.toml and crates/openlark-core
rustc / cargo / python3 on PATH
rustc major.minor ≥ 1.88
cargo metadata --no-deps succeeds (manifest parses)
Prints doctor=PASS and writes artifacts/<run-id>/doctor.txt

If OPENLARK_USER_SEARCH_NAME or OPENLARK_CHAT_SEARCH_NAME is set, doctor warns that examples may hit the live Feishu API — unset them for offline proofs.

Never drive a shared interactive cargo session you did not start for this verification run.

Drive

Prefer control-openlark over raw commands so transcripts land in the run evidence directory.

Intent	Harness command	Maintainer equivalent
Unit/integration tests	`control-openlark test` or `control-openlark test --package openlark-core --lib`	`cargo test --workspace --all-features`
Public example compile gate	`control-openlark example check`	`bash scripts/check-public-examples.sh`
Offline example run	`control-openlark example run client_setup --features "auth,communication"`	`cargo run --example client_setup --features "auth,communication"`
Typed API coverage	`control-openlark api-coverage --crate openlark-docs`	`python3 tools/validate_apis.py --crate openlark-docs`
Field sanity (offline)	`control-openlark field-verify --crate openlark-workflow`	`python3 tools/verify_api_fields.py --crate openlark-workflow`
Field vs live docs	`control-openlark field-verify --crate openlark-workflow --fetch-docs`	same + `--fetch-docs` (needs network; use project skill `openlark-api-field-verify` for SPA docs)
CI-style clippy	`control-openlark lint`	dual `cargo clippy` all-features + no-default-features `-Dwarnings`

Stable handles for this repo: crate names (openlark-core, openlark-docs, …), example names from root Cargo.toml [[example]], script paths scripts/check-public-examples.sh, tools/validate_apis.py, tools/verify_api_fields.py. Do not invent alternate entry points.

Deep field verification against Feishu SPA docs is owned by .agents/skills/openlark-api-field-verify/ — invoke that skill when --fetch-docs is insufficient; this verify skill only wraps the CLI gate.

Show full SKILL.md (254 more words)Show less

Evidence

Proof standards for a library SDK:

Exercise the maintainer path (cargo/examples/tools), not private test hooks that skip the public API surface you claim to fix.
Capture command + exit code + full stdout/stderr in artifacts/<run-id>/.
For mutations to API models, prove with cargo test on the affected crate and (when the change is coverage/fields) the matching Python harness.
Side effects: compiled binaries under CARGO_TARGET_DIR, reports under reports/api_validation/ (copied into evidence by api-coverage).
Mocks/wiremock inside unit tests are fine — they are the production-isolated boundary. Do not claim a live Feishu round-trip unless credentials and network were intentionally used and the transcript shows the response.
client_setup without OPENLARK_USER_SEARCH_NAME / OPENLARK_CHAT_SEARCH_NAME is an offline proof; observe that the transcript says those lookups were skipped — do not trust the example name alone if those env vars might be set.

Locate the current evidence directory:

bash

control-openlark evidence-path

Minimum artifact set for a claimed fix: doctor.txt, the drive transcript for the mapped feature you ran (test.txt, example-client_setup.txt, …), and exit status 0 on that drive.

Cleanup

bash

control-openlark cleanup                 # drop .run-state readiness markers only
control-openlark cleanup --purge-target  # also rm isolated /tmp/openlark-verify-* target dir

Rules:

Never pkill / kill by process name. This skill starts no long-lived processes; cargo/python children exit with the drive.
Never delete artifacts/ proof trees.
Do not cargo clean the developer's default target/ unless this run used an isolated CARGO_TARGET_DIR and --purge-target is set.

After cleanup, confirm evidence still exists at the path printed by evidence-path during the run (re-create path from artifacts/<run-id>/ listing if state was cleared).

Helpers

Executable: .cursor/skills/verify-openlark/scripts/control-openlark

bash

control-openlark doctor
control-openlark launch [--target-dir DIR]
control-openlark test [--package PKG] [--lib] [-- -- FILTER]
control-openlark example run NAME [--features FEATS]
control-openlark example check
control-openlark api-coverage [--crate NAME|--all-crates]
control-openlark field-verify --crate NAME [--fetch-docs] [--api-id ID]
control-openlark lint
control-openlark evidence-init [RUN_ID]
control-openlark evidence-path
control-openlark cleanup [--purge-target]

Maintenance

Keep the feature map honest with /maintain-verification-skill as the SDK surface changes (new examples, harness flags, MSRV bumps).

Files

SKILL.md and 8 other files (scripts) in .cursor/skills/verify-openlark of foxzool/openlark.

SKILL.md
.gitignore
features/README.md
features/api-coverage.md
features/api-field-verify.md
features/ci-lint.md
features/public-examples.md
features/workspace-build-test.md
scripts/control-openlark

Open the folder on GitHubat commit 6128d6d

Compare with similar skills

Verify Openlark next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Verify Openlark compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Verify Openlark this skillfoxzool/openlark	106	—	~1.8k	Automated safety check: Pass	Apache-2.0	6 days ago
Feishu Docopenclaw/openclaw	392k	—	~516	Automated safety check: Pass	MIT	today
Claude To Imop7418/Claude-to-IM-skill	2.9k	—	~3.4k	Automated safety check: Notes	MIT	6 mo ago
Feishu Docraucvr/Group-Goki	112	3 repos	~592	Automated safety check: Pass	MIT	4 mo ago
Feishu BridgeAlexAnys/feishu-openclaw	317	1 repos	~615	Automated safety check: Pass	None	6 mo ago
Content CollectorvigorX777/content-collector-skill	240	—	~2k	Automated safety check: Pass	None	6 mo ago

Similar skills

Feishu Doc
openclaw/openclaw
Feishu document read/write workflows. An agent skill from openclaw/openclaw.
392k GitHub stars~516 tokensUpdated today
Productivity & AutomationAuto-check passed
Claude To Im
op7418/Claude-to-IM-skill
Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone.
2.9k GitHub stars~3.4k tokensUpdated 6 mo ago
Productivity & AutomationAuto-check: notes
Feishu Doc
raucvr/Group-Goki
Feishu document read/write operations. An agent skill from raucvr/Group-Goki.
112 GitHub starsUsed in 3 repos~592 tokens
Productivity & AutomationAuto-check passed
Feishu Bridge
AlexAnys/feishu-openclaw
Connect a Feishu (Lark) bot to Clawdbot via WebSocket long-connection.
317 GitHub starsUsed in 1 repo~615 tokens
Productivity & AutomationAuto-check passed
Content Collector
vigorX777/content-collector-skill
Collect social media content (X/Twitter, WeChat, Jike, Reddit, etc.) into Feishu bitable.
240 GitHub stars~2k tokensUpdated 6 mo ago
Productivity & AutomationAuto-check passed
Feishu Rich Card Sender
xjtulyc/MedgeClaw
Sends interactive Feishu group-chat cards that mix markdown text with uploaded chart or diagram images, for progress updates and analysis results.
617 GitHub starsUsed in 1 repo~734 tokens
Productivity & AutomationAuto-check: notes

More from foxzool/openlark

All 8 skills in this repo

Openlark API
foxzool/openlark
OpenLark 项目 API 接口实现规范（速查）。用于添加/重构飞书开放平台 API：确定落盘路径、实现 Body/Response + Builder(Request)、对齐 endpoints 常量/enum、补齐 mod.rs 导出，并明确"调用服务端 API"的方法签名/RequestOption 传递约定。触发关键词：API 接口、API 文件、飞书 API、添加…
106 GitHub stars~3k tokensUpdated 6 days ago
Auto-check: notes
Openlark API Field Verify
foxzool/openlark
OpenLark API 字段核对技能。用于新增/重构飞书 API 后，核对 Rust 实现的请求体/响应体字段是否与飞书官方文档一致。通过 playwright 渲染飞书 SPA 文档页面，提取真实的请求/响应字段定义，对比代码实现找出不符项。触发关键词：字段核对、字段验证、字段不符、文档核对、核对请求字段、核对响应字段、飞书文档字段、推断字段、user 级接口、用户级接口字段
106 GitHub stars~2.3k tokensUpdated 6 days ago
Auto-check: notes
Openlark Code Standards
foxzool/openlark
OpenLark 项目代码规范检查技能。用于快速审查仓库内的架构一致性、API 实现套路、参数校验、命名与导出规范，并输出可执行检查清单与证据路径。Triggers: code review / consistency check / architecture audit / 规范检查 / 风格一致性 / 体检 / 对齐约定。项目锚点见 AGENTS.mdCONVENTIONS 与…
106 GitHub stars~1.8k tokensUpdated 6 days ago
Auto-check: notes
Openlark Design Review
foxzool/openlark
OpenLark Rust SDK 的代码设计/公共 API 规范审查技能（面向 crate/模块）。用于系统化检查入口设计、feature gating、Request/Service/Builder 一致性、端点体系、Config/错误处理、导出与文档同步、测试与告警控制，并输出按优先级排序的整改清单与可落地改造方案。触发关键词：设计审查、crate 设计、API 设计、public…
106 GitHub stars~2.1k tokensUpdated 6 days ago
Auto-check: notes
Openlark API Validation
foxzool/openlark
OpenLark API 覆盖率验证技能。用于验证各 crate 的 API 实现数量与覆盖率，基于 tools/validateapis.py 脚本和 apilistexport.csv 对比实际代码实现。触发关键词：API 验证、API 覆盖率、验证 API 数量、检查 API 实现、API 统计
106 GitHub stars~2k tokensUpdated 6 days ago
Auto-check: notes
Openlark Naming
foxzool/openlark
OpenLark Rust SDK 命名与对外 API 表达规范（Client/Service/Resource/Request/Builder）。用于新增/重构公开类型、设计 meta 调用链、调整模块导出与 prelude、或排查 Service 同名/语义错配/V{N}Service 版本层错位、Resource 与 Service 同类型两名、以及…
106 GitHub stars~2.1k tokensUpdated 6 days ago
Auto-check: notes

Works with

Questions about Verify Openlark

What does Verify Openlark do?

Prove OpenLark (Feishu/Lark Rust SDK) changes the way a maintainer does — cargo build/test, public examples, API coverage and field-verify harnesses. Verify Openlark is an agent skill from foxzool/openlark. Prove OpenLark (Feishu/Lark Rust SDK) changes the way a maintainer does — cargo build/test, public examples, API coverage and field-verify harnesses.

When should I use Verify Openlark?

Verify Openlark fits situations like: verifying a library change; before claiming an SDK fix works; asked to drive OpenLark verification.

How do I install Verify Openlark in Claude Code?

Run `npx skills add foxzool/openlark --skill verify-openlark -a claude-code`. Or copy the skill folder (.cursor/skills/verify-openlark in foxzool/openlark) into .claude/skills/verify-openlark in your project. Claude Code loads it when a task matches its description.

How do I install Verify Openlark in Codex?

Run `npx skills add foxzool/openlark --skill verify-openlark -a codex`. Or copy the skill folder (.cursor/skills/verify-openlark in foxzool/openlark) into .agents/skills/verify-openlark in your project. Codex loads it when a task matches its description.

Can I use Verify Openlark in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add foxzool/openlark --skill verify-openlark -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify-openlark, .gemini/skills/verify-openlark, .github/skills/verify-openlark and .opencode/skills/verify-openlark in your project.

What does Verify Openlark need to run?

Going by SKILL.md and its folder, Verify Openlark needs the command-line tools its instructions call (cargo, python3 and bash). Our summary lists: Python 3.

Does Verify Openlark access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Verify Openlark safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Verify Openlark use?

Verify Openlark is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify Openlark use?

About 1.8k tokens (SKILL.md is roughly 7.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Verify Openlark?

Skills that share tags, products or a category with Verify Openlark: Feishu Doc (openclaw/openclaw, 392k stars), Claude To Im (op7418/Claude-to-IM-skill, 2.9k stars), Feishu Doc (raucvr/Group-Goki, 112 stars) and Feishu Bridge (AlexAnys/feishu-openclaw, 317 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify Openlark?

foxzool (a GitHub user) maintains it in foxzool/openlark, which has 106 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on October 3, 2026.

Source: foxzool/openlark on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Verify Openlark

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Verify OpenLark

Launch

Doctor

Drive

Evidence

Cleanup

Helpers

Maintenance

Files

Compare with similar skills

Similar skills

More from foxzool/openlark

Related

Questions about Verify Openlark