lark-minutes▌
larksuite/cli · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理
minutes (v1)
CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理
核心概念
- 妙记 Token(minute_token):妙记的唯一标识符。通常可从妙记的 URL 链接中提取(例如
https://*.feishu.cn/minutes/obcnq3b9jl72l83w4f14xxxx中的最后一段字符串obcnq3b9jl72l83w4f14xxxx)。
使用说明
-
提取 Token:
- 只有
minute_token参数是必填的。 - 如果 URL 中包含额外参数(如
?xxx),请截取路径部分的最后一段作为 token。 - 示例:从
https://domain.feishu.cn/minutes/obc123456?project=xxx中提取出obc123456。
- 只有
-
获取妙记信息:
- 使用
lark-cli schema minutes.minutes.get可以查看具体的返回值结构。 - 返回的核心字段通常包含:
title:会议标题cover:视频/音频封面 URLduration:会议时长(毫秒)owner_id:所有者 IDurl:妙记链接
- 使用
典型场景
妙记内容查询
# 首先查询妙记元信息(标题、时长、封面) → 用本 skill
lark-cli minutes minutes get --params '{"minute_token": "obcn***************"}'
# 查妙记关联的纪要产物:逐字稿、总结、待办、章节等 → 用 lark-cli vc +notes
lark-cli vc +notes --minute-tokens obcnhijv43vq6bcsl5xasfb2
本 skill 仅提供妙记基础元信息查询(标题、封面、时长)。如需获取纪要内容(逐字稿、AI 总结、待办、章节),请使用 lark-cli vc +notes:
- 用户未指定需要查询妙记的哪些内容时,默认查询基础元信息和相关联的纪要产物信息。
- 用户未明确指定查看纪要产物(逐字稿、总结、待办、章节)时,向用户展示对应产物的链接即可,不需要直接读取产物内容。
Shortcuts(推荐优先使用)
Shortcut 是对常用操作的高级封装(lark-cli minutes +<verb> [flags])。有 Shortcut 的操作优先使用。
| Shortcut | 说明 |
|---|---|
+download |
Download audio/video media file of a minute |
妙记音视频下载
下载妙记音视频文件到本地,或获取有效期 1 天的下载链接。详见 minutes +download。
# 下载音视频文件到本地
lark-cli minutes +download --minute-tokens obcnq3b9jl72l83w4f149w9c --output ./meeting.mp4
# 仅获取下载链接
lark-cli minutes +download --minute-tokens obcnq3b9jl72l83w4f149w9c --url-only
# 批量下载
lark-cli minutes +download --minute-tokens obcnq3b9jl72l83w4f149w9c,obcnexa7814k4t41c446fzwj
API Resources
lark-cli schema minutes.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli minutes <resource> <method> [flags] # 调用 API
重要:使用原生 API 时,必须先运行
schema查看--data/--params参数结构,不要猜测字段格式。
minutes
get— 获取妙记信息
权限表
| 方法 | 所需 scope |
|---|---|
minutes.get |
minutes:minutes:readonly |
+download |
minutes:minutes.media:export |
How to use lark-minutes on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add lark-minutes
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches lark-minutes from GitHub repository larksuite/cli and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate lark-minutes. Access the skill through slash commands (e.g., /lark-minutes) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★42 reviews- ★★★★★Ishan Robinson· Dec 12, 2024
I recommend lark-minutes for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Chinedu Wang· Dec 8, 2024
Solid pick for teams standardizing on skills: lark-minutes is focused, and the summary matches what you get after install.
- ★★★★★Ganesh Mohane· Dec 4, 2024
lark-minutes reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Chinedu Gupta· Dec 4, 2024
lark-minutes is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Maya Ramirez· Nov 27, 2024
We added lark-minutes from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Sakshi Patil· Nov 23, 2024
I recommend lark-minutes for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Ishan Choi· Nov 7, 2024
Keeps context tight: lark-minutes is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Maya Mehta· Nov 7, 2024
lark-minutes has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Benjamin Khan· Nov 3, 2024
lark-minutes reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Maya Martinez· Oct 26, 2024
lark-minutes is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 42