Feishu Task Management

Overview

Use this skill to operate Feishu Task through the companion toolkit in feishu-task-management/toolkit/. Keep the core workflow in this file: decide the command, resolve members locally, and apply the write-safety rules without loading extra references unless the request falls into an edge case.

Core Workflow

1. 1. Confirm the request is about Feishu task management through the local toolkit.
2. Before the first API-backed operation, make sure the toolkit is configured. If not, use:

1. 3. Treat app credentials as mandatory base config. Prefer the configured user_access_token for task APIs when available, but keep contact and member-sync operations on app auth.
2. If the operation involves people, use the local member table through the toolkit. Do not perform ad hoc contact lookups.
3. Choose the narrowest task command available instead of composing generic HTTP requests.
4. For destructive or state-changing operations, inspect the current task first when practical.
5. Stop if member resolution is ambiguous or missing.

Command Routing

Member Table Maintenance

• - Sync the authorized contact scope:

• - Inspect sync state:

• - Test a member lookup:

• - Validate manual aliases:

Toolkit Configuration

• - Show configuration guidance:

• - Write a local runtime config:

• - Extend the config with existing user OAuth tokens:

• - Inspect effective config:

• - Validate current config:

Read Operations

• - Get one task:

• - List tasks:

Write Operations

• - Create a task:

• - Update core fields:

• - Complete a task:

• - Reopen a task:

• - Add members:

• - Remove members:

• - Delete a task:

Member Resolution

Use local resolution only, in this order:

1. 1. Explicit identifiers: open_id, user_id, email, INLINECODE24
2. Manual alias mapping from INLINECODE25
3. Exact canonical matches on name, en_name, nickname, and email
4. Limited fuzzy matching

Apply these safety rules:

• - Zero matches: stop and report that the member table or aliases need updating.
• One match: proceed.
• Multiple matches: stop and return the candidate list.

If the authorized scope only yields identifier fields without profile fields, natural-language matching depends on manual aliases. This does not change when task APIs later use a user token.

Write Safety Rules

• - Use the toolkit instead of constructing raw HTTP requests in the skill body.
• Prefer dedicated commands over generic update payloads when a command exists.
• Use dedicated completion commands instead of editing completed_at directly.
• Treat origin as create-only.
• Clear start and due explicitly instead of relying on omission.
• Require explicit confirmation before deletion.

Supported v1 Scope

• - Create task
• Get task
• List tasks
• Update summary, description, start, and due
• Delete task
• Complete task
• Reopen task
• Add members
• Remove members

The following are intentionally out of scope for v1:

• - reminders
• tasklists
• dependencies
• repeat rules
• custom complete
• attachments

Conditional References

Load extra context only when the request falls off the main path:

• - Read member-sync-troubleshooting.md only when member sync, alias validation, or authorized-scope coverage is the problem.
• Read task-edge-cases.md only when handling time-field clearing, origin, completion semantics, or deferred task features.
• Read permission-errors.md only when a task operation fails with permission-related behavior such as 1470403.
• Read api-alignment.md only when changing toolkit payloads or aligning CLI defaults to newer Feishu API samples.