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-taskExecute the skills CLI command in your project's root directory to begin installation:
Fetches lark-task 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-task. Access via /lark-task 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,其中包含认证、权限处理
搜索技巧:如果用户的查询只指定了任务名称(例如“完成任务龙虾一号”),请直接使用
+get-my-tasks --query "龙虾一号"命令搜索(不要带--complete参数,这样可以同时搜索未完成和已完成的任务)。 用户身份识别:在用户身份(user identity)场景下,如果用户提到了“我”(例如“分配给我”、“由我创建”),请默认获取当前登录用户的open_id作为对应的参数值。 术语理解:如果用户提到 “todo”(待办),应当思考其是否是指“task”(任务),并优先尝试使用本 Skill 提供的命令来处理。 友好输出:在输出任务(或清单)的执行结果给用户时,建议同时提取并输出命令返回结果中的url字段(任务链接),以便用户可以直接点击跳转查看详情。
创建/更新注意:
- 只有在设置了
due(截止时间)的情况下,才能设置repeat_rule(重复规则)和reminder(提醒时间)。- 若同时设置了
start(开始时间)和due(截止时间),开始时间必须小于或等于截止时间。- 使用 tenant_access_token(应用身份)时,无法跨租户添加任务成员。
查询注意:
- 在输出任务详情时,如果需要渲染负责人、创建人等人员字段,除了展示
id(例如 open_id) 外,还必须通过其他方式(例如调用通讯录技能)尝试获取并展示这个人的真实名字,以便用户更容易识别。- 在输出任务详情时,如果需要渲染创建时间、截止时间等字段,需要使用本地时区来渲染(格式为2006-01-02 15:04:05)。
+create — Create a task+update — Update a task+comment — Add a comment to a task+complete — Complete a task+reopen — Reopen a task+assign — Assign or remove members from a task+followers — Manage task followers+reminder — Manage task reminders+get-my-tasks — List tasks assigned to me+tasklist-create — Create a tasklist and batch add tasks+tasklist-task-add — Add existing tasks to a tasklist+tasklist-members — Manage tasklist memberslark-cli schema task.<resource>.<method> # 调用 API 前必须先查看参数结构
lark-cli task <resource> <method> [flags] # 调用 API
重要:使用原生 API 时,必须先运行
schema查看--data/--params参数结构,不要猜测字段格式。
create — 创建任务delete — 删除任务get — 获取任务详情list — 列取任务列表patch — 更新任务add_members — 添加清单成员create — 创建清单delete — 删除清单get — 获取清单详情list — 获取清单列表patch — 更新清单remove_members — 移除清单成员tasks — 获取清单任务列表create — 创建子任务list — 获取任务的子任务列表add — 添加任务成员remove — 移除任务成员| 方法 | 所需 scope |
|---|---|
tasks.create |
task:task:write |
tasks.delete |
task:task:write |
tasks.get |
task:task:read |
tasks.list |
task:task:read |
tasks.patch |
task:task:write |
tasklists.add_members |
task:tasklist:write |
tasklists.create |
task:tasklist:write |
tasklists.delete |
task:tasklist:write |
tasklists.get |
task:tasklist:read |
tasklists.list |
task:tasklist:read |
tasklists.patch |
task:tasklist:write |
tasklists.remove_members |
task:tasklist:write |
tasklists.tasks |
task:tasklist:read |
subtasks.create |
task:task:write |
subtasks.list |
task:task:read |
members.add |
task:task:write |
members.remove |
task:task:write |
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
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Solid pick for teams standardizing on skills: lark-task is focused, and the summary matches what you get after install.
I recommend lark-task for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for lark-task matched our evaluation — installs cleanly and behaves as described in the markdown.
lark-task reduced setup friction for our internal harness; good balance of opinion and flexibility.
lark-task reduced setup friction for our internal harness; good balance of opinion and flexibility.
lark-task is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend lark-task for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
We added lark-task from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
lark-task reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in lark-task — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 70