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-workflow-standup-reportExecute the skills CLI command in your project's root directory to begin installation:
Fetches lark-workflow-standup-report 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-workflow-standup-report. Access via /lark-workflow-standup-report 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，其中包含认证、权限处理
仅支持 user 身份。执行前确保已授权：
lark-cli auth login --domain calendar,task
{date} ─┬─► calendar +agenda [--start/--end] ──► 日程列表（会议/事件）
└─► task +get-my-tasks [--due-end] ──► 未完成待办列表
│
▼
AI 汇总（时间转换 + 冲突检测 + 排序）──► 摘要
# 今天（默认，无需额外参数）
lark-cli calendar +agenda
# 指定日期范围（必须使用 ISO 8601 格式，不支持 "tomorrow" 等自然语言）
lark-cli calendar +agenda --start "2026-03-26T00:00:00+08:00" --end "2026-03-26T23:59:59+08:00"
注意：
--start/--end仅支持 ISO 8601 格式（如2026-01-01或2026-01-01T15:04:05+08:00）和 Unix timestamp，不支持"tomorrow"、"next monday"等自然语言。需要 AI 根据当前日期自行计算目标日期。
输出包含：event_id、summary、start_time（含 timestamp + timezone）、end_time、free_busy_status、self_rsvp_status。
# 默认：返回分配给当前用户的未完成任务（最多 20 条）
lark-cli task +get-my-tasks
# 只看指定日期前到期的（推荐用于摘要场景，减少数据量）
lark-cli task +get-my-tasks --due-end "2026-03-27T23:59:59+08:00"
# 获取全部（超过 20 条时）
lark-cli task +get-my-tasks --page-all
注意：不带过滤条件时可能返回大量历史待办（实测 30+ 条、100KB+），容易超出上下文限制。摘要场景建议：
- 用
--due-end过滤出目标日期前到期的任务- 如果也需要无截止日期的任务，可不加过滤，但 AI 汇总时只展示近 30 天内创建的，其余折叠为"其他 N 项历史待办"
将 Step 1 和 Step 2 的结果整合，按以下结构输出：
## {日期}摘要（{YYYY-MM-DD 星期X}）
### 日程安排
| 时间 | 事件 | 组织者 | 状态 |
|------|------|--------|------|
| 09:00-10:00 | 产品需求评审 | 张三 | 已接受 |
| 14:00-15:00 | 技术方案讨论 | 李四 | 待确认 |
### 待办事项
- [ ] {task_summary}（截止：{due_date}）
- [ ] {task_summary}
### 小结
- 共 {n} 场会议，{m} 项待办
- 冲突提醒：{列出时间重叠的日程}
- 空闲时段：{free_slots}（根据日程推算）
数据处理规则：
timezone 字段（通常为 Asia/Shanghai）转换为 HH:mm 格式| API 值 | 显示文案 |
|---|---|
accept |
已接受 |
decline |
已拒绝 |
needs_action |
待确认 |
tentative |
暂定 |
| 命令 | 所需 scope |
|---|---|
calendar +agenda |
calendar:calendar.event:read |
task +get-my-tasks |
task:task:read |
+agenda 详细用法+get-my-tasks 详细用法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
jezweb/claude-skills
We added lark-workflow-standup-report from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
lark-workflow-standup-report reduced setup friction for our internal harness; good balance of opinion and flexibility.
lark-workflow-standup-report has been reliable in day-to-day use. Documentation quality is above average for community skills.
Registry listing for lark-workflow-standup-report matched our evaluation — installs cleanly and behaves as described in the markdown.
lark-workflow-standup-report reduced setup friction for our internal harness; good balance of opinion and flexibility.
We added lark-workflow-standup-report from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: lark-workflow-standup-report is focused, and the summary matches what you get after install.
lark-workflow-standup-report is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: lark-workflow-standup-report is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend lark-workflow-standup-report for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
showing 1-10 of 32