CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionlark-sheetsExecute the skills CLI command in your project's root directory to begin installation:
Fetches lark-sheets from larksuite/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate lark-sheets. Access via /lark-sheets in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
6.8K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
6.8K
stars
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理
lark-cli docs +search。docs +search 会直接返回 SHEET 结果,不要把它误解成只能搜文档 / Wiki。sheets +info、sheets +read、sheets +find 等对象内部操作。飞书开放平台中,不同类型的文档有不同的 URL 格式和 Token 处理方式。在进行文档操作(如添加评论、下载文件等)时,必须先获取正确的 file_token。
| URL 格式 | 示例 | Token 类型 | 处理方式 |
|---|---|---|---|
/docx/ |
https://example.larksuite.com/docx/doxcnxxxxxxxxx |
file_token |
URL 路径中的 token 直接作为 file_token 使用 |
/doc/ |
https://example.larksuite.com/doc/doccnxxxxxxxxx |
file_token |
URL 路径中的 token 直接作为 file_token 使用 |
/wiki/ |
https://example.larksuite.com/wiki/wikcnxxxxxxxxx |
wiki_token |
⚠️ 不能直接使用,需要先查询获取真实的 obj_token |
/sheets/ |
https://example.larksuite.com/sheets/shtcnxxxxxxxxx |
file_token |
URL 路径中的 token 直接作为 file_token 使用 |
/drive/folder/ |
https://example.larksuite.com/drive/folder/fldcnxxxx |
folder_token |
URL 路径中的 token 作为文件夹 token 使用 |
知识库链接(/wiki/TOKEN)背后可能是云文档、电子表格、多维表格等不同类型的文档。不能直接假设 URL 中的 token 就是 file_token,必须先查询实际类型和真实 token。
使用 wiki.spaces.get_node 查询节点信息
lark-cli wiki spaces get_node --params '{"token":"wiki_token"}'
从返回结果中提取关键信息
node.obj_type:文档类型(docx/doc/sheet/bitable/slides/file/mindnote)node.obj_token:真实的文档 token(用于后续操作)node.title:文档标题根据 obj_type 使用对应的 API
| obj_type | 说明 | 使用的 API |
|---|---|---|
docx |
新版云文档 | drive file.comments.*、docx.* |
doc |
旧版云文档 | drive file.comments.* |
sheet |
电子表格 | sheets.* |
bitable |
多维表格 | bitable.* |
slides |
幻灯片 | drive.* |
file |
文件 | drive.* |
mindnote |
思维导图 | drive.* |
# 查询 wiki 节点
lark-cli wiki spaces get_node --params '{"token":"wiki_token"}'
返回结果示例:
{
"node": {
"obj_type": "docx",
"obj_token": "xxxx",
"title": "标题",
"node_type": "origin",
"space_id": "12345678910"
}
}
Wiki Space (知识空间)
└── Wiki Node (知识库节点)
├── obj_type: docx (新版文档)
│ └── obj_token (真实文档 token)
├── obj_type: doc (旧版文档)
│ └── obj_token (真实文档 token)
├── obj_type: sheet (电子表格)
│ └── obj_token (真实文档 token)
├── obj_type: bitable (多维表格)
│ └── obj_token (真实文档 token)
└── obj_type: file/slides/mindnote
└── obj_token (真实文档 token)
Drive Folder (云空间文件夹)
└── File (文件/文档)
└── file_token (直接使用)
操作流程(重要):
create — 创建筛选
update — 更新筛选
delete — 删除筛选
get — 获取筛选状态
多列筛选示例:
创建媒体名称(B列)和情感分析(E列)的双重筛选:
# 1. 删除现有筛选(如有)
lark-cli sheets spreadsheet.sheet.filters delete \
--params '{"spreadsheet_token":"<spreadsheet_token>","sheet_id":"<sheet_id>"}'
# 2. 创建第一个筛选,range 覆盖所有要筛选的列
lark-cli sheets spreadsheet.sheet.filters create \
--params '{"spreadsheet_token":"<spreadsheet_token>","sheet_id":"<sheet_id>"}' \
--data '{"col":"B","condition":{"expected":["xx"],"filter_type":"multiValue"},"range":"<sheet_id>!B1:E200"}'
# 3. 添加第二个筛选条件
lark-cli sheets spreadsheet.sheet.filters update \
--params '{"spreadsheet_token":"<spreadsheet_token>","sheet_id":"<sheet_id>"}' \
--data '{"col":"E","condition":{"expected":["xx"],"filter_type":"multiValue"}}'
常见错误:
Wrong Filter Value:筛选已存在,需要先 delete 再 createExcess Limit:update 时重复添加同一列条件Shortcut 是对常用操作的高级封装(lark-cli sheets +<verb> [flags])。有 Shortcut 的操作优先使用。
| Shortcut | 说明 |
|---|---|
+info |
View spreadsheet and sheet information |
+read |
Read spreadsheet cell values |
+write |
Write to spreadsheet cells (overwrite mode) |
+append |
Append rows to a spreadsheet |
+find |
Find cells in a spreadsheet |
+create |
Create a spreadsheet (optional header row and initial data) |
+export |
Export a spreadsheet (async task polling + optional download) |
lark-cli schema sheets.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli sheets <resource> <method> [flags] # 调用 API
重要:使用原生 API 时,必须先运行
schema查看--data/--params参数结构,不要猜测字段格式。
create — 创建电子表格get — 获取电子表格信息patch — 修改电子表格属性create — 创建筛选delete — 删除筛选get — 获取筛选update — 更新筛选find — 查找单元格| 方法 | 所需 scope |
|---|---|
spreadsheets.create |
sheets:spreadsheet:create |
spreadsheets.get |
sheets:spreadsheet.meta:read |
spreadsheets.patch |
sheets:spreadsheet.meta:write_only |
spreadsheet.sheet.filters.create |
sheets:spreadsheet:write_only |
spreadsheet.sheet.filters.delete |
sheets:spreadsheet:write_only |
spreadsheet.sheet.filters.get |
sheets:spreadsheet:read |
spreadsheet.sheet.filters.update |
sheets:spreadsheet:write_only |
spreadsheet.sheets.find |
sheets:spreadsheet:read |
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: lark-sheets is the kind of skill you can hand to a new teammate without a long onboarding doc.
lark-sheets reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend lark-sheets for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
lark-sheets reduced setup friction for our internal harness; good balance of opinion and flexibility.
lark-sheets fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
lark-sheets has been reliable in day-to-day use. Documentation quality is above average for community skills.
lark-sheets has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: lark-sheets is focused, and the summary matches what you get after install.
We added lark-sheets from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
I recommend lark-sheets for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 74