task (v2)

task (v2):

Managing Lark Tasks with the Happycapy Skills Platform

The task (v2) skill for the Happycapy Skills platform provides a comprehensive interface for creating, updating, and managing tasks, subtasks, and task lists via the Lark (Feishu) API. This skill, identified as lark-task, leverages Lark’s robust task management capabilities and exposes them through a standardized command-line interface, enabling users to automate and streamline their workflow within Lark-based environments. This article provides an overview of the skill, its applications, usage instructions, and key implementation details.

What Is This Skill?

The lark-task skill is an integration tool that allows users to interact programmatically with Lark’s task management API. It supports the full lifecycle of task management, including:

• Creating new tasks and subtasks
• Viewing and updating task status
• Organizing tasks into lists
• Assigning tasks to collaborators
• Setting deadlines, reminders, and repeat rules

This skill is designed for scenarios where users need to automate to-do management, track progress, and coordinate with team members directly within the Happycapy Skills platform using the Lark API.

Why Use This Skill?

Efficient task management is critical for productivity and collaboration, especially in design and project-driven teams. The lark-task skill streamlines several key processes:

• Centralization: Manage all tasks and lists within the Lark ecosystem, ensuring consistency and visibility.
• Automation: Automate repetitive or bulk task operations via the CLI.
• Integration: Seamlessly connect task management with other Lark functionalities and organizational tools.
• Collaboration: Assign and organize tasks among team members, monitor progress, and receive reminders.

This skill is especially useful for teams already using Lark as their primary communication and coordination platform. It enables you to script, schedule, or trigger task workflows based on other events or user interactions.

How to Use It

Prerequisites

• The skill requires the lark-cli binary to be installed.
• Proper authentication and permissions must be configured as outlined in the shared SKILL.md file for Lark integrations.

Common Commands

Below are some typical use cases and their relevant command examples using the CLI:

1. Creating a

Task

To create a new task, use the +create shortcut. You must specify the task title, and you may optionally define a due date, assignees, and reminders.

lark-cli task +create --title "Design homepage mockup" --due "2024-07-01 18:00:00" --assignee open_id:ou_abcdefg

Note: repeat_rule and reminder can only be set if due is provided.

2. Searching for a

Task

If a user query only mentions the task name (e.g., "Complete Lobster One"), use the following:

lark-cli task +get-my-tasks --query "Lobster One"

This will search both completed and pending tasks for the given name.

3. Updating a

Task

To update an existing task, you need the task’s global unique identifier (GUID), not the display number. For example:

lark-cli task +update --guid 123e4567-e89b-12d3-a456-426614174000 --status completed

4. Listing Task

Details

When displaying task details, ensure that personnel fields such as assignee or creator show both the open_id and, if possible, the actual user name by referencing the company directory.

5. Managing Subtasks and

Lists

You can split tasks into subtasks and organize them into lists to better manage complex projects. Refer to the CLI help for subtask and list management syntax:

lark-cli task --help

When to Use This Skill

Use the lark-task skill in the following scenarios:

• Task Assignment: When you need to assign tasks to yourself or other team members, especially when user identity ("assigned to me") is mentioned.
• Project Tracking: For managing ongoing projects, updating task statuses, or organizing subtasks within lists.
• Automated Reminders: When you need to set up reminders or recurring tasks, provided a due date is set.
• Reporting: To quickly search, filter, and report on task completion and ownership within your organization.

This skill should be your default choice when dealing with todos or tasks within Lark, as it is specifically optimized for these operations.

Important Notes

• Authentication: Always consult the shared SKILL.md for up-to-date authentication and permissions handling. For user-specific actions, the current logged-in user’s open_id is used.
• Field Requirements: repeat_rule and reminder can only be set if a due date is specified. If both start and due are set, start must be earlier than or equal to due.
• User Identification: Always resolve personnel fields to actual names for clarity, not just IDs.
• GUID Usage: Operations on tasks require the GUID, not the display number. Extract the GUID from the task URL if necessary.
• Timezone Handling: Render all time fields such as creation and due dates in the local timezone using the format YYYY-MM-DD HH:MM:SS.
• Task URLs: When presenting task details, include the task’s url for direct access in the Lark client.

For more details, consult the source repository and the CLI help documentation.

By integrating the lark-task skill into your workflow, you can leverage the full power of Lark’s task management through automation, scripting, and seamless team collaboration.