Say that the CLI has issue and project commands

The work-management skill opened by stating that the CLI provides no named
`issue`, `project`, `label`, `milestone`, or `assignee` commands, and that every
operation had to be a hand-built `openagents api` route. That was true when it
was written. `openagents issue` and `openagents project` have covered most of
this for a while.

A skill that denies the existence of a command is worse than one that omits it.
Asked to list open CLI issues, a session read this, believed there was no
`issue list`, and went looking: `auth status`, `issue list --help` to check
whether the command was real, `pwd`, `git remote -v`, `repo list`, then two
list calls. Six shell commands to answer a question the first one could have.
With the sentence corrected it runs `issue list --state open --search CLI` and
answers.

The named commands are listed and preferred; `openagents api` keeps its place
for the routes that genuinely have no command, which is where the examples
below already were. The reading advice goes with it: plain output, and `--json`
only for one field out of one record, because a JSON list carries every issue's
whole body -- three issues are 442 bytes plain and 20,000 as JSON.

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

pushed

by user · WAL seq 286 · 2026-08-24T14:52:45.565661Z

Changed files

• modified .agents/skills/openagents-work-management/SKILL.md

Diff

1 file changed, +11 -1

Use this skill when the user asks you to manage OpenAgents issues, projects, comments, labels, assignees, milestones, or Projects V2 boards from the command line. Do not use the `pro-work-management` skill or the Pro Linear/MCP surface. This skill targets the OpenAgents `/api/v3` surface through the `@openagentsinc/cli` package.

The OpenAgents CLI does not provide named `issue`, `project`, `label`, `milestone`, or `assignee` commands. For all work system operations, use `openagents api` and construct the route path manually. The Projects V2 routes must be done manually.

The CLI has named commands for most of this work: `openagents issue`

(`list`, `view`, `create`, `close`, `reopen`, `comment`, `label`, `assign`,

`unassign`, `deps`) and `openagents project` (`list`, `view`, `create`,

`fields`, `items`, `item-add`, `item-set`, `item-move`, `item-remove`). Reach

for those first, and run `openagents <command> --help` for a flag you do not

know. Read their plain output; add `--json` only when you need one field out of

one record, because a JSON list carries every issue's whole body.

Use `openagents api` with a hand-built route only where no named command covers

what you need. Milestones and some Projects V2 routes are still in that

position, and the examples below show them.

## Before you start