メニュー
Create one Asana task through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a write fallback when the normal Asana connector is unavailable, and prefer --dry-run to confirm the payload before creating.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Call an arbitrary Asana REST API endpoint by HTTP method and path through the direct Asana API using a local ASANA_ACCESS_TOKEN. Use only as a low-level fallback when the normal Asana connector cannot reach the endpoint you need; you control the method, path, query, and body.
Add a comment story to one Asana task through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a narrow fallback when the normal Asana connector cannot post a comment to a target task.
Delete one Asana task through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a guarded fallback when the normal Asana connector cannot delete a target task. Live deletes require an explicit --confirm matching the resolved task gid.
List Asana projects in a workspace or team through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a read-only fallback when the normal Asana connector is unavailable or cannot enumerate the projects you need.
List the tags in an Asana workspace through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a read-only fallback when the normal Asana connector is unavailable or cannot enumerate workspace tags.
List Asana tasks for a project, section, tag, or assignee through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a read-only fallback when the normal Asana connector is unavailable or cannot enumerate the required tasks.
| name | asana-create-task |
| description | Create one Asana task through the direct Asana REST API using a local ASANA_ACCESS_TOKEN. Use only as a write fallback when the normal Asana connector is unavailable, and prefer --dry-run to confirm the payload before creating. |
| metadata | {"category":"productivity","capability_taxonomy_ids":["cap.productivity.task_tracking","cap.tools.api_automation"],"compatibility":{"runtimes":["codex","claude_code","cursor","antigravity","windsurf"]},"distribution_scope":"public","invocation_strategy":"explicit","version":"v0.1","source_of_truth":"https://github.com/nicshik/asana-skills"} |
Use this skill when the normal Asana connector cannot create a task and a narrow REST fallback is needed.
Prefer the official Asana connector for normal task creation. This skill is not a general Asana client.
ASANA_ACCESS_TOKEN is available in the shell, ASANA_ENV_FILE, --env-file, or a local .env.local.https://app.asana.com/api/1.0 is allowed.scripts/create_task.py.--project (project gid) or --workspace (workspace gid).--section requires --project.--notes, --notes-file, and --html-notes-file are mutually exclusive.--dry-run first to confirm the payload before creating.python3 scripts/create_task.py --name "Example task" --project 1200000000000000 --dry-run --json
python3 scripts/create_task.py --name "Example task" --workspace 1200000000000001 --notes "Body text" --json
python3 scripts/create_task.py --name "Example task" --project 1200000000000000 --section 1200000000000001 \
--tags "1200000000000000,1200000000000001" --assignee 1200000000000000 --due-on 2026-07-01 --json
action, plus payload summary on dry run, or gid, name, and permalink URL on create.--json output: schema_version, fetched_at, action, and either the redacted payload (dry run) or gid, name, permalink_url (created).--dry-run no API call is made; notes and html_notes are redacted to <N chars> in the payload.missing_token, not_found, permission_denied, rate_limited, and network.