Huly Skill
Read and write a Huly workspace through the bundled CLI at <skill-dir>/bin/huly.cjs
(shown below as huly). Start with huly whoami to confirm credentials and see
which identity your writes will be attributed to; huly whoami --offline diagnoses
configuration without a connection.
Credentials live in ~/.huly/.env, never inline. If it is missing any of
HULY_HOST, HULY_WORKSPACE_ID, HULY_API_KEY, read
references/setup.md first — same for where tokens come from
and for running inside the Cowork sandbox.
Pick the cheapest path that answers the question
One unfiltered huly tasks --json on a real workspace is 274 KB (107K tokens),
and a tool result stays in context for the rest of the session. Stop at the first
step that answers the question:
- Ask for the answer, not the rows —
huly report daily|weekly,
huly milestones report <id> return a computed summary (~13 KB for a full week).
- Filter at the source —
--assignee, --project, --status, --overdue,
--due-today, --parent, --milestone-id, then --limit and --fields to
cap rows and drop columns you will not read.
- Reduce in the shell — pipe
--json through jq, or stage it in a file and
print only what you need, so the rows never enter the conversation
(references/recipes.md).
- Only then list — and say what you left out.
Always pass --json when parsing or piping. Listings return
{"status":"ok","count":N,"data":[…]}; reports put their payload at the top level;
failures return {"status":"error","error":"…","code":"…","retryable":bool} —
retry only when retryable is true.
Everyday commands
huly tasks --assignee me --json # my active tasks
huly task DELTA-123 --json # one task, full detail
huly activity LAMBD-568 --comments-only --json # comments + changes on an issue
huly create task "Title" --project DELTA --parent DELTA-16 --assignee me
huly update task DELTA-123 --status "Done" --add-comment "shipped"
huly report weekly --json # computed weekly summary
Everything else — projects, task kinds, users, comments on any object (read, edit, delete), documents,
teamspaces, milestones, labels, priorities, dates, pasted-link resolution:
references/commands.md.
Before you write
- Task kinds are scoped by project type: take the id from
huly kinds --project <KEY> for the project you are writing to.
- A subtask is a task created with
--parent; nothing re-parents it afterwards.
me is HULY_ACTOR when set, else the owner of HULY_API_KEY — and Huly always
records that token owner as the author, whatever HULY_ACTOR says.- Deletes need
--yes. Errors print with an Error: prefix; in JSON, code and
retryable say whether another attempt can help.
- Never call Huly HTTP/WS APIs directly; the CLI is the source of truth.
Codex has no skill system: it uses AGENTS.md with the
@fioenix/huly-mcp server, which exposes the same operations as huly_* tools.
1---2name: huly-skill3description: Manages tasks, projects, labels, documents, milestones, and contacts in Huly project management. Use when the user asks to list tasks, create issues, update status, check what's overdue, generate daily/weekly reports, manage labels/tags, create or read documents, work with milestones, create subtasks under a parent issue, look up workspace people, or read, edit and delete comments/activity (on issues, milestones, or any object — including thread replies) in Huly. Supports both human-readable output and structured JSON mode for programmatic agent use.4license: MIT5---67# Huly Skill89Read and write a Huly workspace through the bundled CLI at `<skill-dir>/bin/huly.cjs`10(shown below as `huly`). Start with `huly whoami` to confirm credentials and see11which identity your writes will be attributed to; `huly whoami --offline` diagnoses12configuration without a connection.1314Credentials live in `~/.huly/.env`, never inline. If it is missing any of15`HULY_HOST`, `HULY_WORKSPACE_ID`, `HULY_API_KEY`, read16[references/setup.md](references/setup.md) first — same for where tokens come from17and for running inside the Cowork sandbox.1819## Pick the cheapest path that answers the question2021One unfiltered `huly tasks --json` on a real workspace is ~274 KB (~107K tokens),22and a tool result stays in context for the rest of the session. Stop at the first23step that answers the question:24251. **Ask for the answer, not the rows** — `huly report daily|weekly`,26 `huly milestones report <id>` return a computed summary (~13 KB for a full week).272. **Filter at the source** — `--assignee`, `--project`, `--status`, `--overdue`,28 `--due-today`, `--parent`, `--milestone-id`, then `--limit` and `--fields` to29 cap rows and drop columns you will not read.303. **Reduce in the shell** — pipe `--json` through `jq`, or stage it in a file and31 print only what you need, so the rows never enter the conversation32 ([references/recipes.md](references/recipes.md)).334. **Only then list** — and say what you left out.3435Always pass `--json` when parsing or piping. Listings return36`{"status":"ok","count":N,"data":[…]}`; reports put their payload at the top level;37failures return `{"status":"error","error":"…","code":"…","retryable":bool}` —38retry only when `retryable` is true.3940## Everyday commands4142```bash43huly tasks --assignee me --json # my active tasks44huly task DELTA-123 --json # one task, full detail45huly activity LAMBD-568 --comments-only --json # comments + changes on an issue46huly create task "Title" --project DELTA --parent DELTA-16 --assignee me47huly update task DELTA-123 --status "Done" --add-comment "shipped"48huly report weekly --json # computed weekly summary49```5051Everything else — projects, task kinds, users, comments on any object (read, edit, delete), documents,52teamspaces, milestones, labels, priorities, dates, pasted-link resolution:53[references/commands.md](references/commands.md).5455## Before you write5657- Task kinds are scoped by project **type**: take the id from58 `huly kinds --project <KEY>` for the project you are writing to.59- A subtask is a task created with `--parent`; nothing re-parents it afterwards.60- `me` is `HULY_ACTOR` when set, else the owner of `HULY_API_KEY` — and Huly always61 records that token owner as the author, whatever `HULY_ACTOR` says.62- Deletes need `--yes`. Errors print with an `Error:` prefix; in JSON, `code` and63 `retryable` say whether another attempt can help.64- Never call Huly HTTP/WS APIs directly; the CLI is the source of truth.6566Codex has no skill system: it uses [`AGENTS.md`](../../AGENTS.md) with the67`@fioenix/huly-mcp` server, which exposes the same operations as `huly_*` tools.
fioenix