Skip to main content
ClaudeWave
Skill82.4k repo starsupdated today

task

This Claude Code skill enables task management within LobeHub's task system, allowing Claude to view, edit, complete, and comment on tasks using the `lh task` CLI commands. Use this skill when Claude needs to manage task lifecycle operations, handle subtasks and dependencies, organize task workspace documents, or access task-related conversations and topics during extended workflows.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/lobehub/lobehub /tmp/task && cp -r /tmp/task/packages/builtin-skills/src/task ~/.claude/skills/task
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

\<task\_skill\_guides>
You are executing a task within the LobeHub task system. Use the `lh task` CLI via `runCommand` to manage your task and related resources.

# Task Lifecycle

| Command                         | Description                                           |
| ------------------------------- | ----------------------------------------------------- |
| `lh task view <id>`             | View task details, instruction, workspace, activities |
| `lh task edit <id>`             | Update task name, instruction, status, priority       |
| `lh task complete <id>`         | Mark task as completed                                |
| `lh task comment <id> -m "..."` | Add a progress comment                                |
| `lh task tree <id>`             | View subtask tree with dependencies                   |

# Working with Subtasks

| Command                                   | Description       |
| ----------------------------------------- | ----------------- |
| `lh task create -i "..." --parent <id>`   | Create a subtask  |
| `lh task list --parent <id>`              | List subtasks     |
| `lh task sort <parentId> <id1> <id2> ...` | Reorder subtasks  |
| `lh task dep add <id> <dependsOnId>`      | Add dependency    |
| `lh task dep rm <id> <dependsOnId>`       | Remove dependency |

# Task Workspace (Documents)

| Command                                           | Description               |
| ------------------------------------------------- | ------------------------- |
| `lh task doc create <id> -t "title" -b "content"` | Create and pin a document |
| `lh task doc pin <id> <docId>`                    | Pin existing document     |
| `lh task doc unpin <id> <docId>`                  | Unpin document            |

# Task Topics (Conversations)

| Command                             | Description              |
| ----------------------------------- | ------------------------ |
| `lh task topic list <id>`           | List conversation topics |
| `lh task topic view <id> <topicId>` | View topic messages      |

# Usage Pattern

1. Read the reference file for detailed command options: `readReference('references/commands')`
2. Run commands via `runCommand` — the `lh` prefix is automatically handled
3. Use `--json` flag on any command for structured output
4. Use `lh task <subcommand> --help` for full command-line help

# Task Execution Guidelines

- **Check your task first**: Use `lh task view` to understand the full instruction and context
- **Use workspace documents**: Store outputs and deliverables as task documents
- **Report progress**: Use `lh task comment` to log key milestones
- **Respect dependencies**: Check `lh task tree` to understand task ordering
- **Complete when done**: Use `lh task complete` when all deliverables are ready
- **Automation tasks are the exception — NEVER complete them**: a task with automation (heartbeat or schedule — shown as an `Automation:` line in the task context) is a recurring loop, and this run is one tick of it. NEVER run `lh task complete` (or set a terminal status via `lh task edit --status`) on that task: a terminal status cancels the in-flight run and permanently disarms the loop — no future tick will fire and nothing recovers it. A tick with nothing to do is still a successful run; just finish your turn and the next tick is armed automatically. Only the user retires a recurring task.
  \</task\_skill\_guides>
add-provider-docSkill

Add documentation for a new AI provider — usage docs, env vars, Docker config, image resources.

add-setting-envSkill

Add server-side environment variables that control default values for user settings.

agent-runtime-hooksSkill

Agent runtime lifecycle hooks. Use for before/after tool or step hooks, tool mocks, human intervention, sub-agent calls, context compression, evals, callAgent, or lifecycle events.

agent-signalSkill

Build or extend LobeHub Agent Signal pipelines. Use for signal sources, signal/action types, policies, middleware, workflow handoff, dedupe, scope behavior, or observability.

agent-tracingSkill

Agent tracing CLI for execution snapshots. Use for agent-tracing, traces, snapshots, LLM call inspection, context engine data, agent step analysis, execution debugging, or pulling remote/production traces ("拉线上 tracing") by operation id. Also the first stop for debugging agent tool calls — wrong or missing tool_calls, unexpected tool arguments or results, which tools were available at a step, or why a tool ran where it did.

builtin-toolSkill

Build LobeHub builtin tool packages. Use when adding agent-callable tools, manifests, executors, runtimes, inspectors, renders, placeholders, streaming, interventions, portals, or tool registries.

chat-sdkSkill

Build multi-platform chat bots with the chat SDK. Use for Slack, Teams, Google Chat, Discord, GitHub, Linear bots, webhooks, mentions, slash commands, cards, modals, or streaming responses.

cli-backend-testingSkill

>