agent-work

Register and render agent-produced work entities across diverse development platforms and shell environments.

82.1k|15.8k|Updated May 21, 2023
One-click install
npx skills add https://github.com/lobehub/lobehub --skill agent-work
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-work
Source: https://github.com/lobehub/lobehub/tree/main/.agents/skills/agent-work
Command: npx skills add https://github.com/lobehub/lobehub --skill agent-work

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the fragmentation of agent-generated outputs by providing a unified registry for tracking, deduplicating, and rendering work items like GitHub PRs, Linear issues, and local files directly within the assistant interface.

Core Features & Use Cases

  • Unified Work Registry: Tracks diverse entities (PRs, issues, files, tasks) in a single database schema with versioning support.
  • Automated Shell Scanning: Automatically detects and registers work items generated by CLI tools like gh or codex via shell command parsing.
  • Use Case: When an agent executes a series of shell commands to create a PR and update a local document, this Skill ensures both actions are captured, linked to the correct operation, and displayed as interactive cards in the chat history.

Quick Start

Run the agent-work scan to register all pending work items from the current operation.

Frequently Asked Questions about agent-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I register a new work type in the agent-work system?

Register a new work type by extending the WorkType union in @lobechat/types, implementing a corresponding WorkTypeAdapter, and adding it to the WORK_TYPE_ADAPTERS registry.

What happens if a shell command fails during work registration?

The system uses a success gate that skips registration for failed commands or plugin errors, ensuring only successful operations are recorded as valid work items.

How does the system handle duplicate work registrations?

Deduplication is managed via unique keys: (resourceType, resourceId) for works and (workId, toolCallId) for work versions, ensuring retried operations do not create redundant records.

Can I add a new shell CLI scanner for custom tools?

Yes, implement a scanner with matches, name, and register functions, then append it to the SHELL_WORK_SCANNERS registry in the server services directory.

Why are some work types hidden from the client UI?

New work types are hidden behind an OPT_IN_WORK_TYPES gate to maintain compatibility with older Electron clients that may crash when encountering unknown type descriptors.