lark-workflow-standup-report

larksuite/cli · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/larksuite/cli --skill lark-workflow-standup-report
0 commentsdiscussion
summary

CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理

skill.md

日程待办摘要工作流

CRITICAL — 开始前 MUST 先用 Read 工具读取 ../lark-shared/SKILL.md,其中包含认证、权限处理

适用场景

  • "今天有什么安排" / "今天的日程和待办"
  • "明天有什么会" / "明日日程与未完成任务"
  • "帮我看看今天要做什么" / "早报摘要"
  • "开工摘要" / "standup report"
  • "这周还有哪些安排"

前置条件

仅支持 user 身份。执行前确保已授权:

lark-cli auth login --domain calendar,task

工作流

{date} ─┬─► calendar +agenda [--start/--end] ──► 日程列表(会议/事件)
        └─► task +get-my-tasks [--due-end]    ──► 未完成待办列表
              AI 汇总(时间转换 + 冲突检测 + 排序)──► 摘要

Step 1: 获取日程

# 今天(默认,无需额外参数)
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-012026-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。

Step 2: 获取未完成待办

# 默认:返回分配给当前用户的未完成任务(最多 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 3: AI 汇总

将 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}(根据日程推算)

数据处理规则:

  1. 时间转换:API 返回 Unix timestamp,需根据 timezone 字段(通常为 Asia/Shanghai)转换为 HH:mm 格式
  2. RSVP 状态映射
    API 值 显示文案
    accept 已接受
    decline 已拒绝
    needs_action 待确认
    tentative 暂定
  3. 日程排序:按开始时间升序排列
  4. 冲突检测:按时间排序后,检查相邻日程是否有时间重叠(前一个 end_time > 后一个 start_time),有则在小结中列出冲突组
  5. 已拒绝日程:标注"已拒绝"但不计入忙碌时段和冲突检测
  6. 待办排序:按截止时间升序,已过期的标注"已过期",无截止时间的排在最后

权限表

命令 所需 scope
calendar +agenda calendar:calendar.event:read
task +get-my-tasks task:task:read

参考

how to use lark-workflow-standup-report

How to use lark-workflow-standup-report on Cursor

AI-first code editor with Composer

1

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-workflow-standup-report
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/larksuite/cli --skill lark-workflow-standup-report

The skills CLI fetches lark-workflow-standup-report from GitHub repository larksuite/cli and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/lark-workflow-standup-report

Reload or restart Cursor to activate lark-workflow-standup-report. Access the skill through slash commands (e.g., /lark-workflow-standup-report) 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

GET_STARTED →

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. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 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

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.532 reviews
  • Ganesh Mohane· Dec 28, 2024

    We added lark-workflow-standup-report from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Sofia Choi· Dec 24, 2024

    lark-workflow-standup-report reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Omar Chawla· Dec 24, 2024

    lark-workflow-standup-report has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • Noah Yang· Dec 20, 2024

    Registry listing for lark-workflow-standup-report matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Rahul Santra· Nov 19, 2024

    lark-workflow-standup-report reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Mia Torres· Nov 15, 2024

    We added lark-workflow-standup-report from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • Omar Farah· Nov 15, 2024

    Solid pick for teams standardizing on skills: lark-workflow-standup-report is focused, and the summary matches what you get after install.

  • Pratham Ware· Oct 10, 2024

    lark-workflow-standup-report is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Lucas Torres· Oct 6, 2024

    Keeps context tight: lark-workflow-standup-report is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Mateo Abbas· Oct 6, 2024

    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

1 / 4