# Asnx > Interact with Asana (tasks, projects, users, workspaces, and more) via the asnx CLI. Use whenever reading or modifying anything in Asana. - Skill: `mwpryer/asnx` (Agent Skill) - Install (CLI): `npx skillmds@latest add mwpryer/asnx` - Raw SKILL.md: https://api.skillmd.com/api/skills/mwpryer/asnx/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: mwpryer (https://skillmd.com/u/mwpryer) - Updated: 2026-09-22 - Page: https://skillmd.com/skills/mwpryer/asnx --- # `asnx`: Asana CLI ```sh asnx [] [--flags...] ``` The CLI is always flat: `asnx `. Sub-resource and verb actions stay explicit, for example `asnx tasks subtasks`, `asnx tasks create-subtasks`, and `asnx tasks add-followers`. Use `asnx describe [ []]` for schema introspection. ## Auth Resolution: `--account ` > `ASANA_TOKEN` env var > single stored account. `asnx auth status` verifies the resolved token against the API; use it to diagnose 401s. ## Input Writes accept either individual flags or a raw JSON body. `--json` wins on conflict. ```sh asnx tasks create --json '{"name":"bugfix","projects":["def"]}' ``` `--json` expects raw request fields only, not a full Asana `{ "data": ... }` envelope. ## Output Successful commands emit a JSON envelope with `meta` and `data`: ```json { "meta": { "command": "tasks.list", "status": 200, "nextPage": null }, "data": [ ... ] } ``` - `meta.command` is always `entity.action` (one dot), e.g. `tasks.list`, `tasks.subtasks`, or `project-briefs.create-for-project`. - `data` is the unwrapped Asana payload: object for single resources, array for lists. - `meta.nextPage` is a pagination offset (string) or `null`. Pass it as `--offset`. Errors go to stderr as `{"error":{"status":...,"message":...,"help":...}}`. `status` is `null` for local errors (usage, transport). The exit code is always 1 on error. ## Rules - Use `--dry-run` to preview writes before sending them. - `--opt-fields` on GET requests to keep responses small. - Pagination is manual: check `meta.nextPage`, pass as `--offset`. - Don't guess GIDs, query first. Start from `asnx workspaces list`, then e.g. `asnx tasks search --text "bugfix"`. - If entity commands come back as unknown, the schema cache is missing: run `asnx schema update`. - Dotted Asana filters stay dotted on the CLI, for example `--projects.any` or `--due-on.before`. ## Gotchas - `start_on` requires `due_on`: always send both together. - `me` is a positional GID alias, not an action. Use `users get me`, not `users me`. - `tasks for-project` returns all tasks, including completed ones, by default. To get only incomplete tasks pass `--completed-since ` (e.g. now); Asana then returns tasks that are incomplete or were completed since that time. - `tasks duplicate` and `projects duplicate` do not carry over every association. A duplicated task comes back with no project membership (`projects: []`) unless you pass `--include` naming the elements to copy, e.g. `--include projects,subtasks,assignee`. - `stories for-task` and `stories for-goal` return comments and system events together. Comments are the entries with `"type": "comment"`; filter client-side. - `tasks search` is eventually-consistent. Verify recent writes with `tasks get` or `tasks for-project`, not `search`. - `attachments create` is multipart on Asana's side and this CLI is JSON-only; the action surfaces but always fails. Use the raw API for file uploads. - `project-briefs create-for-project` may reject plain `--text` with `Rich text should be wrapped in tag.` If that happens, retry with `--html-text '...'`. - ` remove-members --members me` (portfolios, projects, goals, teams) revokes your own access.